GSG:Common target configurations v5

---

Common target configurations.

---

Introduction

This section contains settings required to properly configure the target configuration files (.ccxml) for common boards and board/emulator combinations.

All the procedures below start from a common method shown in GSG:Debugging_projects_v5: 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.

Important! CCSv5.2 comes with several ready-to-run board configurations (EVMAM1808, EVMDM8148, 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), then select the device itself (AM3359, OMAPL138, etc.) as they do not have platform GEL files.

Important! Additional device support for newer devices and boards is located at the page Device support files.

Configuration examples

MSP430 USB Debug Interface:

The MSP430 Configuration using the USB Debug Interface 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 emulators 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.

Note: this is also valid for both all Stellaris and Tiva Launchpads, as well as for the CC3200 Launchpad!

Boards with XDS100v1 onboard debug probe:

• Most C2000 development boards: controlSTICK (F28027, F28069), Piccolo Development Kits (F28027, F28035, F28055, F28069, F28075), Delfino Development Kits (C28343, C28346, F28335, F28377, F28377D)
• C5505 (TMDX5505EZDSP), C5515 (TMDX5515EZDSP) and C5535 (TMDX5535EZDSP) eZdsp USB Sticks
• TMDXEVM6457, TMDSEVM6472, TMDSEVM6670L, TMDSEVM6678L
• Zoom OMAP-L138 EVM

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.

Boards with XDS100v2 onboard debug probe:

• TMS470M HDK Kit and USB Development Stick
• TMS570 MDK Kit and TMS570 USB Kit
• TMS570LS31x HDK Kit, TMS570LS31x USB Kit, and TMS570LS31x CNCD
• TMS570LS12x HDK Kit and TMS570LS12x CNCD
• TMS570LS04x HDK Kit
• RM48 HDK Kit, RM48 USB Kit and RM48 CNCD
• RM46 HDK Kit and RM46 CNCD
• RM42 HDK Kit
• C2000 LaunchPad
• Concerto ControlCARD and Concerto Experimenter Kit
• Zoom AM1808 EVM
• BeagleBone White, AM335x Starter Kit (TMDSSK3358), AM335x Evaluation Module (TMDXEVM3358)
• AM437x Industrial Development Kit (TMDXIDK437X), AM437x Starter Kit (TMDXSK437X)

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.

Boards with XDSD100v3 debug probe:

• CC2538 Development Kit (CC2538DK), CC2650 Development Kit (CC2650DK)

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.

Boards with XDS110 debug probe:

• MSP432P401R Launchpad (MSP-EXP432P401R)
• CC2650 SimpleLink SensorTag Debugger DevPack (CC-DEVPACK-DEBUG)

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:

• eZdspF2808, eZdspR2812, eZdspF28335, eZdspF28044
• DSK5416
• EVM5505, EVM5515, EVM5517, DSK5509A, DSK5510
• DSK6713, DSK6416, DSK6455, EVM6455, EVMC6424, EVMC6474, EVMDM6437

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.

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

Boards with XDS510USB Plus onboard debug probe:

• EVMOMAPL137
• EVMAM1707

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:

• TMDSEVM6657LS, EVMK2H, EVMK2HX

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.

Boards with XDS560v2 STM Mezzanine debug probe:

• TMDSEVM6472LE
• TMDSEVM6657LE
• TMDSEVM6670LE
• TMDSEVM6678LE

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:

C:\ti\ccsv5\ccs_base\emulation\boards

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

ARM and SoC boards without onboard debug probe:

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

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: EVMDM6446, EVMDM355, OMAP3530, etc.

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

Beagleboard, Hawkboard, Leopardboard, Pandaboard

Later revisions of CCS (CCSv5.2 onwards) have GEL scripts for all 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: 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.

Additional Topics

Now that you have learned about common target configurations, you can check other Advanced Topics of the CCSv5 Getting Started Guide.

---