• State TI Thinks Resolved
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 78 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

XDS110ISO-EVM: XDS110 Debug error

Tom M
Prodigy 205 points
Part Number: XDS110ISO-EVM
Other Parts Discussed in Thread: TM4C1294NCPDT

Tool/software:

Hi.,

 I am using TM4C1294NCPDT controller and XDS110 Debug Probe. Frequently i have Error connecting to the target this error. The following dialogue box popup while using debugger. I can't able to debug continuosly.

Kindly give me the solution for avoiding this erreo. If i change hradware or software for avoiding this? or else i will add protection circuit for this issue. Please guide me.

Thank you

  • 0
    TI__Guru**** 183476 points
    Tom M said:

     I am using TM4C1294NCPDT controller and XDS110 Debug Probe. Frequently i have Error connecting to the target this error. The following dialogue box popup while using debugger. I can't able to debug continuosly.

    Hi,

      What is the percentage of time that it shows with the error? My understanding from your description is that it sometimes work, correct?

      Your target device is TM4C129 and you are using an external XDS110 debug probe on your custom board. Is that a correct understanding?

      Can you try the XDS110 debug probe on another custom board if you have one? What is the result? This is to make sure it is not a one-off issue. 

      Can you try the XDS110 debug probe on a LaunchPad? What is the result? If you use XDS110 on a LaunchPad and never have the same error then it is likely a board level issue on your custom board particularly for the JTAG interface.

      In CCS, you can do a test connection. What is the result?

      

  • 0 in reply to Charles Tsai
    Prodigy 205 points

     What is the percentage of time that it shows with the error? 

    30%

    My understanding from your description is that it sometimes work, correct?

    Yes, Controller is in good condition but not able to debug, This occurrences came randomly.

     Your target device is TM4C129 and you are using an external XDS110 debug probe on your custom board. Is that a correct understanding?

    Yes

    Can you try the XDS110 debug probe on another custom board if you have one?What is the result? 

    Yeah i tried. Its working good.

    Can you try the XDS110 debug probe on a LaunchPad? What is the result? 

    Yeah i tried. Its working good.

    This connection information also in correct format.

    Thank you for your guidance.

    Actually this issue came randomly, Microcontroller is in good condition. Once i rework debugging connector(Which is placed in Our Custom PCB) it will debug sometimes.

    And my question is what is the reason for not debugging issue? If you have  any idea regarding this Please suggest!....

    Thanks in advance

  • 0 in reply to Tom M
    TI__Guru**** 183476 points
    Tom M said:

    Can you try the XDS110 debug probe on another custom board if you have one?What is the result? 

    Yeah i tried. Its working good.

    Tom M said:

    Can you try the XDS110 debug probe on a LaunchPad? What is the result? 

    Yeah i tried. Its working good.

    Tom M said:

    Actually this issue came randomly, Microcontroller is in good condition. Once i rework debugging connector(Which is placed in Our Custom PCB) it will debug sometimes.

    And my question is what is the reason for not debugging issue? If you have  any idea regarding this Please suggest!....

    Here you said that other boards will work fine. It is only one board that has random debugging problem. In this case, it is possible a board level issue. You might want to check if you have good soldering of the device. 

    Please also follow section 6 of this app note to debug JTAG failure. 

    Using TM4C12x Devices Over JTAG Interface

    If the problem persists, you can also do a ABA swap test. 

    • A-B-A Swap Method
      (1) Remove the suspected component (A) from the original failing board.
      (2) Replace the suspected component (A) with a known good component (B) and check if the original board now works properly.
      (3) Mount the suspected component (A) to a known good board and see if the same faliure occurs on the good board.

    Step 3 is important because it helps us to exclude any possibility that the issue is caused by a systemic issue or the interaction of multiple slightly bad components on a good board.