MCUBOOT on SED reverts

RE: MCUBOOT on SED reverts

Mary — Wed, 06 Dec 2023 15:27:01 GMT

Indeed the flash partitions are different, though they shouldn't be. For some reason, the NCS 1.9.1 project creates a storage setting partition with size 0x2000, even though I've specified 0x8000.

In partitions.yml

settings_storage:
address: 0xfe000
end_address: 0x100000
placement:
before:
- end
region: flash_primary
size: 0x2000

even though the dts file contains

&flash0 {
	partitions {
		compatible = "fixed-partitions";
		#address-cells = <1>;
		#size-cells = <1>;

		boot_partition: partition@0 {
			label = "mcuboot";
			reg = <0x0 0x10000>;
		};
		slot0_partition: partition@10000 {
			label = "image-0";
			reg = <0x10000 0xE8000>;
		};
	
		storage_partition: partition@f8000 {
			label = "storage";
			reg = <0xf8000 0x8000>;
		};
	};
};

and child_image/mcuboot/prj.conf contains:

CONFIG_PM_PARTITION_SIZE_SETTINGS_STORAGE=0x8000
CONFIG_SETTINGS_NVS_SECTOR_COUNT=8

For production, we will use NCS 2.4.1, or greater, and don't need to go back to NCS 1.9.1.

Thanks, for pointing me in the right direction.

Mary

RE: MCUBOOT on SED reverts

Amanda Hsieh — Tue, 14 Nov 2023 20:47:01 GMT

[quote user="Mary"]mcuboot_swap_type() should be returning BOOT_SWAP_TYPE_REVERT , but it's not.[/quote]

What does mcuboot_swap_type return?

Do you build two projects with the same memory partition?

Can I suggest that you do this to do static partitioning?

First, build your application without static partitioning.
Copy project/build/partitions.yml --> project/pm_static.yml
1. Note: pm_static.yml will automatically be detected by the build system, due to its specific name
Copy project/pm_static.yml to both projects for v2.4.1 and v1.9.1
Rebuild both applications.
Flash first application.
Now try DFU

-Amanda H.

RE: MCUBOOT on SED reverts

Mary — Tue, 14 Nov 2023 16:03:55 GMT

There are modifications, many. It is updating from MyApplication v0.6 to v0.5

v0.5 is compiled with NCS 1.9.1
v0.6 is compiled with NCS 2.4.1

So, MCUBOOT is from NCS 2.4.1

The SED

writes the update (v0.5) to external flash
calls boot_request_upgrage(BOOT_UPGRADE_TEST)
reboots

MCUBOOT runs the new firmware. OK, so far

mcuboot_swap_type() should be returning BOOT_SWAP_TYPE_REVERT , but it's not. So, boot_write_img_confirmed() never get called. On the next boot, MCUBOOT reverts to the previous version.

It should find an Active Dataset, but it doesn't.

After reverting back to v0.6, it does find the Active Dataset.

Note the logs from fs_nvs in the reverted boot, but not the first one.

Console output:

devzone.nordicsemi.com/.../SED_5F00_ota_5F00_revert.txt

Mary

RE: MCUBOOT on SED reverts

Amanda Hsieh — Tue, 14 Nov 2023 15:14:12 GMT

Hi,

[quote user=""] "Swap type : none".[/quote]

This means the “usual” or “no upgrade” case; attempt to boot the contents of the primary slot.

Make sure to the update code with modifications.

-Amanda H.