CCS version 12.4.0
SDK version 0804
freeRTOS+Linux
When I finished loading the symbol table, I saw the following information
Why can't I see normal function information , What causes this problem
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 version 12.4.0
SDK version 0804
freeRTOS+Linux
When I finished loading the symbol table, I saw the following information
Why can't I see normal function information , What causes this problem
Hi,
Why can't I see normal function information , What causes this problem
What do you mean by normal function information? From the trace it looks like your application has already completed the execution and it is in ideal function, which is expected. If you want the CCS to halt at a specific point in your application, while you are loading the application from a Bootloader/U-boot, you can add big loops for that. Please refer the FAQ at https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1121933/faq-tda4vm-debugging-sbl-boot-in-rtos-sdk
Regards,
Parth
Yes, I see what you mean, but my application is working, not complete. Normal function information means that I should be able to see the call stack information for my application, but the problem is that I can only see vApplicationIdleHook
The SDK version of 0703 is normal as shown below, The issue is currently only on version 0804, so I wonder if it is due to the difference between freeRTOS and tirtos
Hi,
Are you building the application in debug mode? If not, can you please try building and loading the debug version of the binary?
Regards,
Parth
hi, i rebuild the mcu2_1 in debug mode, but i can still only see vApplicationIdleHook,
I can confirm that the program on the board is the same as the program of CCS load symbols
Finally, I found out that the SDK0804 version of the compiler had become llvm, and I wondered if the problem was related to the compiler change
Hi,
Finally, I found out that the SDK0804 version of the compiler had become llvm, and I wondered if the problem was related to the compiler change
No that should not be an issue. Can you try loading this directly via CCS and see if you can see the call stack.
Regards,
Parth