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.

Unreliable connection with XDS110 debug probe.

Part Number: TMS320F280041


HI,
I am having an issue with the XDS110 Debug probe wherein the debugger randomly disconnects while the board is in operation. I am using a 4-wrie JTAG protocol with a 14-pin connector

A few observations about the problem.

  1. The problem occurs usually while the debugging session is in progress and not during code upoad.
  2. The time duration after which the disconnection happens is entirely random. Sometimes the connection will for fine for 5 minutes and on other occasions it fails within a few seconds.
  3. Swapping the cable from the debugger to the laptop or the cable from the debugger to the micro-controller does not solve the issue.
  4. After the debugger disconnects once it's not possible to enter a debugging session again unless I power cycle the micro-controller.

Console Log of the error.


C28xx_CPU1: Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.4.0.00129)
C28xx_CPU1: Trouble Halting TargetCPU: (Error -1135 @ 0x82469) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.4.0.00129)
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 debuggingng


Solutions to the issue and suggestions on how to make the connection more reliable will be appreciated

Regards,
Parth
WCB Robotics.

  • Hello Parth,

    We typically see these types of issues when the MCU is controlling some high-power FETs on the board. The switching noise from that activity can affect the emulator. An isolation device placed between the debugger and the system under test can often help. What is your system doing during the debug session?

  • Hi Gus,
    Thanks for your reply.
    During the debug session the micro-controller is doing the following.

    1. Analog voltage sensing on ADC A and B.
    2. Toggling  a few n-p-n transistors using GPIOs,

    The npn transistors have a base current limiting resistors and are toggled at a very low frequency, about once every 20-30 seconds. Also, there appears to be no co-relation between the GPIO's being toggled and the debugger disconnecting.

  • Thanks for the additional information.

    Some additional questions:

    • Is there any indication that the MCU is still executing code after the debug probe disconnects? For example, if your code continuously toggles an LED, do you see that LED continue to toggle?
    • Do you see the same problem on a different board?
    • Have you monitored the XRSn pin on the MCU to see if the MCU is going into reset?
    1. Yes, the MCU continues to execute the code even after the debugger has disconnected. There is a GPIO pin which I periodically toggle and this continues even after the disconnection has occurred.
    2. Yes, we have seen this problem on other boards as well.
    3. I'll monitor the XRSn pin from now on and update you on this.
  • Parth,

    You can also refer to the app note below for some suggestions on what to check for when debugging this issue.

    https://www.ti.com/lit/an/spracf0a/spracf0a.pdf