Part Number: CCSTUDIO-SITARA
Customer still have the same issue with the CCS 11.2.0
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.
Part Number: CCSTUDIO-SITARA
Customer still have the same issue with the CCS 11.2.0
Ming,
The issue reported in this case is actually different than the previous one. There is a separate bug filed to track it. There should be an update on the target fix release shortly.
https://sir.ext.ti.com/jira/browse/EXT_EP-10831
Regards,
John
Fabian,
CCSv12.0.0 will be out the first week of July and then CCSv12.1.0 should be the first week of October.
Regards,
John
HI Fabian,
Waht is your current use case for this scenario? You are explicitly manually adding your source search paths correct?
Hi ki,
sorry for the late reply.
We are compiling our sources in a virtual machine and move for debugging to Windows.
The filesystem of the virtual machine is mounted as network drive. The paths in the elf will therefore look something like this:
/home/sorkallaf/projects/<sources>
But sources under windows are located here //networkdrive/home/sorkallaf/project/<sources>
So yes therefore we need to manually add the sources under windows so CCS is able to find them during debugging.
BR
Fabian
So yes therefore we need to manually add the sources under windows so CCS is able to find them during debugging.
There still appears to be an issue when manually adding the source search path to the debug configuration.
If the symbol or file is selected in the Modules view, in the context menu for it, select "Locate file" and browse to the appropriate file. This will configure the environment correctly and the debugger will open the correct files going forward. The question is why this works while the manual step of adding the path to the debug configuration does not.
If the symbol or file is selected in the Modules view, in the context menu for it, select "Locate file" and browse to the appropriate file. This will configure the environment correctly and the debugger will open the correct files going forward.
I followed up with engineering and they recommend the above method of setting source lookup paths using the Modules view. It is the most guaranteed way to correctly set up the debugger to use the correct paths.
Thanks
ki