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/MSP432P401R: CCS 9.1 Interrupt Analyzer view doesn't indicate when captured data has been affected by data loss due to SWO overflow

Part Number: MSP432P401R

Tool/software: Code Composer Studio

In CCS 9.1.0.00010 the Interrupt Analyzer view can display confusing information if the captured data has been affected by data loss.

E.g. in the following view:

There appears discrepancies since:

a. PENDSV is shown as "preempted" between markers X1 and X2 even though no other interrupt is shown as running during the time PENDSV is reported as having been preempted.

b. PENDSV is shown as apparently running for longer than expected starting from marker X1.

When look at the Trace Viewer "raw" SWO data at the timestamps corresponding to makers X1 and X3 there is a trace status of "OVERFLOW!" meaning that the trace capture has exceeded the SWO bandwidth and data has been lost:

Is it possible the Interrupt Analyzer view could display some warning if an overflow had occurred during the capture, so that the user is aware that the displayed data may be incorrect?

For this capture used:

- CCS 9.1.0.00010 running under Ubuntu 18.04.3 LTS
- MSP432P401R connected to a TMDSEMU110-U, with the probe set to provide 3.3V power and "SWD Mode - Aux COM port is target TDO pin"
- The Hardware Trace Analyzer Interrupt Profiling was started using all defaults
- Using the outofbox_msp432p401r_MSP_EXP432P401R_tirtos_ccs example from "SimpleLink MSP432P4 SDK - v:3.20.00.06"

A similar issue was reported in the original question, but I created this thread to show the issue with an unmodified TI example program.

Note that under Linux the XDS110 SWO baud rate is set to 4 Mbaud, but under Windows 10 the XDS110 SWO baud rate is set to 12 Mbaud. Therefore, running the test with CCS under Linux has a higher chance of causing an SWO overflow.

  • Chester,

    Thanks for reporting this. This interface is changing, but I am reporting this enhancement to be implemented in the next instance of this interface. 

    The number is DBGTRC-5148 and in about half hour it can be checked in the link SDOWP in my signature below. 

    I apologize for the inconvenience,

    Rafael