problem updating mcuboot over FOTA in dual stage bootloader configuration

RE: problem updating mcuboot over FOTA in dual stage bootloader configuration

frankbuss — Mon, 20 May 2024 09:51:51 GMT

I think the problem was that the external flash was in some weird state because of all the testings. I erased it with "flash erase mx25r6435f@0 0 800000" from the shell, and then nRF Connect worked again.

RE: problem updating mcuboot over FOTA in dual stage bootloader configuration

Amanda Hsieh — Wed, 08 May 2024 16:50:16 GMT

Could you use the latest version of NCS v2.6.1 for bug fixing?

RE: problem updating mcuboot over FOTA in dual stage bootloader configuration

frankbuss — Tue, 07 May 2024 07:45:33 GMT

Yes, I changed MCUBoot as well. Here is the current sample project:
https://www.frank-buss.de/tmp/peripheral_hr_smp_b0.zip
First I flashed it with

CONFIG_FW_INFO_FIRMWARE_VERSION=14

in mcuboot.conf, and also used

BOOT_LOG_INF("Starting bootloader 14");

for bootloader/mcuboot/boot/zephyr/main.c. I built the project with this line:

rm -rf build ; west build --board=nrf5340dk_nrf5340_cpuapp -p always

Then I flashed it with "west flash --recover".

Then I changed the two 14 numbers to 15, built it again, and flashed it with "build/zephyr/dfu_mcuboot.zip" over FOTA with nRF Connect. It showed the graph, which looked like it transferred 2 files. While transferring, it showed also some information that it erased something, but apparently not the mcuboot. I needed to reset it manually, and it showed the same 14 numbers. Full log:

*** Booting Zephyr OS build v3.2.99-ncs2 ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
Verifying signature against key 0.
Hash: 0xb4...42
Firmware signature verified.
Firmware version 14
*** Booting Zephyr OS build v3.2.99-ncs2 ***
I: Starting bootloader 14
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0x28000
*** Booting Zephyr OS build v3.2.99-ncs2 ***
[00:00:00.030,273] <inf> bt_hci_core: hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.030,334] <inf> bt_hci_core: hci_vs_init: HW Variant: nRF53x (0x0003)
[00:00:00.030,364] <inf> bt_hci_core: hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 216.11532 Build 3803067951
[00:00:00.032,348] <inf> bt_hci_core: bt_dev_show_info: Identity: F2:7C:B6:5D:C3:74 (random)
[00:00:00.032,379] <inf> bt_hci_core: bt_dev_show_info: HCI: version 5.3 (0x0c) revision 0x224b, manufacturer 0x0059
[00:00:00.032,409] <inf> bt_hci_core: bt_dev_show_info: LMP: version 5.3 (0x0c) subver 0x224b
Bluetooth initialized
Advertising successfully started
build time: May 7 2024 a 09:26:26
Connected
[00:02:29.361,358] <inf> mcuboot_util: boot_swap_type_multi: Swap type: none
[00:02:29.501,556] <inf> mcuboot_util: boot_swap_type_multi: Swap type: none
[00:02:29.501,586] <inf> mcuboot_util: boot_swap_type_multi: Swap type: none
[00:02:34.856,658] <inf> mcuboot_util: boot_swap_type_multi: Swap type: none
[00:02:34.856,719] <inf> mcuboot_util: boot_swap_type_multi: Swap type: none
[00:02:35.721,282] <inf> mcumgr_img_mgmt: img_mgmt_erase_image_data: Erased 0xa000 bytes of image slot
[00:02:35.807,739] <inf> mcumgr_img_mgmt: img_mgmt_erase_image_data: Erased 0x1000 bytes of image slot trailer
*** Booting Zephyr OS build v3.2.99-ncs2 ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
Verifying signature against key 0.
Hash: 0xb4...42
Firmware signature verified.
Firmware version 14
*** Booting Zephyr OS build v3.2.99-ncs2 ***
I: Starting bootloader 14
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0x28000
*** Booting Zephyr OS build v3.2.99-ncs2 ***
[00:00:00.030,303] <inf> bt_hci_core: hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.030,364] <inf> bt_hci_core: hci_vs_init: HW Variant: nRF53x (0x0003)
[00:00:00.030,395] <inf> bt_hci_core: hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 216.11532 Build 3803067951
[00:00:00.032,379] <inf> bt_hci_core: bt_dev_show_info: Identity: F2:7C:B6:5D:C3:74 (random)
[00:00:00.032,409] <inf> bt_hci_core: bt_dev_show_info: HCI: version 5.3 (0x0c) revision 0x224b, manufacturer 0x0059
[00:00:00.032,440] <inf> bt_hci_core: bt_dev_show_info: LMP: version 5.3 (0x0c) subver 0x224b
Bluetooth initialized
Advertising successfully started

