This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320F2800137: XDS110 looses connection sporadically

Part Number: TMS320F2800137
Other Parts Discussed in Thread: LAUNCHXL-F2800137

We're having a annoying problem where the JTAG interface sometimes loses connection during debugging, which is highly annoying.

We're using a custom hardware board with a 14-pin JTAG connector. We program using a flatcable from the 14-pin connector on the XDS110 embedded on the LAUNCHXL-F2800137

The JTAG pinning has been designed based on page 84 of the datasheet. Which is also the same as the pinning in the hardware design guidelines.

However, very sporadically, we get the following error and the device disconnects.

C28xx_CPU1: JTAG Communication Error: (Error -1135 @ 0x8BA11) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.13.0.00201) 
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

I've read in the datasheet that the connection between the 14-pin XDS connector and the pins on the micro shouldn't be longer than roughly 15cm's. Mine are 19cm's. Does this make a big enough difference to sometimes loose connection? If so, i'll make a shorter connector. The pinning is correct and im using high quality flat cables.

Here is the pinning on the hardware design:

  • Hi,

    It's possible that the length of your traces is an issue, in which case it would help to shorten the trace lengths or add a buffer. It may also help to lower the TCK frequency.

    Is it possible that noise from your application is affecting your connection? Could you try looking at your signals with an oscilloscope while your application is running? 

    Best Regards,

    Ben Collier