• State Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 12 replies
  • Subscribers 32 subscribers
  • Views 381 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.

Original question:

CCS crash while debugging

MCU-PLUS-SDK-AM243X: CCS 12.1.0 crashes while debugging

Teja Poorna
Prodigy 115 points
Part Number: MCU-PLUS-SDK-AM243X
Other Parts Discussed in Thread: AM2432

Hello TI,

Currently, we are facing an issue with the CCS as it crashes while debugging through the project. It is our own project in which we are using AM2432 MCU.

The CCS crashes without any notification and we are not able debug the code.

We are facing the issue, When stepping through the code in specific files or functions.

Are they any known issues or workarounds to solve this problem, as this is blocking us now for the further development.

Thanks in advance

BR

Teja

  • 0
    TI__Genius 16490 points

    Is TI ARM Clang being used?  If so, can you tell me what version?

    This is a good chance this may be due to this issue: https://sir.ext.ti.com/jira/browse/EXT_EP-10863

    If you are using the Clang compiler and are not using the latest version, please try updating.

    If this potential cause is not likely, would you be able to attach any crash dump files that have been created?  They can be found by opening the Help -> CCS Support menu.

  • 0 in reply to AndyW
    Prodigy 115 points

    Yes, we are using the updated version of TI Clang Compiler 2.1.2 LTS. Currently there are no dump files available.

  • 0 in reply to Teja Poorna
    TI__Genius 16490 points

    In the absence of any crash dump files, would you be able to generate a Debug Server Log of the activity that leads up to the crash?  There is some information here for how to do this: https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html

    These logs can get very large but compress well with 7z.. If needed, I can provide a private location to upload it to.

    Also, if you are able to provide a .out and approximate location file where the problems occurs, that may also be helpful. As for the log file, I can provide a private location to unload this to.

  • 0 in reply to AndyW
    Prodigy 115 points

    Hi Andy,

    I am able to create the Debug Server Log file as the application crashes. Could you please let me the location, where can i upload the Debug Log file?

  • 0 in reply to Teja Poorna
    TI__Genius 16490 points

    Hi Teja,

    You can use this link with access code "NmW,12QT". This is an upload-only link.

  • 0 in reply to AndyW
    Prodigy 115 points

    Thanks a lot andy for providing the link. I have uploaded the Debug server log file to the link above. Please have a look at it.

    Looking forward to your reply.

  • 0 in reply to Teja Poorna
    TI__Genius 16490 points

    Got it. Will get back to you.

  • 0 in reply to AndyW
    TI__Genius 16490 points

    Hi Teja, could you describe what operation was being performed when the crash occurred?  When it crashes, does CCS just disappear, hang, or something else?  Thanks!

  • 0 in reply to AndyW
    Prodigy 115 points

    When I step into a particular function, the CCS just disappear(i.e. it closes automatically the ccs studio)

  • +1 in reply to Teja Poorna
    TI__Genius 16490 points

    We had a look through the log but did not reach any conclusions.  We have some suggestions that may help us narrow this down further. The log shows the disassembler active right near the end which leads us to ask if you could close as many open CCS windows (or views) as possible during the test case.  Closing the windows will reduce the number of actions occurring within the IDE as you step through the code. Assuming the crash still occurs, would you be able to upload another log showing this?  If the crash does not occur, then opening one window at a time may provide some insight into which area is causing the issue.

    Crash dump files are generated for most crashes. We are aware of threads in the process that can throw exceptions which are not caught and do not create dump files. These could cause the issue you see. These threads rarely cause problems though and don't seem to be associated with the stepping operation. If we're not getting useful logs from the above actions then the next step would be schedule a support call with you so can try to work through some possibilities (and assuming you would be open to this).

  • 0 in reply to AndyW
    TI__Genius 16490 points

    Hi Teja, I'm glad the issue was resolved for you.  Could you comment further on what resolved it?  We can try to reproduce the issue here if, for example, you knew which window was causing the problem.

  • 0 in reply to AndyW
    Prodigy 115 points

    Hi Andy, As mentioned above by you, I created a new project workspace in ccs studio and created a target configuration of my own for debug purpose without importing the project into the workspace. Then launched select configuration, connected to target and Load symbols for the debugging. Then I was able to successfully debug it the function, that has been crashing the ccs studio previously.