CCS/DRA756: Unable to associate ARM assembly source during debug

Stephen Molfetta

Part Number: DRA756

Tool/software: Code Composer Studio

Hi,

I'm trying to step through an assembly function running on the Cortex A15_0 core of a DRA75x device. The assembly function is compiled directly from source within my CCS project (not from a library), and I have debug information enabled in the compiler flags. When I step into the assembly function, I see a window displaying the following:

So I lose my call stack, and the debugger can't associate to the source when stepping through the code. I can step through the disassembly, but I would prefer to use the source itself (with comments, declaration aliases, etc.).

I am using the following tools: bios_6_50_01_12, CCSv7.1.0, uia_2_20_00_02, xdctools_3_50_02_20_core, gcc-arm-none-eabi-4_9-2015q3.

GCC compiler settings for the asm file: "-mcpu=cortex-a15 -mtune=cortex-a15 -marm -mfloat-abi=hard -g -gdwarf-3 -gstrict-dwarf -Wall"

Is there something else that I'm missing here?

Thanks,

Stephen

over 8 years ago

0 Ki over 8 years ago

TI__Guru**** 482331 points

Hi Stephen,
Can you provide the executable to me? You can send to me via private message if you wish.

Thanks
ki

0 Stephen Molfetta over 8 years ago in reply to Ki

TI__Expert 5725 points

Thanks, Ki. I'll send you a mail in a bit.

-Stephen

0 Chester Gillon over 8 years ago

Guru 92251 points

Stephen Molfetta said:
I am using the following tools: bios_6_50_01_12, CCSv7.1.0, uia_2_20_00_02, xdctools_3_50_02_20_core, gcc-arm-none-eabi-4_9-2015q3.

Can you try upgrading to CCS v7.2.0?

Just checked, and the problem was still present in CCS v7.1.0 but is no longer present in CCS v7.2.0.00013.

In CCS v7.2.0.00013 I was able to single-step through an assembler function for a Cortex-A15 built with gcc-arm-none-eabi-4_9-2015q3 and CCS showed the source instructions as stepped.

0 Stephen Molfetta over 8 years ago in reply to Chester Gillon

TI__Expert 5725 points

Hi Chester,

Thanks for the suggestion - CCSv7.2.0 seems to properly associate the debugger with the original source (though still doesn't preserve the call stack). Updating to v7.2.0 may not be the ideal option for our situation, so I'd still like to wait and see if Ki is able make any additional progress on the 7.1.0 baseline. Otherwise, we will have to reconsider the version update.

Thanks,

Stephen

0 Chester Gillon over 8 years ago in reply to Stephen Molfetta

Guru 92251 points

Stephen Molfetta said:
CCSv7.2.0 seems to properly associate the debugger with the original source (though still doesn't preserve the call stack).

I just remembered that also reported an issue where the CCS backtrace for programs compiled with the GCC ARM compiler is not always complete - see CCS 6.2.0.00050 doesn't display complete stack backtrace when a Cortex-A15 SYS/BIOS program using the GNU compiler terminates due to an error or calling BIOS_exit()

Defect CCBT-2049 was raised as a result of that referenced thread, and is scheduled to be fixed in CCS 7.3.

Not sure if your example where the call stack isn't preserved is the same as CCBT-2049, or a different problem.

0 Ki over 8 years ago in reply to Chester Gillon

TI__Guru**** 482331 points

This issue is reproducible with CCS 7.3.0 (beta) and appears to be a different issue. The source code correlation with the assembly file in question appears to be lost. I have filed a new JIRA for this: CCBT-2132

Thanks
ki

0 Ki over 8 years ago in reply to Ki

TI__Guru**** 482331 points

This issue will be fixed in the coming CCSv7.3.0 release

Thanks
ki

0 Stephen Molfetta over 8 years ago in reply to Ki

TI__Expert 5725 points

Great - thanks!

Code Composer Studio™︎

Code Composer Studio forum

CCS/DRA756: Unable to associate ARM assembly source during debug