One application with MCUboot and overwrite image upgrades?

RE: One application with MCUboot and overwrite image upgrades?

SebastianA — Fri, 01 Dec 2023 12:40:57 GMT

That works fine! Thank you!

RE: One application with MCUboot and overwrite image upgrades?

Vidar Berg — Fri, 01 Dec 2023 12:19:33 GMT

Hi,

A solution, if not using sysbuild, is to create a 'child_image' directory in your project source directory containing a Kconfig fragment for MCUBoot where you can place the specific Kconfig symbols for MCUBoot that you want to override. Expected naming and placement of the Kconfif files in the child image folder is illustrated here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.0/nrf/config_and_build/multi_image.html#permanent-configuration-changes-to-child-images

Here is a simple example if you want to build MCUBOOT with CONFIG_BOOT_UPGRADE_ONLY=y:

devzone.nordicsemi.com/.../5875.child_5F00_image.zip

Please note that you must perform a pristine build after adding the child image folder to the project for it to be picked up by the build system. After the build is complete, you can verify that your settings were applied by checking the .config file located in your build directory under mcuboot/zephyr/.

RE: One application with MCUboot and overwrite image upgrades?

SebastianA — Fri, 01 Dec 2023 08:39:16 GMT

Yes, it should work with:
west build -t zephyr/app_moved_test_update.hex
or/and:
west build -t zephyr/app_signed.hex

RE: One application with MCUboot and overwrite image upgrades?

Kuno. — Fri, 01 Dec 2023 07:54:39 GMT

Can you choose to only build the app? So far when I do west build, it builds both the bootloader and the application.
I would like to separate the development of these to projects

RE: One application with MCUboot and overwrite image upgrades?

SebastianA — Fri, 01 Dec 2023 07:29:17 GMT

I don't know if west has support for it, but you can always flash the images yourself with nrfjprog.

There is a build/zephyr/app_signed.hex to just install the app (in the primary area).

build/zephyr/app_moved_test_update.hex is for the secondary area, so the bootloader can update it.

build/zephyr/merged.hex file that contains both the bootloader and the app.

RE: One application with MCUboot and overwrite image upgrades?

Kuno. — Thu, 30 Nov 2023 13:36:53 GMT

I just figured out when I was flashing my application it was also building a default bootloader and flashing that. That's why my Kconfigs was ignored.

Is it possible to build an application for a bootloader, without also building a default bootloader that is also flashed.? I would like these two builds to be seperate.

RE: One application with MCUboot and overwrite image upgrades?

Kuno. — Thu, 30 Nov 2023 11:59:06 GMT

Hi Sebastian,
I'm experiencing something similar.

I have built a new bootloader with the extra configurations;
`
# Overwrite
CONFIG_BOOT_UPGRADE_ONLY=y
# Swap algorithm
CONFIG_BOOT_SWAP_USING_MOVE=n
`

I'm building my app with config
`
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_MCUBOOT_SIGNATURE_KEY_FILE="zephyrproject/bootloader/mcuboot/root-rsa-2048.pem"

I also tried adding these configs to my app

`
CONFIG_MCUBOOT_BOOTLOADER_MODE_OVERWRITE_ONLY=y
CONFIG_MCUBOOT_BOOTLOADER_NO_DOWNGRADE=y

When I try to upgrade with the new application, the bootloader still use the move algorithm to swap. It seems like the config flags are ignored.