RE: problem updating mcuboot over FOTA in dual stage bootloader configuration

Amanda Hsieh — Mon, 06 May 2024 21:32:25 GMT

Do you make a change to MCUBoot?

To make the change visible, make a change to MCUBoot, for example add a log in $NRF_CONNECT_SDK/bootloader/mcuboot/boot/zephyr/main.c.

RE: problem updating mcuboot over FOTA in dual stage bootloader configuration

frankbuss — Mon, 06 May 2024 16:18:43 GMT

I tried the peripheral_hr_smp_b0.zip file from the link you posted, but still doesn't work. First I had to change the source file, because some includes where outdated. Then I removed the hardcoded private file, which should cause it to use the internal key. I flashed then the version 11 Then I changed it to version 12 and compiled it again. This it looks like I could use the dfu_mcuboot.zip file, I got the progress graph, and looks like it flashed both files. But after booting it was still version 11. See below for the log on the serial terminal.

I also tried the 2 files signed_by_mcuboot_and_b0_s0_image_update.bin and signed_by_mcuboot_and_b0_s1_image_update.bin with the peripheral_hr_smp_b0 demo project, but didn't work either. Looks like they didn't flash anything

I'm out of ideas. Could you try the peripheral_hr_smp_b0 sample on a nrf5340dk board, and fix it if required, or describe in detail how I can compile and flash it so that mcuboot gets updated?

*** Booting Zephyr OS build v3.2.99-ncs2 ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
Verifying signature against key 0.
Hash: 0x7f...07
Firmware signature verified.
Firmware version 11
Setting monotonic counter (version: 11, slot: 0)
*** Booting Zephyr OS build v3.2.99-ncs2 ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
Verifying signature against key 0.
Hash: 0x7f...07
Firmware signature verified.
Firmware version 11
*** Booting Zephyr OS build v3.2.99-ncs2 ***
[00:00:00.030,242] <inf> bt_hci_core: hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.030,303] <inf> bt_hci_core: hci_vs_init: HW Variant: nRF53x (0x0003)
[00:00:00.030,334] <inf> bt_hci_core: hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 216.11532 Build 3803067951
[00:00:00.032,318] <inf> bt_hci_core: bt_dev_show_info: Identity: F2:7C:B6:5D:C3:74 (random)
[00:00:00.032,348] <inf> bt_hci_core: bt_dev_show_info: HCI: version 5.3 (0x0c) revision 0x224b, manufacturer 0x0059
[00:00:00.032,379] <inf> bt_hci_core: bt_dev_show_info: LMP: version 5.3 (0x0c) subver 0x224b
Bluetooth initialized
Advertising successfully started
build time: May 6 2024 a 17:30:00
Connected
[00:14:17.292,266] <inf> mcuboot_util: boot_swap_type_multi: Swap type: none
[00:14:17.433,807] <inf> mcuboot_util: boot_swap_type_multi: Swap type: none
[00:14:17.433,868] <inf> mcuboot_util: boot_swap_type_multi: Swap type: none
[00:14:22.428,955] <inf> mcuboot_util: boot_swap_type_multi: Swap type: none
[00:14:22.429,016] <inf> mcuboot_util: boot_swap_type_multi: Swap type: none
[00:14:23.293,853] <inf> mcumgr_img_mgmt: img_mgmt_erase_image_data: Erased 0xa000 bytes of image slot
[00:14:23.380,340] <inf> mcumgr_img_mgmt: img_mgmt_erase_image_data: Erased 0x1000 bytes of image slot trailer
*** Booting Zephyr OS build v3.2.99-ncs2 ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
Verifying signature against key 0.
Hash: 0x7f...07
Firmware signature verified.
Firmware version 11
*** Booting Zephyr OS build v3.2.99-ncs2 ***
[00:00:00.030,303] <inf> bt_hci_core: hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.030,364] <inf> bt_hci_core: hci_vs_init: HW Variant: nRF53x (0x0003)
[00:00:00.030,364] <inf> bt_hci_core: hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 216.11532 Build 3803067951
[00:00:00.032,379] <inf> bt_hci_core: bt_dev_show_info: Identity: F2:7C:B6:5D:C3:74 (random)
[00:00:00.032,409] <inf> bt_hci_core: bt_dev_show_info: HCI: version 5.3 (0x0c) revision 0x224b, manufacturer 0x0059
[00:00:00.032,440] <inf> bt_hci_core: bt_dev_show_info: LMP: version 5.3 (0x0c) subver 0x224b
Bluetooth initialized
Advertising successfully started
build time: May 6 2024 a 17:30:00

