Other Parts Discussed in Thread: OMAPL138
Tool/software: Code Composer Studio
When using the following I am getting CCS consistently crashing when attempt to use the hardware trace analyser to collect PC trace of the OMAP-L137 ARM9 core using the ETB:
- 9.0.1.00004 running in Ubuntu 18.04.2 LTS
- TI Emulators 8.1.0.00012
- OMAP-L137 on a MCBTMS570
- Blackhawk USB560-M, 20 pin JTAG cable
Steps to reproduce are:
- Download program which stops at main
- Use Hardware trace analyser to select PC trace using the ETB, selecting defaults.
- Step the program and CCS crashes.
Setting the environment variable TI_TRACE_LOGGING=6 before starting CCS shows the following final output on the console when CCS crashes:
M 15:03:40:827 | ETB Data Source: ELAPSED TIME Data Source, time to collect trace data + ICE, , , 0.000015 *** buffer overflow detected ***: /home/mr_halfword/ti/ccs901/ccs/eclipse/ccstudio terminated
From a quick decode of the .dmp file generated when CCS crashes, libc-2.27.so is exiting CCS with a SIGABRT, when the C run time library was called from libEtmHistTI.so
71d0e5f9-6cb4-3b19-54e6db5c-48d25bb1.zip contains the .dmp file from one crash, along with the cTools/Trace log.
OMAP_l137_hello_ARM.zipis the simple "hello world" program used to create the crash. Originally I was getting the CCS crash attempting to use PC trace with one of the ti-processor-sdk-rtos-omapl137-evm-05.03.00.07 examples, but repeated the crash on a simple example.