AnsweredAssumed Answered

Adding .elf files to debug context when using multiple binaries?

Question asked by gearhead1107 on Oct 11, 2017
Latest reply on Oct 27, 2017 by gearhead1107

I'm working on a "mini" bootloader which pulls in a bootloader .bin from another project in S32DS. After making the jump to the application, I naturally don't have any source code to step through since it's not part of the project.

 

I poked around at a few guides, namely this one (“No source available”, or how to Debug Multiple Binaries with GDB and Eclipse | MCU on Eclipse ) and in Debug Configurations-> Startup -> GDB run commands I added the following (where 0x10410 is the .text space according to the map file)
add-symbol-file "[file path]Bootloader_A00.elf" 0x10410

 

In my debugger console I see the following;

add-symbol-file "[file path]Bootloader_A00.elf" 0x10410
add symbol table from file "[file path]Bootloader_A00.elf" at
.text_addr = 0x10410
(y or n) [answered Y; input not from terminal]
Reading symbols from [file path]Bootloader_A00.elf...done.


however after the jump to Bootloader, I still get the "no source available for "_binary_C__Users_[myname]_workspaceS32DS_ARM... at [location in bootloader]" "

 

I've made sure I'm building in debug, but still can't see my code from the bootloader... any commands that I'm missing here?

Outcomes