• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 1865 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/TM4C1294KCPDT: CCS crashes every time I try to launch a debug session [CCSv7]

Oliver Douglas
Prodigy 180 points
Part Number: TM4C1294KCPDT
Other Parts Discussed in Thread: SEGGER, AM3352

Tool/software: Code Composer Studio

Hello,

I am using CCSv7 on Linux with a TM4C1294KCPDT and the J-Link EDU Mini. This set up worked fairly well for a few days (once or twice CCS froze while trying to launch the debugger).

Something changed. The past five or so times that I have tried launching a debug session, CCS abruptly crashed. I rebooted my computer and tried again, but this did not help. I am including the most recent crash log.

Thanks!

2fc0de5f-9042-e409-28df4424-4310e5b8.log

PS: I had to rename the '.dmp' file to a '.log' suffix to post it... this seems a bit silly.

  • 0
    Guru 92251 points

    Oliver Douglas said:
    I am using CCSv7 on Linux with a TM4C1294KCPDT and the J-Link EDU Mini.

    I did report CCS/AM3352: CCS 7.2.0.00013 under Ubuntu 16.04 crashes with SIGABRT when attempt to use Segger J-Link support v6.16.7.0 to debug an AM3352, in which the cause of the problem seemed to be inside the Segger J-Link driver (as opposed to CCS). The crash seemed to be sensitive to the program being debugged, as opposed to a hard fault.

    Oliver Douglas said:
    I am including the most recent crash log.

    Do you know how to analyse a crash dump file?

    I haven't been able to determine if the cause of your crash dump is for the same reason as my crash in the referenced thread, as so far have been unable to find how to analyse the minidump crash dump files CCS under Linux saves.

  • 0 in reply to Chester Gillon
    Guru 92251 points

    Chester Gillon said:
    I haven't been able to determine if the cause of your crash dump is for the same reason as my crash in the referenced thread, as so far have been unable to find how to analyse the minidump crash dump files CCS under Linux saves.

    https://www.chromium.org/developers/decoding-crash-dumps has a download link to the minidump_stackwalk program which can decode the minidump crash dump files saved by CCS.

    Oliver Douglas said:
    I am including the most recent crash log.

    For both my crash example and your example, the crash reason is SIGABRT from JLINK2GTIAdapter.dvr. The stack backtrace is not exactly the same, suspect due to not exactly the same versions of software.

  • 0 in reply to Chester Gillon
    Prodigy 180 points
    Chester,

    That is an interesting find. I guess I'll go back to using my launchpad ICDI probe, since it seems like it may be a while before Segger fixes the problem.

    Thanks
  • 0 in reply to Oliver Douglas
    Guru 92251 points

    Oliver Douglas said:
    I guess I'll go back to using my launchpad ICDI probe, since it seems like it may be a while before Segger fixes the problem.

    Installing the latest CCS update for SEGGER J-Link Support (Linux) 6.20.7.0 has stopped CCS 7.2 and CCS 7.3 under Ubuntu 16.0.4.LTS from crashing when debugging an AM3352 with a Segger J-Link.

    The Segger J-Link release notes report that the following fix was made in Version V6.20d (2017-09-29):

    12. J-Link TI CCS plugin: Under certain conditions, e.g. using an AM335x device, starting a debug session did not work. Fixed.

    Does updating your CCS installation to SEGGER J-Link Support (Linux) 6.20.7.0 prevent the crashes?

    [My CCS 7.2 and 7.3 installations were previously using SEGGER J-Link Support (Linux) 6.18.0.0 or 6.14.0.e which were suffering from a crash]