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.
JTAG configuration for CCS and Stellaris
This article will explain how to get started with using Code Composer Studio to debug a Stellaris device. For the latest information on CCS support for Stellaris please visit the Stellaris support in CCS topic.
If using XDS emulators, also refer to the Stellaris Emulator Compatibility page
On-Board Emulation connection
Stellaris Evaluation Kits and Development Kits have on-board emulators, and CCSv4.1.x/CCSv5 versions pre-install the device drivers for them. However, in certain occasions Windows may not recognize this installation. Therefore the instructions below indicate how to properly perform a manual installation.
Note: Reference design kits do not have embedded emulation. Consult the User's Manuals for details on how to properly connect and configure an external emulator.
- When you plug in the Evaluation Board for the first time, Windows starts the Found New Hardware Wizard and asks if Windows can connect to Windows Update to search for software. Select “No, not this time” and then click Next.
- Next, the Found New Hardware Wizard asks from where to install the software. Select “Install from a list or specific location (Advanced)” and click Next.
- Select “Search for the best driver in these locations,” and check the “Include this location in the search" option. Click Next. Browse to the following directory in the installation:
- CCSv4: <CCS_INSTALL_DIR>\ccsv4\emulation\drivers\stellaris\ftdi
- CCSv5: <CCS_INSTALL_DIR>\ccsv5\ccs_base\emulation\drivers\stellaris\ftdi
- Note: Some legacy boards may require the drivers located in the icdi directory (instead of ftdi) in the paths above.
- If a warning pops up during the Hardware Installation like the one below; click Continue Anyway.
- Windows finishes installing the drivers for “Stellaris Evaluation Board A.” When the driver install is finished, the Found New Hardware Wizard window appears like the one below. Click Finish to close the dialog box.
You have just installed the drivers for “Stellaris Evaluation Board A.” The USB device built into the EVB is a composite USB device. After you click Finish, a Found New Hardware Wizard appears asking to install drivers for another device. This is for the “Stellaris Evaluation Board B” part of the composite USB device. Follow the same instructions as above to install the drivers for this device.
The Found New Hardware Wizard appears one last time. This is to install the drivers for the “Stellaris Virtual COM Port.” Again, follow the same instructions to install the drivers for this device.
Now all of the hardware drivers for the Evaluation Board have been installed. These drivers give the debugger access to the JTAG interface and the host PC access to the Virtual COM Port.
External Emulator Connection
- The TMDSADPEMU-20A 20-Pin ARM Adapter to 14-pin TI Emulation Adapter needs to be used in order to connect to the Stellaris EVM with a XDS510 based emulator. Take care to ensure that the adapter is connected to the board in the proper direction. Pin 1 on the board should meet pin 1 on the adapter. Pinout is available at JTAG Connectors
- The Stellaris device does not pin out the RTCK signal, which the TI emulators need. So, there are two ways around this.
- Short Pin 9 and Pin 11 together on the 20-pin header (J1), so that TCK is fed back into RTCK. This can be done with a small jumper wire (see picture).
- use the software configurable feedback loop which allows the emulator to use TCK as RTCK. This is not supported on all emulators. Check your emulator documentation to see if it available and how to configure it on yours.
For emulator compatibility please check the page Stellaris_Emulator_Compatibility
Stellaris is first supported in CCS with v4.1.0. It is recommended that you follow the instructions in the QuickStart Guide
- If using CCS 4.1.3 through 4.2.3 and a LM3Sxxxx device, go to the 'Advanced' setup tab and make sure 'Access Port Designator' option for Cortex M3 is set to 0x02000000 (see picture). The TI default may be 0x02000003 which could result in a bad target silicon revision number error when you try to connect to a LM3S device.
- Note: this was fixed in CCS 4.2.4 and newer
- If using a TI or Blackhawk emulator, go to the 'Advanced' setup tab and make sure the 'Pseudo Address' option for the 'subpath' is disabled