Upgraded firmware image not confirmed by MCUBoot DFU

RE: Upgraded firmware image not confirmed by MCUBoot DFU

Anthony — Fri, 27 Aug 2021 10:57:40 GMT

Hey Esisk, yes I figured out the problem by using static partitions as suggested by Heidi. In addition to my reply above, here are the Kconfig options that I used:

# Bootloader
CONFIG_BOOTLOADER_MCUBOOT=y
# Device firmware upgrade
CONFIG_DFU_TARGET=y
CONFIG_DFU_TARGET_MCUBOOT=y
CONFIG_FLASH=y
CONFIG_IMG_ERASE_PROGRESSIVELY=y
CONFIG_IMG_MANAGER=y
CONFIG_MCUBOOT_IMG_MANAGER=y
CONFIG_SIGN_IMAGES=y

The CONFIG_MCUBOOT_ options were not needed to confirm the image successfully. Still, now we need to configure the build system to sign the firmware with our own keys.

RE: Upgraded firmware image not confirmed by MCUBoot DFU

Anthony — Fri, 27 Aug 2021 10:38:47 GMT

Hi !

Thank you very much for your answer. The configuration of static partitions in the new firmware project allowed to solve the problem. The new image is now successfully confirmed by the boot_write_img_confirmed() method.

I followed the documentation you provided, and as suggested in Configuring static partitions I copied the "build/partitions.yml" file from the old firmware project into the root directory of the new firmware project, under the name "pm_static.yml". At first I was a bit confused because $APPLICATION_SOURCE_DIR refers to the root directory of the project and not to the src/ directory, but now it works as expected.

RE: Upgraded firmware image not confirmed by MCUBoot DFU

esisk — Thu, 26 Aug 2021 12:47:43 GMT

Hey Anthony, I'm having a very similar issue. Did you figure out the problem?

RE: Upgraded firmware image not confirmed by MCUBoot DFU

Heidi — Mon, 23 Aug 2021 11:38:31 GMT

Hi!

I wonder if your static configuration is the issue? How did you set this up?

Best regards,

Heidi