How to use mcuboot to upgrade

[Abner]

Hi,

I am using nrf52832 to test the function of mcuboot. The reference routine used is D:\ncs\v2.6.0\zephyr\samples\application_development\sysbuild\with_mcuboot. After compilation, I get the following output:

Download the image to flash and get the following log output：

From the above log output, I think that both the mcuboot image and the app image were burned into the FLASH possibly by merged.hex, and mcuboot successfully booted the app.

The problem now is that I want to test the upgrade function of mcuboot. The version number is upgraded to CONFIG_MCUBOOT_IMGTOOL_SIGN_VERSION="0.0.0+1". At the same time, I change the log in the main function. After compilation, I also get app_signed.hex, app_update.bin, app_test_update.hex , merged.hex, in order to test the upgrade function, which file should I use to burn into the flash and how do I burn it? Do I need to specify the address of the flash when burning?

[Abner]

I have found a way to upgrade using app_moved_test_update.hex, but why is the starting address 0x46000 instead of 0x43000?

[Vidar Berg]

Hello,

The memory placement is controlled by the Partition Manager when you perform multi-image builds (e.g. application + MCUBoot) and not the devicetree. You can view the actual memory layout using the 'Memory report' action in VS Code.

For a description of the generated hex files, please refer to: Output build files (image files). You may also want to have a look at this course at the DevAcademy: https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/ 

Best regards,

Vidar

[Abner]

That's great. The information you provided solved a lot of my confusion. I just started using ncs for development and there are still a lot of things to learn. Thank you.