GSG:Common target configurations

---

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: 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! Although CCSv4 comes with several ready-to-run board configurations pre-installed, some boards still require GEL files to be either downloaded from the board manufacturer website or installed from the companion CD - these cases will be highlighted below. These files are required to properly initialize the device and the board during debugging.

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

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 emulation

The Stellaris configuration using the embedded emulator 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 the Stellaris Launchpad!

Boards with XDS100v1 onboard emulator:

• controlSTICK (F28027, F28029), Piccolo Experimenter Kits (F28027, F28035, F2808), Delfino Experimenter Kits (C28343, F28335)
• C5505 and C5515 eZDSP USB Stick
• EVMC6457, EVMC6472
• OMAPL138EVM, AM3517EVM

Add the following parameters to the new target configuration:

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

GEL configuration files are required for:

• EVMC6457 - files are supplied with the companion CD
• EVMC6472 - http://www.einfochips.com/TI/evm6472-support.php
• OMAPL138 - link Access Downloads at http://www.logicpd.com/product-support (requires registration)

Note: the embedded emulator on OMAPL138EVM only connects to the DSP.

Note: check the section GSG:Adding_GEL_files_to_a_target_configuration for additional details.

Boards with XDS100v2 onboard emulator:

• C2000 LaunchPad
• Concerto ControlCARD and Concerto Experimenter Kit
• AM1808 EVM
• AM3517EVM
• BeagleBone
• AM335x Starter Kit

Add the following parameters to the new target configuration:

• In the box Connection select the option Texas Instruments XDS100v2 USB Emulator.
• In the box Board or Device select the appropriate board: AM1808EVM.

GEL configuration files are required for:

• AM1808EVM - link Access Downloads at http://www.logicpd.com/product-support (requires registration)
• AM3517EVM - link Access Downloads at http://www.logicpd.com/product-support (requires registration)

Note: check the section GSG:Adding_GEL_files_to_a_target_configuration for additional details.

Boards with XDS510USB onboard emulator:

• eZdspF2808, eZdspR2812, eZdspF28335, eZdspF28044
• DSK5416
• EVM5505, EVM5515, 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 emulator:

• 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 AM1707.

ARM and SoC boards without onboard emulation

• EVMDM6446, EVMDM6467, EVMDM6467T
• EVMDM355, EVMDM365, OMAP3530EVM
• Beagleboard, Hawkboard, Leopardboard
• DM8148 EVM, DM8168 EVM
• AM335x EVM

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

Check the section GSG:Connecting_to_slave_cores_in_SoC_devices before trying to load code to the slave core of SoC devices.

Beagleboard, Hawkboard, Leopardboard, Pandaboard

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 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 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 CCSv4 Getting Started Guide.

---

CN GSG:Common target configurations