Ozone settings with bootloader

[Fabien Comte]

Hello,

I tried to configure Ozone for aws_fota sample without any success. I loaded elf files but one is debuging mcu boot and the other never access to the main. Do someone have an idea please ?

[Vidar Berg]

It worked Ozone 3.10 as well. Here is what I did:

1. Loaded the merged.hex with SES

2. Opened the Ozone project which loads the application .elf file. 

3. Selected "attached to running programming" followed by "Reset & break at symbol".  As shown below, this made the program halt in main().

But I'm not sure how good Ozone supports debugging of multiple images at the same time. The File.Load() command "replace any previously loaded debug symbols". Maybe there is another command to load additional debug symbols. SES has that option.

[Fabien Comte]

Hello,
Thank you Vidar, you fixed my mistake, I was using "download & reset program", not "attach to running program"

[Vidar Berg]

Hello,

Thanks for confirming. I guess it's possible that the .elf and .hex file have different padding rules and thus cause the boot validation to fail (results in a different hash digest or checksum). It's something we should more look into.

[Fabien Comte]

Hello,

I fixed that by adding this in the Ozone configuration that you proposed.

void TargetDownload (void) { 
Target.LoadMemory("$(ProjectDir)/build_nrf9160_pca10090ns/zephyr/merged.hex", 0);                                      
}