CCSTUDIO-SITARA: CodeComposer Studio does not locate Debug Symbols correctly

Thank you for the update. It is likely related to EXT_EP-10606, which is still unresolved. I'll try to get an update on this issue.

Hi Ki,

Can update on this issue? It has been 5 months since customer reported this issue. Thanks!

Ming 

The effort required for this bug is evaluated by engineering. Oncethe effort required has been determined, a proper timetable can be given

Thanks

ki

Hi Ki,

Any progress on this issue?

Best regards,

Ming

It is still under investigation...

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

Hi John,

is there a timeline/ release date for 12.1 ?

Thanks!

Fabian

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 John and Ki,

Customer has checked with the CCS 12.1.0, the problem still exists. Please confirm this issue has been fixed in CCS 12.1.0 or not.

Thanks!

Ming

According to the bug record, it should be fixed in 12.1.0. Which compiler version are they using?

Thanks

ki

Hi Ki,

currently we are using 1.3.1 LTS compiler since SDK version 8.4 uses also this compiler version.

BR

Fabian

Thank you. I'll try to confirm the fox on 12.1 and keep you posted.

ki

Just a quick update - I'm investigating this now and will have an update later today

I am able to reproduce this issue with CCS 12.1.0 also. I will check with engineering to see if the proposed fix ever made it into the 12.1 build.

I am working with engineering in this. I will keep you posted of any updates

Please note that the engineer responsible for the fix in currently away. Apologies for the delay

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

Fabian Sorkalla said:

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. 

Ki said:

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