This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Ozone settings with bootloader

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 ?

Parents
  • Hello,

    Have you commented the AfterTargetReset() and AfterTargetDownload() implementation in your Ozone project? Those will by default make the program jump directly to the start of the executable you are currently debugging. i.e.,  cause the MCUBOOT/SPM part of the boot sequence to be skipped if you are attempting to debug the main app. 

    Ozone *.jdebug project file I used to debug the aws fota sample:

  • Hello Vidar, 

    Do you have any another idea about that ?

Reply Children
  • Hello,

    I can try again with Ozone 3.10 to see if I can replicate it. Do you mind sharing your Ozone project?

  • My Ozone project is just your configuration file that target an aws_fota sample built with SES.

  • 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.

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

  • 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.