DFU BLE bootloader doesn't seem to work

RE: DFU BLE bootloader doesn't seem to work

Jerry Easley — Wed, 16 Aug 2023 17:45:18 GMT

Hi Hung,

Thank you ever so much for helping me with this problem; I would never have gotten through it without your kind help,

Regards,

Jerry

RE: DFU BLE bootloader doesn't seem to work

Hung Bui — Wed, 16 Aug 2023 14:49:55 GMT

Hi Jerry,
Yes SMP_SVR is integrated into your application automatically when you enable those configuration you find in the smp_svr (both prj.conf and the overlay_bt.conf)

RE: DFU BLE bootloader doesn't seem to work

Jerry Easley — Wed, 16 Aug 2023 13:53:38 GMT

Hi Hung,

I apologize, it is working: I must have had too much coffee and not enough sleep.

I have just one other question if I may abuse you further:

My understanding of how this works is as follows:

Any application that I want to update from time to time over BLE will necessarily have to include the equivalent of the smp_svr code; is that correct?

Regards,

Jerry

RE: DFU BLE bootloader doesn't seem to work

Hung Bui — Wed, 16 Aug 2023 13:12:57 GMT

Hi again,

Have you built the blinky with MCUBoot added ? The image should be configured so that it can run on slot 0

My suggestion is to do an update with the same smp_svr image, just change something like advertising name, or blink another LED but still the same smp_svr application.

RE: DFU BLE bootloader doesn't seem to work

Jerry Easley — Wed, 16 Aug 2023 12:56:47 GMT

Hi Hung,

Ok this is what I did:

(.venv) jerry@Ubuntu:~/zephyrproject$ sudo ~/go/bin/mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='Zephyr' image upload ~/MyApps/blinky/build_dk/zephyr/app_update.bin
23.03 KiB / 23.03 KiB [====================================================================================================================] 100.00% 10.43 KiB/s 2s
Done
(.venv) jerry@Ubuntu:~/zephyrproject$ sudo ~/go/bin/mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='Zephyr' image list
Images:
image=0 slot=0
    version: 0.0.0
    bootable: true
    flags: active confirmed
    hash: ea9c889031e33c8c9c500e00e8ed94454f536368c499c186688f323a48f973b4
image=0 slot=1
    version: 0.0.0
    bootable: true
    flags:
    hash: 582ef2530f15968c39513443f312418a0179dac2050b1146bd727467df042564
Split status: N/A (0)
(.venv) jerry@Ubuntu:~/zephyrproject$ sudo ~/go/bin/mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='Zephyr' image test 582ef2530f15968c39513443f312418a0179dac2050b1146bd727467df042564 + a reset
Images:
image=0 slot=0
    version: 0.0.0
    bootable: true
    flags: active confirmed
    hash: ea9c889031e33c8c9c500e00e8ed94454f536368c499c186688f323a48f973b4
image=0 slot=1
    version: 0.0.0
    bootable: true
    flags: pending
    hash: 582ef2530f15968c39513443f312418a0179dac2050b1146bd727467df042564
Split status: N/A (0)
(.venv) jerry@Ubuntu:~/zephyrproject$ sudo ~/go/bin/mcumgr --conntype ble --connstring ctlr_name=hci0,peer_name='Zephyr' image confirm 582ef2530f15968c39513443f312418a0179dac2050b1146bd727467df042564 + a reset
Images:
image=0 slot=0
    version: 0.0.0
    bootable: true
    flags: active confirmed
    hash: ea9c889031e33c8c9c500e00e8ed94454f536368c499c186688f323a48f973b4
image=0 slot=1
    version: 0.0.0
    bootable: true
    flags: pending
    hash: 582ef2530f15968c39513443f312418a0179dac2050b1146bd727467df042564
Split status: N/A (0)

My blinky application does not run.

I have reset the device with vscode: it doesn't run.

I have reset the device with the reset button: it does not run.

I have removed power and applied power: it does not run.

I am sure I have switched images because my smp_svr is no longer manifest.

Maybe I have not properly prepared my blinky application?

Regards,

Jerry

RE: DFU BLE bootloader doesn't seem to work

Hung Bui — Wed, 16 Aug 2023 12:10:25 GMT

Hi Jerry,

When in doubt , just try both ;)

Just kidding, you should use the one at slot 1 : 582ef2530f15968c39513443f312418a0179dac2050b1146bd727467df042564

The original image will always at slot 0. It's the image that will run at boot (after MCUBoot). When you do test, image at slot 1 will be temporarily copied to slot 0 and revert back after rest.

When you do confirm the image at slot 1 will overwrite the one at slot 0 and run at next boot.

RE: DFU BLE bootloader doesn't seem to work

Jerry Easley — Wed, 16 Aug 2023 11:34:41 GMT

Hi Hung,

You will have to forgive me; I have read the documentation a 1000 times; I don't understand it; it if full of buzz words which are not defined and I can't figure out what it is talking about.

This is what I see:

Images:
image=0 slot=0
    version: 0.0.0
    bootable: true
    flags: active confirmed
    hash: ea9c889031e33c8c9c500e00e8ed94454f536368c499c186688f323a48f973b4
image=0 slot=1
    version: 0.0.0
    bootable: true
    flags: pending
    hash: 582ef2530f15968c39513443f312418a0179dac2050b1146bd727467df042564
Split status: N/A (0)

As you can see I have two images. I presume one is my smp_svr application and one is my binky application; I don't know which is which.

I don't know how this works; I have uploaded my blinky image, apparently, successfully. From your comments above I need to do two additional steps in order to get my blinky application running. In order to do that I need to specify the <hash>, of which I have two; which should I use?

Let us suppose that I have my blinky application up and running and I want to update it; how do I do that if the smp_svr is no longer active?

Regards,

Jerry

RE: DFU BLE bootloader doesn't seem to work

Hung Bui — Wed, 16 Aug 2023 11:05:34 GMT

Hi Jerry,
Please read the documentation.
https://docs.zephyrproject.org/latest/services/device_mgmt/mcumgr.html
You will see the hash when you call

mcumgr <connection-options> image list

RE: DFU BLE bootloader doesn't seem to work

Jerry Easley — Wed, 16 Aug 2023 11:03:45 GMT

What is the <hash> item and how do I obtain it?

Jerry

RE: DFU BLE bootloader doesn't seem to work

Hung Bui — Wed, 16 Aug 2023 08:08:49 GMT

Hi Jerry,

Please try to do FOTA update with your tablet before you try with the mcumgr. You can use nRF Connect or nRF Device Manager to do update.

For a FOTA process to complete you would need to either test or confirm the new image (confirm is done automatically in the app on the tablet)

Please take a look at the documentation here: https://docs.zephyrproject.org/latest/services/device_mgmt/mcumgr.html

For test (only run new image once then revert back to original application) you need to do:

mcumgr <connection-options> image test <hash> 

+ a reset

For confirm (permanently switch the imag) you need to call:

mcumgr <connection-options> image confirm <hash> 

+ a reset.

RE: DFU BLE bootloader doesn't seem to work

Jerry Easley — Wed, 16 Aug 2023 04:13:35 GMT

Hi Hung,

Just a side note:

I tried to build smp_svr with a board, nreff52840dongle_nrf52840, I get a build error:

[74/140] Building C object modules/nrf/subsys/bluetooth/controller/CMakeFiles/..__nrf__subsys__bluetooth__controller.dir/hci_driver.c.obj
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /home/jerry/ncs/toolchains/1f9b40e71a/usr/local/bin/cmake --build /home/jerry/MyApps/smp_svr/build_dongle

There seems to be some kind of issue with dongles and bootloaders: do you know anything about it?

Regards,

Jerry

RE: DFU BLE bootloader doesn't seem to work

Jerry Easley — Wed, 16 Aug 2023 03:19:59 GMT

Hi Hung,

I have (I think) gotten the smp_svr sample working correctly. I have established a serial connection under vscode and it will interact with me. However, I have modified both the blinky and hello_world sample applications to upload to the smp_svr via ble. I get the following message: "[00:02:31.535,949] <inf> smp_bt_sample: Disconnected (reason 0x13)" from the smp_svr. I suspect that I have not correctly configured the apps I am trying to upload.

This is my prj.conf for blinky:

CONFIG_GPIO=y
CONFIG_BOOTLOADER_MCUBOOT=y 
CONFIG_MCUBOOT_SIGNATURE_KEY_FILE=""

This is the serial log file at reset

uart:~$ *** Booting Zephyr OS build v3.3.99-ncs1-1 ***
[00:00:00.006,927] <inf> bt_hci_core: Identity: C7:28:33:33:F4:D5 (random)
[00:00:00.006,958] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x1077, manufacturer 0x0059
[00:00:00.006,988] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x1077
[00:00:00.007,904] <inf> smp_bt_sample: Advertising successfully started

In a terminal, I entered my upload command:

The serial log responded with:

[00:00:00.007,965] <inf> smp_sample: build time: Aug 15 2023 05:04:51
[00:01:52.927,215] <inf> smp_bt_sample: Connected
[00:01:53.752,197] <inf> mcumgr_img_grp: Erased 0x6000 bytes of image slot
[00:01:53.849,670] <inf> mcumgr_img_grp: Erased 0x1000 bytes of image slot trailer
[00:01:55.670,562] <inf> smp_bt_sample: Disconnected (reason 0x13)
[00:01:55.672,058] <inf> smp_bt_sample: Advertising successfully started

The blinky application, apparently, was not started; (led0 not blinking).

Do you have any ideas?

Regards,

Jerry

RE: DFU BLE bootloader doesn't seem to work

Hung Bui — Tue, 15 Aug 2023 11:32:37 GMT

Hi Jerry,

You should use app_update.bin. It's the signed binary that you can use to do FOTA.

You can read more about different hex/bin files here:
developer.nordicsemi.com/.../multi_image.html

RE: DFU BLE bootloader doesn't seem to work

Jerry Easley — Tue, 15 Aug 2023 11:04:28 GMT

I am trying to upload my blinky sample to the smp_svr; I'm getting errors because the zephyr.bin file is unsigned, Is there a way to sign it under vscode?

Regards,

Jerry

RE: DFU BLE bootloader doesn't seem to work

Jerry Easley — Tue, 15 Aug 2023 10:11:55 GMT

Hi Hung,

I followed your excellent instructions and voila, I can see the advertisement on iPad!

Thank you so much!

Regards,

Jerry

RE: DFU BLE bootloader doesn't seem to work

Hung Bui — Tue, 15 Aug 2023 09:38:48 GMT

Hi Jerry,
I attached here how i built the project with VS Code:
First you create new application based on smp_svr:

After that you create the configuration, and select the overlay_bt.conf as the Kconfig fragments, make sure you click OK after you select the file:

After the build, you should be able to find overlay_bt.conf in the project configuration:

I attached here the hex file that worked for me:
devzone.nordicsemi.com/.../4544.merged.hex

RE: DFU BLE bootloader doesn't seem to work

Jerry Easley — Tue, 15 Aug 2023 08:42:41 GMT

I do not see the device at all on the mobile app.

RE: DFU BLE bootloader doesn't seem to work

Hung Bui — Mon, 14 Aug 2023 13:43:48 GMT

Hi Jerry,
Just want to double check, now do you see the smp_svr advertising ?
Can you do DFU update via tablet or PC ?

RE: DFU BLE bootloader doesn't seem to work

Jerry Easley — Mon, 14 Aug 2023 13:27:48 GMT

A little update:

I corrected the length parameter of:

BT_DATA(BT_DATA_NAME_COMPLETE, "Zephyr_DFU", 8),

it now reads

BT_DATA(BT_DATA_NAME_COMPLETE, "Zephyr_DFU", 11),

I added a little code to blink led0; I am now sure the smp_svr application is up and running.

Regards,

Jerry

RE: DFU BLE bootloader doesn't seem to work

Jerry Easley — Mon, 14 Aug 2023 12:19:48 GMT

Hi Hung,

My SDK is 2.4.1; toolchain is 2.4.0.

This is the command I used to build thee smp_svr.

(.venv) jerry@Ubuntu:~/zephyrproject$ west build \
            -b nrf52840dk_nrf52840 \
            zephyr/samples/subsys/mgmt/mcumgr/smp_svr \
            -- \
            -DEXTRA_CONF_FILE=overlay-bt.conf

:It sounds like you are assuming I'm building smp_svr under VSCODE; I am following the instructions, which use west command line tools to build mcuboot, and smp_svr in discrete steps. I don't understand how to do this under VSCODE; the documentation is enigmatic and confusing. In addition, including the necessary prj.conf statements for mcuboot causes build errors. If you know how to do it under VSCODE I would prefer to do it that way.

I did use my iPad to check for the advertisement; The scanner did not display the device.

Regards,

Jerry

RE: DFU BLE bootloader doesn't seem to work

Hung Bui — Mon, 14 Aug 2023 09:24:12 GMT

Hi Jerry,

Could you please let me know which NCS SDK version you are using ? The implementation of smp_svr has been changed lately especially in NCS v2.3.0 and NCS v2.4.0

When you build smp_svr, did you use the overlay-bt.conf in addition to the prj.conf ?

Please be aware that when you build smp_svr it will automatically build MCUBoot as the child image so you don't have to flash anything else in addition.

My suggestion is to use a phone to check if the device advertise or not after you flash. You then can use nRF Connect app on the phone to do an DFU update.
After you can verify that it works with a phone, then you can continue the test with mcumgr on PC.