Introduction

This article is intended to help debug some common issues seen when connecting a debugger to a 28x device. Many of the other JTAG debug articles are also applicable to the C2000 family.

Other Resources

XDS100 Wiki article. In particular take a look at the troubleshooting section.
Debugging JTAG Connectivity Problems Wiki Article
E2E Community for Code Composer Studio

First Steps

Check the JTAG Connection

Make sure the emulator is correctly and firmly connected to the board connector.
If the device is in a socket, make sure the device is properly seated and had good contact with the socket.
The Debugging JTAG Connectivity Problems Wiki Article has many suggestions for determining if you JTAG is correctly connected and setup.

Code Composer Studio 4.x - Debug Session Doesn't Start

If you try to start a debug session in CCS 4 and it looks like the session started, but you don't see any disassembly, and the Target menu is mostly grey'ed out - then it may be because the debug window has been closed. Try the following:

Go to the debug perspective:

Then make sure the view->debug window is open:

The window looks something similar to this and displays the CPU's to be debugged. This example is a 2803x with CLA debug window:

On-Board XDS100 Issues

XDS100 Not Programmed

There is an issue with some of the C2000 Experimenter's kits that include the docking station with on-board USB JTAG emulation being recognized by Windows as "Dual RS232 USB Serial Bridge" instead of the TI XDS100 JTAG emulator. The USB emulation on the docking station is based on an FTDI USB Serial adapter chip that can act as a JTAG emulator when connected to an external EEPROM containing the emulation parameters. If the EEPROM is not programmed then the FTDI chip appears as a "Dual RS232 USB Serial Bridge". We believe there is an issue with some of the USB docking stations not getting programmed properly.

Please refer to this FAQ to check if your XDS100 is programmed properly.

Windows is recognizing the XDS100 as "Dual RS232 USB Serial Bridge" instead of the TI XDS100 JTAG emulator.

See this post on the C2000 E2E forums.

Also refer to this FAQ Please refer to this FAQ to check if your XDS100 is programmed properly.

2803x/2802x Specific

Code Composer Studio can not connect to a password protected device

A byproduct of the emulation code security logic is that when the device first powers up, before CCS is connected, the security logic may disable the JTAG. To prevent that from occurring use the "wait" boot mode that we have provided that emulates wait-in-reset mode.

Also refer to:

Code Security Module FAQ wiki article.
Emulation_Boot wiki article.

2833x/2823x Specific

Code Composer Studio can not connect to a password protected device

A byproduct of the emulation code security logic is that when the device first powers up, before CCS is connected, the security logic may disable the JTAG. To prevent that from occurring there are two solutions:

use an emulator that supports wait-in-reset (e.g., in SDconfig click on the Emu folder and check the "Perform C27x style Wait-In-Reset" box),
use a boot mode that we have provided that emulates wait-in-reset mode (loop to checkmode)

Also refer to:

Code security information - TMS320x2833x, 2823x System Control and Interrupts Reference Guide sprufb0
Boot mode information: TMS320x2833x, 2823x Boot Rom Reference Guide spru963(spru963)

For technical support on the C2000 please post your questions on The C2000 Forum. Please post only comments about the article Troubleshooting C2000 Debugger Connection Issues here.