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.
Tool/software: Code Composer Studio
Is there a way to use the CPU utilization analysis tools in CCS (Tools->RTOS Analyzer->Load Analysis->CPU Load / Task Load) on a binary that was NOT debugged from within Code Composer Studio?
i.e. If I just have a binary file that I want to run on the CC1352p1 board, can I still use those tools to analyze what's happening? Is there a way for me to just flash the binary from within CCS and use these tools?
HI Samyukta,
I don't recall this feature being supported. Have you made attempts to do this? If so, what did you observe?
Derrick
Hi Derrick,
Thanks for your response.
I managed to include a binary file (which I compiled from within CCS using the TI toolchain with just the function of interest) into another CCS project without the source code, including only the object file and the header file. I was able to debug the project, step through the functions, and step into the function of interest and view its source code (in debug mode) even though it was not included anywhere in the project.
This is when the function was compiled within CCS using the same toolchain. Would it be possible to include and debug a binary whose source code or compiler I do not know or have?
Warm regards,
Samyukta
Samyukta,
My guess is this is possible as long as the binary includes dwarf information that the debugger can interpret.
As far as the Load Analyzer tool, I would need to check with a CCS expert.
Derrick
Hi Samyukta,
First your application must be enabled to have the kernel log the necessary records to get the execution graph to work. You can take a look at the SimpleLink Academy (SLA) TI-RTOS Basics lab for instructions on how to do this.
If you have that working, you have three options
1. Let the target run and then connect CCS. Load the symbols of the .out that is running on the target. Note: don't load the image...just the symbols. You can then start execution graph as noted in the SLA lab.
2. You can configure the application to send out log records via the UART. Then in CCS instead of connecting to the target, you can open a UART based System Analyzer session. This method is more complicated. It also requires more code footprint on the target.
3. You can configure the application to write the records to persistent memory (e.g. flash or an SD card). Then place the log records into a binary file (e.g. use CCS to copy the flash memory into a binary file). Then you can import the binary data into System Analyzer for the execution graph. Again this method is more complicated.
I'd recommend option 1 if you are able to connect CCS to the target.
Todd