• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 709 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.

CCS/TMS320C6657: CCS 10 Crashes a lot.

lemmiwinks
Expert 1060 points
Part Number: TMS320C6657


Tool/software: Code Composer Studio

Never had problems with 7,8 or 9.  10 crashes several times a day on average.

  • 0
    TI__Guru**** 469201 points

    Hello,

    Do the crashes tend to occur when doing a specific action in CCS? Or is it pretty random? 

    If CCS is crashing during a debug session, there should be some crash dump files. Please provide any crash dump and eclipse error logs:

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

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1060 points

    It always happens right as the debugger starts to load.  For example I'll build the project and then it prompts "A file that you are debugging has been modified.  Do you want to reload this file?"  I click OK and then almost immediately CCS just terminates.  No messages, all windows simply close.

    I've been sending the crash logs when prompted after I start the program again.

    I'm using a Blackhawk USB560V2 System Trace Emulator.  It's been flawless under 7, 8, and 9.  Only started doing this under 10.  I have another development machine running CCS 8 and it never crashes.

  • 0 in reply to lemmiwinks
    TI__Guru**** 469201 points

    lemmiwinks said:
    always happens right as the debugger starts to load.  For example I'll build the project and then it prompts "A file that you are debugging has been modified.  Do you want to reload this file?"  I click OK and then almost immediately CCS just terminates.  No messages, all windows simply close.

    Ah ok. Crash dump files should be generated in this case

    lemmiwinks said:
    I've been sending the crash logs when prompted after I start the program again.

    Could you also attach them to this thread? This will help us analyze the issue faster.

    If the issue can be reproduce fairly consistently, a debug sever log would also help immensely. It is not enabled by default so you would need to explicitly enable it first:

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

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1060 points

    So it crashed a few times more today.  I'd attach the log file or email it to someone but the file is 147 GB!!!

  • 0 in reply to lemmiwinks
    TI__Guru**** 469201 points

    The raw debug server logs are usually pretty huge but 147GB is especially huge. It is recommended to enable logging right before the issue is expected to occur, and then disable it shortly after.

    The raw logs do compress very well when zipped. But at 147GB, not sure it can be compressed to a reasonable size.