RE: Debugging MCUboot

Elfving — Wed, 08 Jan 2025 10:21:20 GMT

Hi Odd Rune,

Glad to see you found a solution this quickly yourself. I've also explained this here in an older case of mine.

Regards,

Elfving

RE: Debugging MCUboot

vitalgobo — Wed, 08 Jan 2025 09:51:32 GMT

Well, to tie things up, I have solved it.

The basic gist of it is:
* Flash the merged.hex from the west build.
* Make sure to run b0 (wichever you use) before attempting to debug mcuboot. Essentially, the steps are:

In the Ozone jdebug script:
1. We do this by inspecting the b0 elf, finding the entry point and adding a step to _SetupTaget(), in our case
Target.SetReg("PC", 0x10E0")
Target.SetReg("SP", 0x20003208).
2. Load the mcuboot ELF in Ozone using: File.open() in OnProjectLoad() to get access to the debug symbols.
3. In TargetDownload(): Target.LoadMemory("/home/user/blah/build/merged.hex")

In effect, this flashes and runs b0 (entry point at 0x10E0), and hands things over to mcuboot; so that the external APIs are registered by b0 and accessible by mcuboot [used as the second stage bl].

So that works.

A second case I had was getting Segger RTT to work in mcuboot, but I've abandoned this for now as I can actually get step-debugging to work.