Configuring SEGGER debugger with boot loader

[MKir]

On our platform we have the following configuration of firmware:

• Master boot record
• Boot loader
• Thread application (compiled separately from the boot loader)

We can currently use the SEGGER debugger to debug the application by only loading that and starting execution inside the application.

We cannot debug some aspects of the overall firmware (notably firmware update) without executing the boot loader.

What do we need to adapt to add the bootloader to a debugging session?

[Vidar Berg]

Hello,

To my knowledge, Segger does not support the loading of additional symbol files. The way I do it is to have both the bootloader and application projects open, and then start the debug session from either the application or bootloader project, depending on what I want to debug. It's not a problem to have an active debug session running for the bootloader project while the main application is running.

Best regards,

Vidar

[MKir]

It turns out the "loader" options were the answer for us, although it does not allow loading the debug symbols for all those images.

In the version we use (which is admittedly quite old) there are options to load up to four additional images before starting the debug session: