Hello!
We are in the middle of an upgrade to 3.2.1, and we encounter the following issue using SB_CONFIG_MCUBOOT_MODE_SWAP_WITHOUT_SCRATCH, SB_CONFIG_MCUBOOT_MODE_SWAP_USING_MOVE & SB_CONFIG_MCUBOOT_MODE_SWAP_USING_OFFSET
Basically right after flashing `b0` fails to boot:
*** Booting nRF Connect SDK v3.2.1-d8887f6f32df *** *** Using Zephyr OS v4.2.99-ec78104f1569 *** Attempting to boot slot 0. Attempting to boot from address 0x8200. [00:00:00.000,854] <inf> bl_validation: Trying to get Firmware version [00:00:00.001,129] <err> bl_validation: Invalid size or total_size in firmware info. Failed to validate, permanently invalidating! Attempting to boot slot 1. Attempting to boot from address 0x18200. [00:00:00.001,892] <inf> bl_validation: Trying to get Firmware version [00:00:00.002,197] <err> bl_validation: Invalid size or total_size in firmware info. Failed to validate, permanently invalidating! No bootable image found. Aborting boot.
One of the main reasons we want to upgrade to 3.2.1 (qualification aside) is to get the new "OFFSET mcuboot algorithm" (SB_CONFIG_MCUBOOT_MODE_SWAP_USING_OFFSET), since 2.9.0 does not have that we were using the MOVE algorithm ( SB_CONFIG_MCUBOOT_MODE_SWAP_USING_MOVE ), and that was working fine, until the upgrade.
Another weird thing we found is that (SB_CONFIG_MCUBOOT_MODE_OVERWRITE_ONLY) botos alright and allows us to do the updates ( but we want to move to SWAP using OFFSET)
We seem to have some space available in s0/s1
but not so much on b0
Any ideas?