mcumgr netcore update

RE: mcumgr netcore update

menzM — Wed, 24 May 2023 15:20:46 GMT

Hello everyone,

I try to run a DFU update via bluetooth for app and net core on a nrf53. We have to batch flash around 180 devices, so I would like to run the update automated and not manually with the mobile app.

As we do not have enabled CONFIG_MCUBOOT_SERIAL in the currently running firmware the `mcumgr image upload -n` option is not working for us.

But obviously there is a way because one can perform updates via the mobile app and the dfu_application.zip that just contains the same files and a manifest with consolidated information.

Can you help me please an elaborate how the mobile app is performing the update?

Another question would be how one could confirm what image is currently running on the net core e.g. by getting a hash like we can do with the app core?

thx in advance

Michael

RE: mcumgr netcore update

Amanda Hsieh — Mon, 01 May 2023 14:33:51 GMT

Hi,

[quote user="enukic"]1. Is it possible to revert to a previous version of the net core image if the newly updated image doesn't behave properly?[/quote]

It would revert to a previous image due to a faulty update.

[quote user="enukic"]3. Is there a reason for using -n 3 when uploading image? Why "3"? Could it be any other slot?[/quote]

3 means slot-3 for the new image of the net core.

-Amanda H.

RE: mcumgr netcore update

enukic — Sat, 29 Apr 2023 21:58:09 GMT

Hi,

thanks for the response.

I have two more questions, please:

1. Is it possible to revert to a previous version of the net core image if the newly updated image doesn't behave properly?

3. Is there a reason for using -n 3 when uploading image? Why "3"? Could it be any other slot?

Thanks

Emir

RE: mcumgr netcore update

Amanda Hsieh — Tue, 25 Apr 2023 16:42:07 GMT

Hi,

In the latest version of the tool, it's suggested to execute image test as you did. See https://docs.zephyrproject.org/3.1.0/services/device_mgmt/mcumgr.html

-Amanda H.

RE: mcumgr netcore update

enukic — Fri, 21 Apr 2023 20:29:12 GMT

Hi Amanda Hsieh Thank you for looking further into this.

1. (and 3.) That is strange. I triple-checked on my side, and I'm still getting the same behavior. Please see my mcumgr commands and RTT output from the nRF5340 NETCORE below:

a) This is the printout from the first boot (before the upgrade)

00> *** Booting Zephyr OS build v3.2.99-ncs2 ***
00> [00:00:00.001,617] <inf> hci_rpmsg: Pending update               <<========== I added this message
00> [00:00:00.001,647] <inf> bt_sdc_hci_driver: SoftDevice Controller build revision: 
00>                                             d8 0c 2d 2f 36 ae e2 5c  80 26 80 4c 3f 4d 16 53 |..-/6..\ .&.L?M.S
00>                                             50 96 c7 73                                      |P..s             
00> [00:00:00.002,563] <inf> bt_hci_raw: Bluetooth enabled in RAW mode
00> [00:00:00.036,376] <inf> sync_rtc: Updated timestamp to synchronized RTC by 396 ticks (12084us)
00> [00:00:11.742,340] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:11.742,767] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:11.742,950] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:11.842,926] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:11.843,109] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:11.943,084] <inf> hci_rpmsg: Sent mes.

b) Commands for uploading the image (I'm uploading only netcore image and using no flags with image upload command):

C:\Users\Em>mcumgr conn add cli type="serial" connstring="COM27,baud=115200,mtu=512"
Connection profile cli successfully added

C:\Users\Em>mcumgr -c cli image list
Images:
 image=0 slot=0
    version: 0.0.1
    bootable: true
    flags: active confirmed
    hash: 2d6635f37bf16dbb8172b2306f921a8b627e9623254b555d45681997c81294f3
Split status: N/A (0)

C:\Users\Em>mcumgr -c cli image upload C:\ncsproj\gitlab\headphone\v2_image\net_core_app_update.bin
 198.59 KiB / 198.59 KiB [===================================================================] 100.00% 2.24 KiB/s 1m28s
Done

C:\Users\Em>mcumgr -c cli image list
Images:
 image=0 slot=0
    version: 0.0.1
    bootable: true
    flags: active confirmed
    hash: 2d6635f37bf16dbb8172b2306f921a8b627e9623254b555d45681997c81294f3
 image=0 slot=1
    version: 0.0.1
    bootable: true
    flags:
    hash: 9c5f942103fbfc8e6eaef5a833e7b430f2d3e2e05de11e2599a56e426d4b9ccc
Split status: N/A (0)

C:\Users\Em>mcumgr -c cli reset
Done

c)So, if I only upload the image and perform restart, nothing happens:

