• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 189 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CODECOMPOSER: V20.3 Crashing routinely while debugging on hardware

JT
Prodigy 80 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: TMS320F280041

Tool/software:

It seems like 1 out of 5 attempts to debug project fails, getting hung up somewhere along the way. This can be rebuilding while in an active debug session, debugging project from a restart of CCS, etc. At the point of hangup, I cannot stop or pause the active debug session. I close CCS, and upon restarting CCS, a crash report is generated.

I have tried deleting the workspace cache, which seemed like an improvement, but the problem is persistent. I don't understand if this is common (seems unlikely) or if there's something problematic with my setup.

CCS is running on Windows 11 Pro and I'm working on custom hardware using the TMS320F280041.

Thanks in advance.

  • 0
    TI__Guru**** 472411 points

    Hello,

    When it gets stuck, is there any message in the lower right corner like "Initializing device registers" or "re-connecting to TI Cloud Agent"?

    JT said:
    I close CCS, and upon restarting CCS, a crash report is generated.

    Can you attach this crash file? It is also known as a "debug server dump" file. Please see the below document for more details:

    https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 80 points

    Thanks for the quick reply.

    I enabled the Debug Server Log but haven't had an issue since posting. I replaced the USB cable to the XDS200 and the issue appears to be resolved. Seems there was an unreliable connection to the emulator and CCS wasn't handling it so gracefully.

    To answer your question, there were different messages depending on the which process CCS got hung up on. Sometimes no messages at all except that a debug session was already running when I tried to stop and start a new one.

    I'll mark this one as resolved.