Introduction

This page is intended to help developers find the required settings when creating the target configuration file (.ccxml) for development kits and LaunchPads that have built-in Debug Probes.

Despite several example projects already pre-configure the Target Configuration Files, it is not uncommon to have to manually create these files, thus finding the correct settings may be tricky.

All the procedures below start from the common steps to create a new Target Configuration File: right-click on the project name (or go to menu File) and select New → Target Configuration File; then select a name and click Finish. The topics below show the configuration settings.

Differences between boards and devices

Code Composer Studio comes with several ready-to-run processor board configurations (GPEVM_AM572X, K2GEVM, etc.) with platform GEL files, which configure not only the device but also board peripherals.

If you intend to connect to a device with minimal disruption (case where there is already software running on it such as Linux or RTOS), then select the device itself (AM5728, 66AK2G02, etc.) as they do not have platform GEL files.

Configuration examples

MSP430 USB Debug Interface

Configure MSP430 devices is pretty straightforward. Creating a new project using the wizard also creates the target configuration for the processor of choice: a file named <name_of_device.ccxml>. If desired, additional target configurations can be created by simply creating a new target file with the following settings:

• In the box Connection select the option TI MSP430 USB1. It can also be USB2 or USB3 if additional debug probes are connected to the host

• Search for or select the desired device in the box Board or Device.

  Note: this is also valid for the MSP430 LaunchPad!
  

Stellaris on-board ICDI

The Stellaris configuration using the embedded debug probe is also pretty straightforward. Creating a new project using the wizard also creates the target configuration for the processor of choice: a file named <target_config.ccxml>. If desired, additional target configurations can be created by simply creating a new target file with the following settings:

• In the box Connection select the option Stellaris In-circuit Debug Interface.
• Search for or select the desired device in the box Board or Device.

XDS100v1 onboard debug probe

Add the following parameters to the new target configuration:

• In the box Connection select the option Texas Instruments XDS100v1 USB Debug Probe.
• In the box Board or Device select the appropriate board: USBSTK5505, TMS320C6457, OMAPL138, etc.

^*Requires configuring GEL files separately

XDS100v2 onboard debug probe

Add the following parameters to the new target configuration:

• In the box Connection select the option Texas Instruments XDS100v2 USB Debug Probe.
• In the box Board or Device select the appropriate board: AM1808EVM, TMS570LS3137, etc.
  • For C2000 and Hercules devices, select the device

XDSD100v3 debug probe

Add the following parameters to the new target configuration:

• In the box Connection select the option Texas Instruments XDS100v3 USB Debug Probe.
• In the box Board or Device select the appropriate device: CC2538, CC2650, etc.

XDS110 debug probe

Add the following parameters to the new target configuration:

• In the box Connection select the option Texas Instruments XDS110 USB Debug Probe.
• In the box Board or Device select the appropriate device: MSP432P401R, CC2650, etc.

Boards with XDS510USB onboard debug probe

Add the following parameters to the new target configuration:

• In the box Connection select the option Spectrum Digital DSK-EVM-eZdsp onboard USB Emulator.
• In the box Board or Device select the appropriate board: EZDSPF2808, EVM5505, DSK6455, etc.

Note: Additional information can be obtained at the manufacturer's support page: http://support.spectrumdigital.com/

Boards with XDS510USB Plus onboard debug probe

Add the following parameters to the new target configuration:

• In the box Connection select the option Spectrum Digital DSK-EVM PLUS onboard USB Emulator.
• In the box Board or Device select the appropriate board: EVMOMAPL137 or EVMAM1707.

Boards with XDS200 Mezzanine debug probe

Add the following parameters to the new target configuration:

• In the box Connection select the option Texas Instruments XDS2xx USB Onboard Debug Probe.
• In the box Board or Device select the appropriate device: TMS320C6657.

^*Requires configuring GEL files separately

Boards with XDS560v2 STM Mezzanine debug probe

Add the following parameters to the new target configuration:

• In the box Connection select the option Blackhawk XDS560v2-USB Mezzanine Emulator.
• In the box Board or Device select the appropriate board/device: EVMC6472, TMS320C6657, TMS320C6670 or TMS320C6678.

These are two of the few boards that still do not have board configurations with platform GEL files, thus requiring separate GEL configuration files to be added. They are installed with CCSv5 and are typically located at:

Note: check the section [[GSG:Adding GEL files to a target configuration v5]] for additional details.

^*Requires configuring GEL files separately

ARM and SoC boards without onboard debug probe:

Add the following parameters to the new target configuration:

• In the box Connection select the debug probe being used (any class: XDS100v2, XDS110, XDS2xx, XDS510, XDS560).
• In the box Board or Device select the appropriate board: LCDKOMAPL138, LCDKC6748, EVMAM437X, etc.

List of boards:

• LCDKOMAPL138, LCDKC6748
• EVMAM437X (AM437x Evaluation Module - TMDXEVM437X)
• EVMDM6446, EVMDM6467, EVMDM6467T
• EVMDM355, EVMDM365, OMAP3530EVM
• Beagleboard, Hawkboard, Leopardboard
• DM8148 EVM, DM8168 EVM

Check the section [[GSG:Connecting to slave cores in SoC devices v5]] before trying to load code to the slave core of SoC devices.

BeagleBone Black, BeagleBoard-x15, Beagleboard, Hawkboard, Leopardboard, Pandaboard

Code Composer Studio has GEL scripts for several of these boards, but under certain circumstances the procedure below still applies.

These boards sometimes are better initialized by the U-boot code instead of using a GEL script, therefore requiring the removal of the GEL script from the target configuration.

1. Add the following parameters to the new target configuration:

• In the box Connection select the emulator being used (any emulator class: XDS100v2, XDS510, XDS560).
• In the box Board or Device select the appropriate device: AM3359, AM5728, OMAP3530, OMAPL138, DM365, etc.

2. If the configuration has a pre-configured GEL file, remove it. Check the section [[GSG:Adding GEL files to a target configuration v5]] to learn how to do this.

3. Connect the host PC to the serial port of the board and open a terminal program, as it would be done normally if CCSv4 was not being used.

4. When the board is turned on, hit any key when the autoboot prompt asks to do so. An example would be

Texas Instruments X-Loader 1.4.4ss (Apr 13 2010 - 22:36:28)
Beagle Rev C1/C2/C3
Reading boot sector
Loading u-boot.bin from mmc


U-Boot 2010.03 (May 04 2010 - 08:48:31)

OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max clock-600Mhz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  256 MB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial

Probing for expansion boards, if none are connected you'll see a harmless I2C er
ror.

Recognized Tincantools Zippy expansion board (rev 1 )
Beagle Rev C1/C2/C3
Die ID #3e8c000300000000040323090a021014
Hit any key to stop autoboot:  0

5. Connect to the target normally. Do not forget to follow the procedure in the section below [[GSG:Connecting to slave cores in SoC devices v5]] if trying to load code to slave cores.

Resources

Code Composer Studio
Related Technical Documents
TI E2E Technical Forums

This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.

Last updated: May 17 2022 13:20 Central Time