00> *** Booting Zephyr OS build v3.2.99-ncs2 ***
00> [00:00:00.001,617] <inf> hci_rpmsg: Pending update                  <<========== Still getting the same message
00> [00:00:00.001,678] <inf> bt_sdc_hci_driver: SoftDevice Controller build revision: 
00>                                             d8 0c 2d 2f 36 ae e2 5c  80 26 80 4c 3f 4d 16 53 |..-/6..\ .&.L?M.S
00>                                             50 96 c7 73                                      |P..s             
00> [00:00:00.002,593] <inf> bt_hci_raw: Bluetooth enabled in RAW mode
00> [00:00:00.036,376] <inf> sync_rtc: Updated timestamp to synchronized RTC by 395 ticks (12054us)
00> [00:00:11.741,851] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:11.742,279] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:11.742,462] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:11.842,437] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:11.842,590] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:11.942,596] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:11.942,779] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.042,755] <inf> hci_rpmsg: Sent message of 71 bytes.
00> [00:00:12.042,938] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.142,883] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:12.145,233] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.243,041] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:12.243,225] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.343,200] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:12.343,383] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.443,359] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:12.443,542] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.543,518] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:12.546,020] <inf> hci_rpmsg: Received message of 11 bytes.
00> [00:00:12.643,676] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:12.643,829] <inf> hci_rpmsg: Received message of 5 bytes.
00> [00:00:12.743,804] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:12.743,957] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.843,933] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:12.844,116] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.944,091] <inf> hci_rpmsg: Sent message of 10 bytes.
00> [00:00:12.944,274] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:13.044,250] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:13.044,433] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:13.144,409] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:13.144,592] <inf> hci_rpmsg: Received message of 8 bytes.
00> [00:00:13.244,567] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:13.244,720] <inf> hci_rpmsg: Received message of 12 bytes.
00> [00:00:13.344,696] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:13.344,879] <inf> hci_rpmsg: Received message of 12 bytes.
00> [00:00:13.444,824] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:13.444,976] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:13.544,952] <inf> hci_rpmsg: Sent message of 19 bytes.
00> [00:00:13.545,135] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:13.645,111] <inf> hci_rpmsg: Sent message of 71 bytes.
00> [00:00:13.645,782] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:13.745,269] <inf> hci_rpmsg: Sent message of 13 bytes.
00> [00:00:13.745,452] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:13.845,397] <inf> hci_rpmsg: Sent message of 30 bytes.
00> [00:00:13.845,611] <inf> hci_rpmsg: Received message of 10 bytes.
00> [00:00:13.945,556] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:13.945,739] <inf> hci_rpmsg: Received message of 19 bytes.
00> [00:00:14.045,715] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:14.045,898] <inf> hci_rpmsg: Received message of 36 bytes.
00> [00:00:14.145,874] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:14.146,057] <inf> hci_rpmsg: Received message of 36 bytes.
00> [00:00:14.246,032] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:14.246,246] <inf> hci_rpmsg: Received message of 5 bytes.
00> [00:00:14.346,191] <inf> hci_rpmsg: Sent message of 7 bytes.

d) Then I do image test on the image that's already uploaded:

C:\Users\Em>mcumgr -c cli image list
Images:
 image=0 slot=0
    version: 0.0.1
    bootable: true
    flags: active confirmed
    hash: 2d6635f37bf16dbb8172b2306f921a8b627e9623254b555d45681997c81294f3
 image=0 slot=1
    version: 0.0.1
    bootable: true
    flags:
    hash: 9c5f942103fbfc8e6eaef5a833e7b430f2d3e2e05de11e2599a56e426d4b9ccc
Split status: N/A (0)

C:\Users\Em>mcumgr -c cli image test 9c5f942103fbfc8e6eaef5a833e7b430f2d3e2e05de11e2599a56e426d4b9ccc
Images:
 image=0 slot=0
    version: 0.0.1
    bootable: true
    flags: active confirmed
    hash: 2d6635f37bf16dbb8172b2306f921a8b627e9623254b555d45681997c81294f3
 image=0 slot=1
    version: 0.0.1
    bootable: true
    flags: pending
    hash: 9c5f942103fbfc8e6eaef5a833e7b430f2d3e2e05de11e2599a56e426d4b9ccc
Split status: N/A (0)

C:\Users\Em>mcumgr -c cli reset
Done

e) I see the change in the logs:

