Troubleshooting C2000 Debugger Connection Issues

From Texas Instruments Wiki
Jump to: navigation, search

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

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.
  • If the connection seems unstable, make sure that a pull-down resistor (2.2kohm is typically adequate) is tied to TRSTn. For stability, pull-up resistors (~4.7kohm) should also be placed on EMU0 and EMU1 if applicable.

Confirm that your Target Configuration is Correct

The next step is to make sure that CCS is configured to connect to the correct MCU with the correct emulator.

On custom boards this is pretty self-explanatory, but for C2000 evaluation kits the emulator is often on one of the boards.

The following is a list of C2000's basic evaluation kits and what their respective target configuration should be so that you may connect Code Composer Studio with the MCU. Also listed are any cable and switch settings that you may need to be aware of. More exhaustive information on each kit can be found within each kit's folder inside controlSUITE.

In more advanced application kits, the hardware setup can be more complicated. Please use the quick start guide and/or user's guide that was designed around the kit. These documents can also be found within controlSUITE.

Kit Name Description Emulator MCU Notes Type
TMDSDOCK28027 F28027 Experimenter's Kit xds100v1 TMS320F28027 USB standard-B cable should be plugged into the Docking Station.

LD1 on the controlCARD and LD1 on the Docking Station should both be on.
J8 on Docking Station should not be jumpered.

DIMM100
TMDSDOCK28035 F28035 Experimenter's Kit xds100v1 TMS320F28035 USB standard-B cable should be plugged into the Docking Station.

LD1 on the controlCARD and LD1 on the Docking Station should both be on.
J8 on Docking Station should not be jumpered.

DIMM100
TMDSCNCD28035 +
Docking Station
Isolated F28035
controlCARD +
Docking Station
xds100v1 TMS320F28035 USB standard-B cable should be plugged into the Docking Station.

USB mini-B cable should be plugged into the controlCARD.
SW3 on the controlCARD should be switched toward 'ON'.
LD1 and LD4 on the controlCARD and LD1 on the Docking Station should all be on.

DIMM100
TMDSDOCK28069 F28069 Experimenter's Kit xds100v1 TMS320F28069 USB standard-B cable should be plugged into the Docking Station.

LD1 on the controlCARD and LD1 on the Docking Station should both be on.
J8 on Docking Station should not be jumpered.

DIMM100
TMDSDOCK28335 F28335 Experimenter's Kit xds100v1 TMS320F28335 USB standard-B cable should be plugged into the Docking Station.

LD1 on the controlCARD and LD1 on the Docking Station should both be on.
J8 on Docking Station should not be jumpered.

DIMM100
TMDSDOCKH52C1 F28M35 Experimenter's Kit xds100v2 F28M35H52C1 USB standard-B cable should be plugged into the Docking Station.

USB mini-B cable should be plugged into the controlCARD.
SW3 on the controlCARD should be turned to the 'ON' position.
LD1 on the controlCARD and LD1 the Docking Station should both be on.

DIMM100
TMDSDOCK28M36 F28M36 Experimenter's Kit xds100v2 F28M36P63C2 USB mini-B cable should be plugged into the Docking Station.

USB mini-B cable should be plugged into the controlCARD.
A:SW1 on the controlCARD should be turned to the 'ON' position.
LD1 on the controlCARD and A:LD1 on the Docking Station should both be on.

HSEC180
TMDSDOCK28377D F28377D Experimenter's Kit xds100v2 TMS320F28377D USB mini-B cable should be plugged into the Docking Station.

USB mini-B cable should be plugged into the controlCARD.
A:SW1 on the controlCARD should be turned to the 'ON' position.
LD1 on the controlCARD and A:LD1 on the Docking Station should both be on.

HSEC180


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:

Debugview002.jpg

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

Debugview000.jpg

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

Debugview001.jpg

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:

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:

  1. 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),
  2. 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)