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.

debug sessioon hangs after while

Other Parts Discussed in Thread: AM3359

Hello,

I'm using TMS470F03107 with custom designed board and XDS200 usb debugger. I'm able to enter debug session and debug my code but after while (approx. less then 1-2 minutes)CCS hangs out and becomes not responsive untill i unplug the debugger. after which ccs restores and gives the following error: 

Memory Map Setup for Flash @ Address 0x0IcePick: Error: (Error -2172 @ 0x0) Unable to communicate with the emulator. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.1.507.0)
Dap: Error: (Error -2172 @ 0x0) Unable to communicate with the emulator. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.1.507.0)
CortexM3_0: JTAG Communication Error: (Error -2172 @ 0x0) Unable to communicate with the emulator. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.1.507.0)

CCS version 6 

i have noticed that duration for which i'm able to debug decreases as i increase TCK clock.

attached is the log files generated by ccs

6758..TI-trace.rar

  • Thank you for the trace logs. Can you also provide a debug server log?

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv6#Debug_Server_Logging

    Thanks

    ki

  • Hi Ki,

    This morning I solved the issue just by cleaning and heating the mcu so i guess it was some paste residue left from soldering the part or something similar causing the problem.

    Anyway many thanks for your reply to my question.

  • Hello Again,

    Unfortunatelly this problems seems to repeat it self periodically and i can't figure out the reason. Attached are the logs taken during the debug session problem. It is really frustrating that it keeps repeating itself every now and then.4034.Logs.rar

  • Did anyone had the chance to analyze the logs that I provided ??

    Many Thanks,

    Suat

  • Yes. We are able to see where the issue is occurring. We are still trying to determine the root cause.

    Are you using the profile clock?

    Thanks

    ki

  • No I'm not using profile clock.

    It is disabled when i check it from debug perspective Run->Clock menu... Also all the other clock sub menu items (enable, disable, show, hide, reset and setup) are disabled that is i can't even configure them.

    Many Thanks,

    Suat

  • Ok, thanks. There was some reference to a clock in the log, hence I was curious. The log is still under analysis.

    ki

  • Hi Ki,

    Does your analysis still continue??

    Suat

  • Hello TI Support Team,

    I reply to this thread, because I have the same problem. I am using the XDS200 with our custom design board, based on the AM3359. After about two minutes debugging the CCS hangs. Then I have to reset the board and disconnect the XDS200 and after about one minute, the CCS is responsible again. Then I have to plug and unplug the USB of the XDS200 about 3 times to establish a new debug session. I am using the Beagleboneblack too and with this one I can debug more than 15 minutes without problems. Especially debugging in the assembly view forces the hanging. I am searching already a long time for a solution.
    I tried many things like
    - different power supplies
    - shorter USB cable
    - lowering the frequency to 1MHz in the emulator configuration
    - updating to the latest emulator drivers
    - differnt CCS versions 5.5 and 6.0
    - ferrite around the JTAG and USB cable
    - disabling the semihosting flag under debug settings
    - reading the Blackhwak trouble shooting guide

    I enabled the server-log too, which becomes hundreds of megabytes in such a case.

    Is there anything else I can do to find the reason for this problem?

    Thanks in advance,
    Stephan
  • Hello Ki-Soo Lee,

    is there any new information about the problem described in this thread?

    Thanks in advance,
    Stephan
  • Hi Stephan,

    A similar issue was resolved by replacing the XDS200 emulator with another one. Apparently some of the XDS200 emulators are "flakey" and more prone to instability. I don't know if you have another emulator to try out... or even if it is of a different type (like XDS100) so we can confirm that the JTAG scan chain on the custom target is fine. You can also try running some of the more comprehensive dbgjtag tests to check for stability issues.

    If all else fails, you can try attaching your generated debug server log for the engineers here to take a look.

    Thanks

    ki