RE: problem updating mcuboot over FOTA in dual stage bootloader configuration

frankbuss — Fri, 03 May 2024 14:01:49 GMT

This is the same posting, but I'll try their project zip, maybe some setting is different.

RE: problem updating mcuboot over FOTA in dual stage bootloader configuration

Amanda Hsieh — Fri, 03 May 2024 13:49:48 GMT

This post has the answer.

RE: problem updating mcuboot over FOTA in dual stage bootloader configuration

frankbuss — Fri, 03 May 2024 13:33:28 GMT

I checked the posting about dfu_mcuboot.zip. They tried signed_by_mcuboot_and_b0_s0_image_update.bin and signed_by_mcuboot_and_b0_s1_image_update.bin, but it doesn't work. I also changed

CONFIG_FW_INFO_FIRMWARE_VERSION in mcuboot.conf to 2.

I looked at the nRF log when I tried the zip file, and it looks like it is something on the device:

RE: problem updating mcuboot over FOTA in dual stage bootloader configuration

Amanda Hsieh — Wed, 01 May 2024 15:41:11 GMT

[quote user="frankbuss"]But updating mcuboot with dfu_mcuboot.zip doesn't work.[/quote]

Check out this post.

[quote user="frankbuss"]How many keys can I store in this OTP place?[/quote]

One-time programmable (OTP) memory is typically used for holding values that are written once, and then never to be changed again throughout the product lifetime. The OTP region of UICR is emulated by placing a write-once per halfword limitation on registers defined here.

The key storage region contains multiple key slots, where each slot consists of a key header and an associated key value. The key value is limited to 128 bits. Any key size greater than 128 bits must be divided and distributed over multiple key slot instances.

Key headers are allocated an address range of 0x400 in the UICR memory map, allowing a total of 128 keys to be addressable inside the key storage region. See nRF5340 PS.

Also see https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.6.1/nrf/samples/bootloader/README.html#otp-regions

RE: problem updating mcuboot over FOTA in dual stage bootloader configuration

frankbuss — Wed, 01 May 2024 13:54:32 GMT

Thanks, this works, now I can update the application with the dfu_application.zip file. But updating mcuboot with dfu_mcuboot.zip doesn't work. nRF Connect shows the upload graph, but then looks like it closes without uploading. I also tried to increase CONFIG_FW_INFO_FIRMWARE_VERSION to 2.

But if this works, I might be in trouble anyway, because the 2 instances of mcuboot and B0 reduces the space for the application. Best would be if B0 could update the application from the external flash, because I can use multiple keys with B0, so I could revoke compromised keys, as described here:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/libraries/security/bootloader/bl_storage.html

But I guess B0 can't update the application image from external flash, and mucboot can't use the keys in the Bootloader storage? If mcuboot could use the keys from this storage, this would be probably the best solution. I could provision it then with the normal public key, and a disaster public key (or multiple) in case the first key gets compromised. How many keys can I store in this OTP place?

RE: problem updating mcuboot over FOTA in dual stage bootloader configuration

Amanda Hsieh — Tue, 30 Apr 2024 17:55:41 GMT

Hi,

[quote user=""]When I change the message in the app, and compile it again, and want to update it over FOTA with the file "build/zephyr/dfu_application.zip" and nRF Connect, then looks like the mobile app hangs, says just "Connecting", but it doesn't upload. This used to work without the extra settings for b0 etc. Is there some setting wrong or missing?[/quote]

Try to add this config CONFIG_MCUMGR_SMP_BT_AUTHEN=n to prj.conf.

[quote user=""]can I combine the mcuboot update zip file with the application and network update zip file?[/quote]

Unfortunately, no. the app doesn't support that.

Regards,
Amanda H.