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:
Hello,
When stepping through SDK code I am able to locate a file on each debug session. In the example below, I can browse for the pmic folder and I am able to debug the source.
However, I can't seem to make this permanent by Source Lookup Path. What exactly do I have to put in the following dialogue to avoid the problem above please?
Hi Kier,
In the example below, I can browse for the pmic folder and I am able to debug the source.
Once you locate a file, the debugger should add this path to the source lookup paths and remember this for future debug launches. Is this not happening?
Also see slides 51-55: https://software-dl.ti.com/ccs/esd/training/ccs_tips-and-tricks.pdf
Thanks
ki
Hello Ki,
Thanks for the slides.
Once you locate a file, the debugger should add this path to the source lookup paths and remember this for future debug launches. Is this not happening?
Yes 'Locate File' does seem to work for other files. I think this is Method 1 in your slides.
I noticed that CCS then adds the path below (starting /nightlybuilds) to the .launch file automatically which seems to be Method 2 in your slides.
I think I understand the cause now.
As mentioned in the opening question, the path I added manually beforehand "source - C:\ti\mcu_plus_sdk_am263px_09_02_00_56" was not successful but I noticed this is not the same as Method 3. Method 3 uses Preferences -> Debug -> Source Lookup Path but I added the path via the Project Properties.
The latter dialogue box does not offer to search sub folders which I think is the key difference.
Anyway, I guess Method 1 is OK for now. I can see though that if we change the SDK version, this will break the path mapping.
The latter dialogue box does not offer to search sub folders which I think is the key difference.
Recursive searching in subfolders can cause performance issues hence why method 1 is best.
Anyway, I guess Method 1 is OK for now. I can see though that if we change the SDK version, this will break the path mapping.
Yes, you may have to redo it when there are changes but only once per instance.