Please note as of Wednesday, August 15th, 2018 this wiki has been set to read only. If you are a TI Employee and require Edit ability please contact x0211426 from the company directory.

Target Configuration - Custom Configurations

From Texas Instruments Wiki
Jump to: navigation, search


The Code Composer Studio v4 Target Configuration tool provides a way for users to create a target configuration (*.ccxml) file to be used by the debugger. While it is recommended to use the 'General Setup' to specify a custom target, the desired option for the 'Connection' or 'Device' may not be available for a specific emulator or target board. This is because the XML files which contain the list of options displayed in the 'General Setup' may not have an entry for that particular connection and device combination. In these cases the user will need to build their own configuration using the 'Advanced Setup' utility.

Advanced Setup

The 'Advanced Setup' utility allows the user to build a configuration by selecting from a list of available 'Connections' to specify the connection type, and then selecting from the list of components ('Devices', 'Cpus', 'Routers') to add to the connection to complete the configuration. It will be difficult to properly use the 'Advanced Setup' utility unless the user has good knowledge of the device they are building their configuration for.

Let's walk through the creation of an example configuration for a single TCI6486 device using a Blackhawk USB-510 emulator using the 'Advanced Setup' utility. The connection type will be a Blackhawk USB-510 emulator and routers and CPU component types will be added to the configuration. A device component type is not used since a TCI6486 device file does not come with CCStudio (see next section 'Using Device Files' for more information on device files).

The first step is to enter the 'Advanced Setup' utility:

Fig. 1: Entering 'Advanced Setup'

Now we can build a custom configuration. For this example, a configuration for a single TCI6486 device using a Blackhawk USB-510 emulator will be created.

Next, specify the connection (emulator) we wish to use by selecting 'New':

Fig. 2: 'Advanced Setup' Utility

Then select the desired connection (BH USB510 Emulator):

Fig. 3: Selecting a Connection

We can see that the BH USB510 Emulator connection has been added to the left pane. The 'Connection Properties' for the emulator can be modified in the right pane if needed.

Fig. 4: 'Advanced Setup' with Connection Specified

Next we will add the router we need for a TCI6486 by selecting 'Add' and then selecting 'IcePick_C' under the list of available routers:

Fig. 5: Selecting a Router

We can see that an 'IcePick_C' has been added to the left pane. Now select the added router and the hit the 'Add' button:

Fig. 6: 'Advanced Setup' with Connection and Router Component Specified

Then specify the number of subpaths to be '6' as highlighted with the red circle in the screenshot below:

Fig. 7: Specifying Number of Subpaths

We can see that six subpaths have been added to the left pane. The 'Port Number' for each subpath will need to be specified. For a TCI6486 device, the port numbers start at '16' for the first core and '21' for the last:

Fig. 8: Configuring the Port Number

Next we will add a C64x+ CPU under each subpath.

To do so, highlight a subpath and then hit the 'Add' button. Then select a C64XP CPU under the list of available CPUs:

Fig. 9: Selecting a CPU

We can see that a C64XP CPU has been added to the left pane, under the specified subpath:

Fig. 10: 'Advanced Setup' with Added CPU Component Under First Subpath

Repeat this until a C64XP CPU has been added for each subpath:

Fig. 11: Completed Setup

A GEL startup script can be specified for each CPU. The above screenshot shows where this can be done.

Now the target configuration has been created for a TCI6486 device using a Blackhawk 510-USB Emulator.

Note that each of the names for the connection and components added can be renamed if desired:

Fig. 12: Renaming the Connection

Device Files

Device files are setup xml files that provides all the information for an entire device. This can include router information, multiple CPUs, etc. For example, a DM6446 device consists of one router (ICEPick C) with three subpaths with a different CPUs on each subpath (ARM9, ETB, C64x+). If the target consists of only one device and a device file for the device exists, then all that is needed to build the target configuration is to utilize that device file. If a device file exists with CCStudio for a particular device, it will appear in the 'Devices' category:

Fig. 13: Selecting the DM6446 Device

An added device has its own distinct device icon as highlighted in the screenshot below. Note how by adding the DM6446 device, the rest of the configuration for a DM6446 (router, CPU information) is complete:

Fig. 14: Configured for a DM6446 target

Thus if the target consists of one DM6446 device (DM6446 EVM), then the target configuration is complete.

Another benefit of using device files is that device files often reference other module xml files which describe device specific memory mapped register information to the CCStudio 'Register' view. This allows for more detailed information to appear in the 'Register' view that normally would not appear.

Multiple devices (whether same or different) can be added to a single connection. Check the short clip below for details on how to do that.

Multiple devices in the same target configuration

Combining devices with non-device file specified information for a single connection is also allowed.

The screenshot below shows the process of adding multiple devices or bypass devices in the same scan chain.

  1. Highlight the Texas Instruments XDS... entry under All Connections
  2. Click on Add...
  3. In the </i>Add Component</i> box, select the desired device or bypass.
  4. Repeat the process for all devices, always highlighting the Texas Instruments XDS... before clicking on the Add... button.
Fig. 15: Adding multiple devices and bypasses to a configuration

Multiple debug probes

When using multiple debug probes, the procedure is very similar as above. The only difference is the option New... is used in this case.

Fig. 16: Adding multiple debug probes to a configuration

Additional instructions on how to set up the serial number for XDS100 and XDS110 are shown in the respective debug probe pages. XDS200 and XDS560v2 port numbers are ordered by the time they are connected to the host.