Building and debugging a monolithic bin/hex/elf/out

RE: Building and debugging a monolithic bin/hex/elf/out

Eliot Stock — Fri, 18 Nov 2016 00:37:08 GMT

OK, I'll stick to the .out file, forget the .elf file, run gdb against the application .out file and then use add-symbol-file to add the bootloader .out file. Will leave -flto out of my application build, but I see you've got it turned on for the armgcc debug build of the bootloader in SDK 12.1.0 btw.

RE: Building and debugging a monolithic bin/hex/elf/out

Vidar Berg — Wed, 16 Nov 2016 13:26:09 GMT

Shouldn't be a problem to use .out instead of .elf, we use it for all of our GCC examples. However, you may want to disable link time optimization (remove -flto flag in Makefile). I my experience it does not always work well with debugging (maybe dependent on toolchain version).

RE: Building and debugging a monolithic bin/hex/elf/out

Eliot Stock — Tue, 15 Nov 2016 08:00:42 GMT

Yep, done that. Actually, I just realised the Makefile for the bootloader from the SDK does NOT build an .elf file at all yet. Just .bin, .out and .hex. And the .out file it builds is not debuggable, even in the _debug build. First of all, how do I modify Makefile.common to link an .elf file? Here's how it links the .out file:

# Link object files
%.out:
	@echo Linking target: $@
	$(NO_ECHO)$(CC) -Wl,-Map=$(@:.out=.map) $(LDFLAGS) $^ $(LIB_FILES) -lm -o $@
	-@echo ''
	$(NO_ECHO)$(SIZE) $@
	-@echo ''

RE: Building and debugging a monolithic bin/hex/elf/out

Thomas Stenersen — Mon, 14 Nov 2016 12:42:46 GMT

Hi,

First of all make sure you build your project (and bootloader) with -g for adding the debug symbols to the .elf file. Next, take a look at the gdb command add-symbol-file https://sourceware.org/gdb/current/onlinedocs/gdb/Files.html#index-add_002dsymbol_002dfile-1172.