Common target configurations

# 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. <table id="stl01"> <tr> <th> Board </th> <th> Setting </th> </tr> <tr> <th colspan="2">Simplelink Wi-Fi LaunchPads</th> </tr> <tr> <th>CC3200S-LAUNCHXL </th> <th>CC3200 or CC3200-SWD</th> </tr> <tr> <th>CC3200SF-LAUNCHXL</th> <th>CC3200 or CC3200-SWD</th> </tr> <tr> <th colspan="2">TM4C LaunchPads</th> </tr> <tr> <th>EK-TM4C123GXL</th> <th>TM4C123GH6PM</th> </tr> <tr> <th>EK-TM4C1294XL</th> <th>TM4C1294NCPDT</th> </tr> <tr> <th>EK-TM4C129EXL</th> <th>TM4C1294NCPDT</th> </tr> <tr> <th colspan="2">TM4C Design Kits</th> </tr> <tr> <th>DK-TM4C123G</th> <th>TM4C123GH6PM</th> </tr> <tr> <th>DK-TM4C129X</th> <th>TM4C1294NCPDT</th> </tr> <tr> <th colspan="2">All legacy Stellaris (LM3S) development kits</th> </tr> </table> ## 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. <table id="stl01"> <tr> <th> Board </th> <th> Setting </th> </tr> <tr> <th colspan="2">C2000 Experimenter's Kits</th> </tr> <tr> <th>TMDSDOCK28027</th> <th>TMS320F28027</th> </tr> <tr> <th>TMDSDOCK28035</th> <th>TMS320F28035</th> </tr> <tr> <th>TMDXDOCK28055</th> <th>TMS320F28055</th> </tr> <tr> <th>TMDSDOCK28069</th> <th>TMS320F28069</th> </tr> <tr> <th>TMDSDOCK28335</th> <th>TMS320F28335</th> </tr> <tr> <th>TMDSPREX28335</th> <th>TMS320F28335</th> </tr> <tr> <th>TMDXDOCK28343</th> <th>TMS320F28343</th> </tr> <tr> <th>TMDXDOCK28346</th> <th>TMS320F28346</th> </tr> <tr> <th colspan="2">C2000 controlCARDs</th> </tr> <tr> <th>TMDSCNCD28035ISO </th> <th>TMS320F28035</th> </tr> <tr> <th>TMDSCNCD28054MISO</th> <th>TMS320F28054</th> </tr> <tr> <th>TMDSCNCD28069ISO </th> <th>TMS320F28069</th> </tr> <tr> <th>TMDSCNCD28069MISO</th> <th>TMS320F28069</th> </tr> <tr> <th colspan="2">C2000 controlSTICKs</th> </tr> <tr> <th>TMDS28027USB</th> <th>TMS320F28027</th> </tr> <tr> <th>TMDS28069USB</th> <th>TMS320F28069</th> </tr> <tr> <th colspan="2">C5000 eZdsp USB Sticks</th> </tr> <tr> <th>TMDX5505EZDSP (device: TMS320C5505 or TMS320VC5505)</th> <th>USBSTK5505 or USBSTK5505_VC5505</th> </tr> <tr> <th>TMDX5515EZDSP (device: TMS320C5515)</th> <th>USBSTK5515</th> </tr> <tr> <th>TMDX5535EZDSP (device: TMS320C5535)</th> <th>EZDSP5535</th> </tr> <tr> <th colspan="2">C6000 Evaluation Modules</th> </tr> <tr> <th>TMDSEVM6457L (device:TMS320C6457)</th> <th>TMDSEVM6457L</th> </tr> <tr> <th>TMDSEVM6472 (device: TMS320C6472)</th> <th>EVMC6472</th> </tr> <tr> <th>TMDSEVM6474L (device:TMS320C6474)</th> <th>TMDSEVM6474L</th> </tr> <tr> <th>TMDSEVM6670L</th> <th>TMS320C6670&lowast; </th> </tr> <tr> <th>TMDSEVM6657L</th> <th>TMS320C6657&lowast;</th> </tr> <tr> <th>TMDSEVM6678L</th> <th>TMS320C6678&lowast;</th> </tr> <tr> <th colspan="2">Sitara Evaluation Modules</th> </tr> <tr> <th>Zoom OMAP-L138 EVM</th> <th>EVMOMAPL138</th> </tr> </table> *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 <table id="stl01"> <tr> <th> Board </th> <th> Setting </th> </tr> <tr> <th colspan="2">C2000 LaunchPads</th> </tr> <tr> <th>LAUNCHXL-F28027</th> <th>TMS320F28027</th> </tr> <tr> <th>LAUNCHXL-F28027F</th> <th>TMS320F28027</th> </tr> <tr> <th>LAUNCHXL-F28069M</th> <th>TMS320F28069</th> </tr> <tr> <th>LAUNCHXL-F28377S</th> <th>TMS320F28377S</th> </tr> <tr> <th>LAUNCHXL-F28379D</th> <th>TMS320F28379D</th> </tr> <tr> <th colspan="2">C2000 controlCARDs</th> </tr> <tr> <th>TMDSCNCD280049M</th> <th>TMS320F280049M</th> </tr> <tr> <th>TMDSCNCD28055ISO</th> <th>TMS320F28055</th> </tr> <tr> <th>TMDXCNCD28075ISO</th> <th>TMS320F28075</th> </tr> <tr> <th>TMDSCNCD28377D</th> <th>TMS320F28377D</th> </tr> <tr> <th>TMDSCNCD28379D</th> <th>TMS320F28379D</th> </tr> <tr> <th>TMDSCNCDH52C1</th> <th>F28M35H52C1</th> </tr> <tr> <th>TMDSCNCD28M36</th> <th>F28M36P63C2</th> </tr> <tr> <th colspan="2">Sitara Industrial Development Kits</th> </tr> <tr> <th>TMDSICE3359 (device: AM3359)</th> <th>ICE_AM3359</th> </tr> <tr> <th>TMDXIDK437X (device: AM4379)</th> <th>IDK_AM437X</th> </tr> <tr> <th>TMDXIDK5718 (device: AM5718)</th> <th>IDK_AM571X</th> </tr> <tr> <th>TMDXIDK5728 (device: AM5728)</th> <th>IDK_AM572X</th> </tr> <tr> <th>TMDXIDK5748 (device: AM5748)</th> <th>IDK_AM574X</th> </tr> <tr> <th colspan="2">Sitara Starter Kits</th> </tr> <tr> <th>BeagleBone White</th> <th>BeagleBone</th> </tr> <tr> <th>TMDSSK3358 (device: AM3358)</th> <th>SK_AM3358</th> </tr> <tr> <th>TMDXSK437X (device: AM4379)</th> <th>SK_AM437X</th> </tr> <tr> <th colspan="2">Sitara Evaluation Modules</th> </tr> <tr> <th>TMDXEVM3358 (device: AM3358)</th> <th>EVMAM3358</th> </tr> <tr> <th>TMDSEVM437X (device: AM4379)</th> <th>EVMAM437X</th> </tr> <tr> <th>Zoom AM1808 EVM</th> <th>EVMAM1808</th> </tr> <tr> <th colspan="2">Hercules LaunchPads</th> </tr> <tr> <th>LAUNCHXL-TMS57004 (device: TMS570LS0432)</th> <th>TMS570LS043x</th> </tr> <tr> <th>LAUNCHXL-RM42</th> <th>RM42L432</th> </tr> <tr> <th colspan="2">Hercules USB Sticks</th> </tr> <tr> <th>TMDX470MF066USB</th> <th>TMS470MF06607</th> </tr> <tr> <th>TMDS570LS31USB</th> <th>TMS570LS3137</th> </tr> <tr> <th>TMDSRM48USB</th> <th>RM48L952</th> </tr> <tr> <th colspan="2">Hercules controlCards</th> </tr> <tr> <th>TMDXLS12CNCD</th> <th>TMS570LS1227</th> </tr> <tr> <th>TMDX570LS31CNCD</th> <th>TMS570LS3137</th> </tr> <tr> <th>TMDXRM46CNCD</th> <th>RM46L852</th> </tr> <tr> <th>TMDXRM48CNCD</th> <th>RM48L952</th> </tr> <tr> <th colspan="2">Hercules HDK/MDK</th> </tr> <tr> <th>TMDX470MF066HDK</th> <th>TMS470MF06607</th> </tr> <tr> <th>TMDX570LS12HDK</th> <th>TMS570LS1227</th> </tr> <tr> <th>TMDS570LS31HDK</th> <th>TMS570LS3137</th> </tr> <tr> <th>TMDX570LC43HDK (device: TMS570LC4357)</th> <th>TMS570LC43xx</th> </tr> <tr> <th>TMDX570LS20SMDK</th> <th>TMS570LS20216ZWT</th> </tr> <tr> <th>TMDXRM42HDK</th> <th>RM42L432</th> </tr> <tr> <th>TMDXRM46HDK</th> <th>RM46L852</th> </tr> <tr> <th>TMDSRM48HDK</th> <th>RM48L952</th> </tr> <tr> <th>TMDXRM57LHDK (device: RM57L843)</th> <th>RM57L8xx</th> </tr> </table> ## 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. <table id="stl01"> <tr> <th> Board </th> <th> Setting </th> </tr> <tr> <th colspan="2">Simplelink Wireless MCU Development Kits</th> </tr> <tr> <th>C2538DK</th> <th>CC2538F53</th> </tr> <tr> <th>CC2650DK</th> <th>CC2650F128</th> </tr> </table> ## 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. <table id="stl01"> <tr> <th> Board </th> <th> Setting </th> </tr> <tr> <th colspan="2">Simplelink MCU LaunchPads</th> </tr> <tr> <th>MSP-EXP432E401Y</th> <th>MSP432E401Y</th> </tr> <tr> <th>MSP-EXP432P4111</th> <th>MSP432P4111</th> </tr> <tr> <th>MSP-EXP432P401R</th> <th>MSP432P401R</th> </tr> <tr> <th colspan="2">Simplelink Wireless MCU LaunchPads</th> </tr> <tr> <th>LAUNCHXL-CC1310</th> <th>CC1310F128</th> </tr> <tr> <th>LAUNCHXL-CC1312R1</th> <th>CC1312R1F3</th> </tr> <tr> <th>LAUNCHXL-CC1350</th> <th>CC1350F128</th> </tr> <tr> <th>LAUNCHXL-CC1352R1</th> <th>CC1352R1F3</th> </tr> <tr> <th>LAUNCHXL-CC2650</th> <th>CC2650F128</th> </tr> <tr> <th>LAUNCHXL-CC2640R2</th> <th>CC2640R2F</th> </tr> <tr> <th>LAUNCHXL-CC26X2R1</th> <th>CC2652R1F</th> </tr> <tr> <th colspan="2">Simplelink Wi-Fi MCU LaunchPads</th> </tr> <tr> <th>CC3220S-LAUNCHXL</th> <th>CC3220S or CC3220S_SWD</th> </tr> <tr> <th>CC3220SF-LAUNCHXL</th> <th>CC3220SF or CC3220SF_SWD</th> </tr> <tr> <th colspan="2">Simplelink Wireless SensorTags</th> </tr> <tr> <th>CC-DEVPACK-DEBUG (SimpleLink SensorTag Debugger DevPack)</th> <th>CC1310F128 or CC2650F128</th> </tr> <tr> <th colspan="2">Hercules LaunchPads</th> </tr> <tr> <th>LAUNCHXL2-TMS57012</th> <th>TMS570LS1224</th> </tr> <tr> <th>LAUNCHXL2-570LC43 (device: TMS570LC4357)</th> <th>TMS570LC43xx</th> </tr> <tr> <th>LAUNCHXL2-RM46 (RM46)</th> <th>RM46L852</th> </tr> <tr> <th>LAUNCHXL2-RM57L (device: RM57L843)</th> <th>RM57L8xx</th> </tr> </table> ## 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. <table id="stl01"> <tr> <th> Board </th> <th> Setting </th> </tr> <tr> <th colspan="2">C2000 eZdsp kits</th> </tr> <tr> <th>eZdspF2808</th> <th>EZDSPF2808</th> </tr> <tr> <th>eZdspF2812</th> <th>EZDSPF2812</th> </tr> <tr> <th>eZdspF28335</th> <th>EZDSPF28335</th> </tr> <tr> <th>eZdspF28044</th> <th>EZDSPF28044</th> </tr> <tr> <th colspan="2">C5000 DSP Starter Kits</th> </tr> <tr> <th>DSK5416 (device: TMS320VC5416)</th> <th>DSK5416</th> </tr> <tr> <th>DSK5509A (device: TMS320VC5409A)</th> <th>DSK5509A</th> </tr> <tr> <th>DSK5510 (device: TMS320VC5510)</th> <th>DSK5510</th> </tr> <tr> <th colspan="2">C5000 Evaluation Modules</th> </tr> <tr> <th>EVM5505 (device: TMS320C5505)</th> <th>EVM5505</th> </tr> <tr> <th>EVM5515 (device: TMS320C5515)</th> <th>EVM5515</th> </tr> <tr> <th>EVM5517 (device: TMS320C5535)</th> <th>EVM5517</th> </tr> <tr> <th colspan="2">C6000 DSP Starter Kits</th> </tr> <tr> <th>DSK6713 (device: TMS320C6713)</th> <th>DSK6713</th> </tr> <tr> <th>DSK6416 (device: TMS320C6416)</th> <th>DSK6416</th> </tr> <tr> <th>DSK6455 (device: TMS320C6455)</th> <th>DSK6455</th> </tr> <tr> <th colspan="2">C6000 Evaluation Modules</th> </tr> <tr> <th>EVM6455 (device: TMS320C6455)</th> <th>EVM6455</th> </tr> <tr> <th>EVMC6424 (device: TMS320C6424)</th> <th>EVMC6424</th> </tr> <tr> <th>EVMC6474 (device: TMS320C6474)</th> <th>EVMC6474</th> </tr> <tr> <th>EVMDM6437 (device: TMS320DM6437)</th> <th>EVMDM6437</th> </tr> </table> 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. <table id="stl01"> <tr> <th> Board </th> <th> Setting </th> </tr> <tr> <th colspan="2">Sitara Evaluation Modules</th> </tr> <tr> <th>EVMOMAPL137 (device: OMAPL137)</th> <th>EVMOMAPL137</th> </tr> <tr> <th>EVMAM1707 (device: AM1707)</th> <th>EVMAM1707</th> </tr> </table> ## 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. <table id="stl01"> <tr> <th> Board </th> <th> Setting </th> </tr> <tr> <th colspan="2">C6000 Evaluation Module</th> </tr> <tr> <th>TMDSEVM6657LS</th> <th>TMS320C6657&lowast;</th> </tr> <tr> <th colspan="2">Keystone 2 Industrial Communications Engine</th> </tr> <tr> <th>K2GICE (device: 66AK2G02)</th> <th>K2GICE</th> </tr> <tr> <th colspan="2">Keystone 2 Evaluation Modules</th> </tr> <tr> <th>EVMK2G (device: 66AK2G02)</th> <th>K2GEVM</th> </tr> <tr> <th>EVMK2H</th> <th>66AK2H12&lowast;</th> </tr> <tr> <th>EVMK2HX</th> <th>66AK2H12&lowast;</th> </tr> <tr> <th>EVMK2L</th> <th>66AK2L06&lowast;</th> </tr> <tr> <th>EVMK2EX</th> <th>66AK2E05&lowast;</th> </tr> </table> *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: <tt>C:\ti\ccsv8\ccs_base\emulation\boards</tt> Note: check the section [[GSG:Adding GEL files to a target configuration v5]] for additional details. <table id="stl01"> <tr> <th> Board </th> <th> Setting </th> </tr> <tr> <th colspan="2">C6000 Evaluation Modules</th> </tr> <tr> <th>TMDSEVM6472LE (device: TMS320C6472)</th> <th>EVMC6472</th> </tr> <tr> <th>TMDSEVM6457LE (device: TMS320C6457)</th> <th>TMDSEVM6457L</th> </tr> <tr> <th>TMDSEVM6670LE</th> <th>TMS320C6670&lowast; </th> </tr> <tr> <th>TMDSEVM6657LE</th> <th>TMS320C6657&lowast;</th> </tr> <tr> <th>TMDSEVM6678LE</th> <th>TMS320C6678&lowast;</th> </tr> </table> *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 <pre><code> 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 </code></pre> 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. <hr>  <div id="footer"></div>