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.

CCS crash while debugging

Other Parts Discussed in Thread: CC1352P

My customer has encountered CCS crash during debugging, it frequently occurs when attempting to use breakpoints to debug.

Please find the dmp file as attached, the exception code is 0x80000003 "a breakpoint was encountered".

Please help advice how this can be fixed, thanks!

hang_34_bc967e05-1581-4d09-aa94-4cbfb006ebb9.dmp

Best regards,

Shuyang

  • Hello,

    I see that the customer is using CCS 12.0.0. What device is being used while debugging? And what compiler version was used compile the application?

    it frequently occurs when attempting to use breakpoints to debug.

    If a breakpoint is not explicitly set, there is no crash (target can run, halt, etc)?

    Thanks

    ki

  • Hi Ki,

    This issue has been resolved, the ccxml file was accidently modified, the issue goes away after changing to the normal ccxml.

    The issue still exists in customer's project, but not in SDK example. In customer's project, everytime the program runs to the breakpoint CCS will crash.

    The device is CC1352P, compiler version is TIClang v2.1.0. No issue has been discovered when target is running or pausing), but 100% to happen at the breakpoint.

    Regards,

    Shuyang

  • The device is CC1352P, compiler version is TIClang v2.1.0.

    There are some known issues with that version of the clang compiler where the generated debug symbols could crash CCS:

    https://sir.ext.ti.com/jira/browse/EXT_EP-10863

    Could the customer try using clang compiler 2.1.2? 

    Thanks

    ki

  • Hi Ki,

    The customer has tried TIClang v2.1.2 but the issue remains.

    The customer has a UART callback in his program, in which a semaphore is released and relavant action is performed in the main task. The program can run without a breakpoint, but when he tried to add a breakpoint in the main task where the relavant action is taken, CCS crashed.

    Any other suggestions? Thanks.

    BR,

    Shuyang

  • Hi Shuyang,

    The dmp file you provided did not help us understand the problem unfortunately.  Would you be able to ask the customer for the following:

    * When the customer says CCS crashes, do they mean that CCS exits when the problem occurs or does CCS become unresponsive and need to be killed off from the task manager?

    * Could the customer check if there are any additional dmp files being generated?

    * Could the customer also generate a debugger log? Instructions are available here: https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html.  Log files can be huge. We can provide a shared folder if they don't have any way to share the log file.

    Thank you!

  • Hi Andy,

    * CCS became unresponsive when the issue happens, after killing it manually and restart, CCS reported the dmp file.

    * I collected all dmp files from the customer, some of them cannot be opened on my computer, but in all that can be opened the error code are the same. I attach the files, would you please check if you can find anything?

    1362.dmp.7z

    * By debug log do you mean the Eclipse Debug Logs? I will ask the customer to help generate this log and get back to you.

    BR,

    Shuyang

  • Hi Shuyang,

    By debugger log I mean the "Debug Server Log".  The Eclipse debug log probably will not help much.

    Thank you for the other information.