NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Hung Bui — Mon, 19 Dec 2022 08:25:22 GMT

Hi Jimmy,

I suspect that it doesn't fit into the secondary slot for some reason. Maybe you can check the log from MCUBoot ?

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Jimmy — Fri, 16 Dec 2022 15:15:19 GMT

I have remove some code in my main.c(such as disable uart, disable rtt), make the flash usage at lower than 94%(before is 97%), ota ok now.

I don't know why flash used 97% not work, it's pretty strange.

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Hung Bui — Thu, 15 Dec 2022 12:50:51 GMT

It's pretty strange that it didn't work for you.

I noticed that you have the device advertised as "Zephyr Heartrate 3" . Was that because you modified the BLE name and flash it manually ?

Could you try to do DFU with nRF Connect and check the log ?

Also if you build it for the nRF52833 DK, please check the UART log on the board as well (The UART log on the merged.hex file won't work because I built it for nRF52832 DK)

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Jimmy — Thu, 15 Dec 2022 12:39:22 GMT

I tryed two way:

1. As you said, flash merged.hex, update app_update3.bin;

2. Build the source code you provide(Base on ncs2.0, 52833dk), flash, change ble name, rebuild, update;

Both two method are stuck when i clieck start upload buttion in Device Manage app.

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Hung Bui — Thu, 15 Dec 2022 10:08:31 GMT

Hi Jimmy,
Could you try:
Flash merged.hex
Use the phone to DFU update app_update3.bin ?

How did you get it to advertise Zephyr heartrate 3 ?

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Jimmy — Wed, 14 Dec 2022 16:37:14 GMT

I have try both your bin file and build with source code. It stuck when i clieck start uploard:

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Hung Bui — Wed, 14 Dec 2022 15:48:40 GMT

Hi Jimmy,
I was just following the guide again and it worked just fine.
Could you try to test the following project. It's made with NCS v2.2.0 but it should work with earlier SDK as well.

I also attached here the two bin files that you can use to test. By using app_update3, the device should advertise as "Zephyr Heartrate 3" instead of "Zephyr Heartrate 2" and you can use the other file to update back to "Zephyr Heartrate 2".
The hex and bin file was built for nRF52832 but it would work with nRF52833 as well.

devzone.nordicsemi.com/.../1526.peripheral_5F00_hr_5F00_smp.zip

devzone.nordicsemi.com/.../2287.merged.hex

devzone.nordicsemi.com/.../app_5F00_update2.bin

devzone.nordicsemi.com/.../app_5F00_update3.bin

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Jimmy — Wed, 14 Dec 2022 15:31:28 GMT

I use the new version of Device manage app, it show "Image not confirmed".

So, why my image cannot confirmed ?

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Jimmy — Wed, 14 Dec 2022 15:01:45 GMT

I delete the below config:

app prj.conf:

# Enable mcumgr.

CONFIG_MCUMGR=y

CONFIG_MCUMGR_CMD_IMG_MGMT=y

CONFIG_MCUMGR_CMD_OS_MGMT=y

CONFIG_BOOTLOADER_MCUBOOT=y

CONFIG_MCUMGR_SMP_BT=y

CONFIG_MCUMGR_SMP_BT_AUTHEN=n

CONFIG_IMG_ERASE_PROGRESSIVELY=y

# CONFIG_MCUBOOT_SIGNATURE_KEY_FILE="child_image/mcuboot/mcuboot_private.pem"

CONFIG_MCUBOOT_IMAGE_VERSION="0.0.0+0"

mcuboot pro.conf:

# CONFIG_BOOT_ENCRYPT_RSA=n

# CONFIG_BOOT_SIGNATURE_TYPE_RSA=y

# CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=y

# CONFIG_BOOT_SIGNATURE_KEY_FILE="mcuboot_private.pem"

And use nRF Connect app to upload just "Confirm only" option (Can not use Device Manage app, there are some bug: RE: DFU - Device Manager Question - Payload(250 bytes) too long for MTU: 249 ).

The result is the same. The only diffrent is "CONFIRM" button is not clieckble in Device Manage app:

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Hung Bui — Wed, 14 Dec 2022 14:22:35 GMT

Hi Jimmy,

I noticed that in the log MCUBoot was responding with "NOT SUPPORTED" it seems that there were an issue with confirming the image.
Have you tested without changing the signing key ? Have you managed to do DFU update with MCUBoot before ?

As far as I know CONFIG_MCUBOOT_SIGNATURE_KEY_FILE is obsoleted and you should use CONFIG_BOOT_SIGNATURE_KEY_FILE in the mcuboot configuration only (either by the mcuboot prj.conf of by the overlay in child_image\mcuboot.conf).

But I think it's the best to not changing the key and use the default key for testing first.

Please try to follow the guide here. Please use option "Confirm only" when you test.

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Jimmy — Wed, 14 Dec 2022 14:12:37 GMT

This is my partitions.yml file in build folder:

app:
  address: 0xc200
  end_address: 0x45000
  region: flash_primary
  size: 0x38e00
mcuboot:
  address: 0x0
  end_address: 0xc000
  placement:
    before:
    - mcuboot_primary
  region: flash_primary
  size: 0xc000
mcuboot_pad:
  address: 0xc000
  end_address: 0xc200
  placement:
    before:
    - mcuboot_primary_app
  region: flash_primary
  size: 0x200
mcuboot_primary:
  address: 0xc000
  end_address: 0x45000
  orig_span: &id001
  - mcuboot_pad
  - app
  region: flash_primary
  sharers: 0x1
  size: 0x39000
  span: *id001
mcuboot_primary_app:
  address: 0xc200
  end_address: 0x45000
  orig_span: &id002
  - app
  region: flash_primary
  size: 0x38e00
  span: *id002
mcuboot_secondary:
  address: 0x45000
  end_address: 0x7e000
  placement:
    after:
    - mcuboot_primary
    align:
      start: 0x1000
  region: flash_primary
  share_size:
  - mcuboot_primary
  size: 0x39000
settings_storage:
  address: 0x7e000
  end_address: 0x80000
  placement:
    align:
      start: 0x1000
    before:
    - end
  region: flash_primary
  size: 0x2000
sram_primary:
  address: 0x20000000
  end_address: 0x20020000
  region: sram_primary
  size: 0x20000

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Jimmy — Wed, 14 Dec 2022 14:03:01 GMT

I clicked the "CONFIRM", and then "SEND RESET COMMAND", the result is the same

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Hung Bui — Wed, 14 Dec 2022 13:53:57 GMT

Hi Jimmy,
If you click on CONFIRM, do you see slot 1 being swapped ?

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Jimmy — Wed, 14 Dec 2022 13:50:20 GMT

I have confirmed the main.c is changed before rebuild, and i can see the hash is diffrent from Device Manage app:

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Hung Bui — Wed, 14 Dec 2022 11:28:05 GMT

Hi Jimmy,

Have you tried to change the content of the application and rebuild ? Can be just as little as the text in the log. As far as I know if the hash of the image binary matches with the current image(s) on the chip it will reject the image upload.

RE: NCS2.0 MCUBOOT OTA startup with old firmware not the new one after upload app_update.bin

Jimmy — Tue, 13 Dec 2022 14:22:07 GMT