00> *** Booting Zephyr OS build v3.2.99-ncs2 ***
00> [00:00:00.001,617] <inf> hci_rpmsg: Updated                         <<====================== New message is printed
00> [00:00:00.001,678] <inf> bt_sdc_hci_driver: SoftDevice Controller build revision: 
00>                                             d8 0c 2d 2f 36 ae e2 5c  80 26 80 4c 3f 4d 16 53 |..-/6..\ .&.L?M.S
00>                                             50 96 c7 73                                      |P..s             
00> [00:00:00.002,593] <inf> bt_hci_raw: Bluetooth enabled in RAW mode
00> [00:00:00.036,437] <inf> sync_rtc: Updated timestamp to synchronized RTC by 396 ticks (12084us)
00> [00:00:11.741,882] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:11.742,309] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:11.742,492] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:11.842,468] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:11.842,620] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:11.942,626] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:11.942,810] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.042,785] <inf> hci_rpmsg: Sent message of 71 bytes.
00> [00:00:12.042,968] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.142,913] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:12.145,263] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.243,072] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:12.243,255] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.343,231] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:12.343,414] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.443,389] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:12.443,572] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.543,548] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:12.546,051] <inf> hci_rpmsg: Received message of 11 bytes.
00> [00:00:12.643,707] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:12.643,859] <inf> hci_rpmsg: Received message of 5 bytes.
00> [00:00:12.743,835] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:12.743,988] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.843,994] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:12.844,177] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:12.944,152] <inf> hci_rpmsg: Sent message of 10 bytes.
00> [00:00:12.944,335] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:13.044,311] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:13.044,494] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:13.144,470] <inf> hci_rpmsg: Sent message of 15 bytes.
00> [00:00:13.144,653] <inf> hci_rpmsg: Received message of 8 bytes.
00> [00:00:13.244,628] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:13.244,781] <inf> hci_rpmsg: Received message of 12 bytes.
00> [00:00:13.344,757] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:13.344,940] <inf> hci_rpmsg: Received message of 12 bytes.
00> [00:00:13.444,885] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:13.445,037] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:13.545,013] <inf> hci_rpmsg: Sent message of 19 bytes.
00> [00:00:13.545,196] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:13.645,172] <inf> hci_rpmsg: Sent message of 71 bytes.
00> [00:00:13.645,843] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:13.745,330] <inf> hci_rpmsg: Sent message of 13 bytes.
00> [00:00:13.745,513] <inf> hci_rpmsg: Received message of 4 bytes.
00> [00:00:13.845,458] <inf> hci_rpmsg: Sent message of 30 bytes.
00> [00:00:13.845,672] <inf> hci_rpmsg: Received message of 10 bytes.
00> [00:00:13.945,617] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:13.945,800] <inf> hci_rpmsg: Received message of 19 bytes.
00> [00:00:14.045,776] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:14.045,959] <inf> hci_rpmsg: Received message of 36 bytes.
00> [00:00:14.145,935] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:14.146,118] <inf> hci_rpmsg: Received message of 36 bytes.
00> [00:00:14.246,093] <inf> hci_rpmsg: Sent message of 7 bytes.
00> [00:00:14.246,307] <inf> hci_rpmsg: Received message of 5 bytes.
00> [00:00:14.346,252] <inf> hci_rpmsg: Sent message of 7 bytes.

2. Ok. Understood.

4. Thank you. This looks interesting. I'll check it out.

RE: mcumgr netcore update

Amanda Hsieh — Wed, 19 Apr 2023 14:08:42 GMT

Hi,

1. I have tested the command without -n and see the uploaded can work. However, the image cannot be booted as expected.

See https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/samples/subsys/mgmt/mcumgr/smp_svr/README.html#direct-image-upload-and-image-mapping-to-mcuboot-slot

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/services/device_mgmt/mcumgr.html#image-management

2. Only support for app core.

3. I cannot reproduce. Please post the completed commands you used.

4. See my colleague's sample https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/nrf5340

-Amanda H.

RE: mcumgr netcore update

enukic — Mon, 17 Apr 2023 22:24:05 GMT

Hi Amanda Hsieh Thank you for the response. I was able to perform netcore DFU following steps form your post. 👍

I do have a couple of follow-up questions:

Regarding mcumgr image upload flags (-n specifically). For me, the netcore upgrade worked with and without flags specified in the command. Is this expected behavior? How can the bootloader know where to apply the new image? Could you point me to any documentation regarding --image int flag? How did you come to use "-n 3" for the netcore upgrade?
Is there a way of seeing all the images and slots available on a target with mcumgr image list command? So far I was only able to see the "main" app core image, and the image that I upload with mcumgr (image 0, slot 1).
I was following the steps form your post, but I wasn't observing the same behavior. For example:
- after uploading image, it showed up when I requested image list (image 0, slot 1)
- I had to call mcumgr image test in order to load the image into the netcore. Only uploading image and restarting the device didn't perform netcore upgrade, like in your example.
- After the image was in the netcore, it's there permanently. Even if I don't mcumgr image confirm, it will stay.
- The question is: Is there a way of reverting to the previous netcore image?
Any additional documentation/examples on multi-image DFU is welcome.

Thanks

Best regards

Emir

RE: mcumgr netcore update

Amanda Hsieh — Tue, 11 Apr 2023 20:05:41 GMT

Hi,

[quote user=""]I have been trying to implement DFU using mcumgr over Shell, for both app and netcore on nRF5340.[/quote]

I have nRF53 MCUBoot Serial Recovery Sample over USB CDC for netcore and appcore with mcumgr in this post, but it's for v2.2.0. Hope that can help you.

Regards,
Amanda H