Retrieve the MCUboot version from the application

[QuentinD]

Hello,

I have a project with b0 + MCUboot + App.

My partitions are like this:

b0_container: 0x0 -> 0x9000 (0x9000)
	b0: 0x0 -> 0x8000 (0x8000)
	provision: 0x8000 -> 0x9000 (0x1000)

s0: 0x9000 -> 0x19200 (0x10200)
	s0_pad: 0x9000 -> 0x9200 (0x200)
	s0_image: 0x9200 -> 0x19200 (0x10000)
		mcuboot: 0x9200 -> 0x19200 (0x10000)

EMPTY_0: 0x19200 -> 0x1a000 (0xe00)

s1: 0x1a000 -> 0x2a200 (0x10200)
	s1_pad: 0x1a000 -> 0x1a200 (0x200)
	s1_image: 0x1a200 - 0x2a200 (0x10000)

EMPTY_1: 0x2a200 -> 0x2b000 (0xe00)

mcuboot_primary: 0x2b000 -> 0xe0000 (0xB5000)
	mcuboot_pad: 0x2b000 -> 0x2b200 (0x200)
	mcuboot_primary_app: 0x2b200 -> 0xe0000 (0xb4e00)
		app_image: 0x2b200 -> 0xe0000 (0xb4e00)
			app: 0x2b200 -> 0xe0000 (0xb4e00)

mcuboot_secondary: 0xe0000 -> 0xf0000 (0x10000)

settings_storage: 0xf0000 -> 0x100000 (0x10000)

sram_primary: 0x20000000 -> 0x20040000 (0x40000)

In my application, how can I retrieve the version number of the bootloader (MCUboot) that is currently active?

Thank you

[Hakon]

Hello,

I was discussing this with a coworker, and I think this will be very hard to implement. Is this feature a high priority for you? Perhaps you can check this and see if you find some helpful information.

[QuentinD]

Hello,

Yes I need it in my application to know if the bootloader needs to be updated (my device connects via BLE to a smartphone and it checks the versions of the bootloader and the application to check if the device is up to date).

I find it surprising that it is so complicated to recover the version of the bootloader that is currently in use. The only way to retrieve the boot version is to save it in RAM/falsh ?
How does the immutable bootloader (b0) know if it is the bootloader present in s0 or s1 that it should boot (thus with the latest version)? Could this version number be in the s0_pad or s1_pad partition?

[QuentinD]

Hakon Could you answer my questions please?

[Sigurd]

Hi! 

Could you try using the function boot_read_bank_header()?

Example usage: https://github.com/nrfconnect/sdk-nrf/blob/v2.4.2/applications/nrf_desktop/src/modules/dfu.c#L738

[QuentinD]

Hi,

This function is what I need but it returns the error "-5": do you have any idea why?

In the "boot_read_v1_header" function, I see:

	/*
	 * Sanity checks.
	 *
	 * Larger values in header_size than BOOT_HEADER_SIZE_V1 are
	 * possible, e.g. if Zephyr was linked with
	 * CONFIG_ROM_START_OFFSET > BOOT_HEADER_SIZE_V1.
	 */
	if ((v1_raw->header_magic != BOOT_HEADER_MAGIC_V1) ||
	    (v1_raw->header_size < BOOT_HEADER_SIZE_V1)) {
		return -EIO;
	}

Here I tried to read the header of the S0 image but v1_raw->header_magic=0x20009680 (not 

0x96f3b83d)

Thank you for your help

[Sigurd]

Hi!

Is it this if check that fails?

https://github.com/nrfconnect/sdk-zephyr/blob/v3.3.99-ncs1/subsys/dfu/boot/mcuboot.c#L98

[QuentinD]

Yes exactly!

[Sigurd]

Hi!

The function might not be compatible with S0. But can you try reading the PM_MCUBOOT_PRIMARY_ID instead?

[QuentinD]

I was able to retrieve the versions to compare them using this function:

const struct fw_info *firmware_info = fw_info_find(PM_S0_IMAGE_ADDRESS);