Part Number: MSP432P401R
Tool/software: Code Composer Studio
The following repeatably causes a crash:
- CCS 9.1.0.00010 running under Ubuntu 18.04.3 LTS
- Trace Analyzer 4.1.0.201905081124 com.ti.dvt2.trace.ccs.feature.group
- TI Emulators 8.2.0.00004 com.ti.emulation.pack.linux.feature.group
- CCS MSP432 Flash files 8.1.4 com.ti.msp432.flash_files.feature.group
- The environment variable TI_TRACE_LOGGING set to 6 to enable trace logging
- 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"
- Using the outofbox_msp432p401r_MSP_EXP432P401R_tirtos_ccs example from "SimpleLink MSP432P4 SDK - v:3.20.00.06"
The aim was to the use the trace logging to see what the XDS110 SWO baud rate was set to when the Hardware Trace Analyser - Interrupt Profiling was used. However, the act of enabling trace logging causes CCS 9.1 under Linux to crash when the debug session is started, before the program halts at main and before had a chance to start the Hardware Trace Analyser.
The crash doesn't occur if either:
a. Run CCS 9.1 under Linux but without enabling trace logging, and can successfully use Hardware Trace Analyser - Interrupt Profiling.
b. Run CCS 9.1 under Windows 10 with trace logging enabled, and can successfully use Hardware Trace Analyser - Interrupt Profiling with trace logging enabled (which reported the SWO baud rate was 12 MHz).
The attached log file contains the CCS crash dump and trace logging capture prior to the crash. From looking at the the crash dump with minidump_stackwalk the crash was due to a SIGSEGV in libct470api.so + 0x3eeff.
