• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 875 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 11.0.0.00012 under Linux crashes when attempt to use data variable trace

Chester Gillon
Guru 92251 points

Other Parts Discussed in Thread: MSP-EXP432E401Y, MSP432E401Y, LAUNCHXL-F280049C

The attached example causes CCS 11.0.0.00012 under Ubuntu 18.04.6 LTS to reliably crash.

The sequence is:

1. Download program to a MSP-EXP432E401Y.

2. With the program halted at main select menu option Tools -> Code Analysis -> Event Analysis (hardware events and messaging)

3. In the Configure Event Profile select Variable Profile and enter trace_var as the variable name. The address in hex is reported, indicating the address of the global variable has been resolved:

4. Select OK on the above dialog, and select Start Capture in the Event Analysis window.

5. Select Resume for the debugger, and CCS crashes.

An example dmp file from a crash is attached

4e16fba0-75bb-4f96-e9607d9e-460b9bad.zip

And the example project used.

MSP432E401Y_tracer.zip

I can't repeat the crash with CCS 11 under Windows 10.

  • 0
    Guru 92251 points

    Attached is another crash dump, which may be related.

    Sequence was:

    1. Using the same CCS 11 workspace as used to create the above test.

    2. In the workspace created a program for a LAUNCHXL-F280049C.

    3. Started a debug session for the program on the LAUNCHXL-F280049C, and CCS prompted that the XDS110 firmware on the launch pad needed updating.

    4. Selected to update the XDS110 firmware. Noticed that the Event Analysis view from the previous test was on display with a message indicate the view wasn't applicable to a C28xx CPU. Went to close the Event Analysis view.

    5. CCS 11 crashed while the XDS110 firmware update was in progress.

    6. The XDS110 was left in DFU mode, and had to run the following to recover the XDS110:

    mr_halfword@Haswell-Ubuntu:~/ti/ccs1100/ccs/ccs_base/common/uscif/xds110$ ./xdsdfu -f firmware_3.0.0.18.bin -r

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated.  All rights reserved.

Scanning USB buses for supported XDS110 devices...

Downloading firmware_3.0.0.18.bin to device...

    Not sure if the crash was related to closing the Event Analysis view or not.

    d7885cc2-526c-401c-ae0961a9-21f12f57.zip

  • 0
    TI__Guru**** 476741 points

    Hello Chester,

    I can reproduce the crash on my Ubuntu 18.04LTS VM. One question:

    Chester Gillon said:

    4. Select OK on the above dialog, and select Start Capture in the Event Analysis window.

    5. Select Resume for the debugger, and CCS crashes.

    If you skip step 4 and instead resume the debugger (and have the capture start automatically when the debugge resumes), do you still see a crash?

    Thanks

    ki

  • 0 in reply to Ki
    Guru 92251 points
    Ki said:
    If you skip step 4 and instead resume the debugger (and have the capture start automatically when the debugge resumes), do you still see a crash?

    I will try that at the weekend, when next have access to the launchpad and PC.

  • +1 in reply to Chester Gillon
    TI__Guru**** 476741 points

    In any case, I can definitely reproduce the crash when following your steps (start collection first, then run the target).

    I filed a bug for this. Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-10675

    Thanks

    ki

  • 0 in reply to Ki
    Guru 92251 points
    Ki said:

    If you skip step 4 and instead resume the debugger (and have the capture start automatically when the debugge resumes), do you still see a crash?

    I tried several times, and confirm that skipping 4 avoids the crash.