Tool/software: Code Composer Studio
Hi,
Is there a way to upload code to the target device without running the debugger?
thank you,
Scott
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
Hi,
Is there a way to upload code to the target device without running the debugger?
thank you,
Scott
Ki-Soo, thank you for asking.
Well, what I meant is: let's say I want the code to be optimized for speed. But if there are debugging symbols, etc, embedded in the code by the debugger, won't that increase execution time? Also, when I build the project under "Release", CCS still allows me to debug the code. How is this possible if it's a release version? I just want to make sure I'm running the optimized code.
thank you,
Scott
scott said:But if there are debugging symbols, etc, embedded in the code by the debugger, won't that increase execution time?
The debug symbols have no impact on the the actual target execution of code. Those symbols are loaded only to the debugger and not the target. When a *.out file (which has both debug symbols and target code) is loaded by the debugger, the target code is loaded to just the target while the debug symbols are loaded just to the debugger.
scott said:Also, when I build the project under "Release", CCS still allows me to debug the code. How is this possible if it's a release version?
Unless debug symbols are fully stripped from the executable, you will always have some level of visibility - even for optimized code. The only issue is that the more optimization enabled, the more limited your debug experience is.
Please take a look at the below article. It should address your main questions:
Thanks
ki