How do I add a DFU support for nRF Connect SDK in Linux

[matan_spada]

Hello, 

I'm using Linux (Ubuntu) and I would like to add a DFU support to my app.

Tried to follow Add DFU support to your application but it seems to me that some of the steps really focus on the sample they used in the article.

Additionally, I get an error when trying to add the includes described in the article, so I don't know how to proceed from here.

Advice and tips are welcome :)

[Hung Bui]

Hi Matan, 

The instruction in the blog can be a bit out of date due to some changes in the latest SDK. 

Could you give us more information about the issue you are facing ? What kind of DFU you want to implement in your application ? BLE or UART or other ? 
Please post your error/build log. 

[matan_spada]

Hi, Thanks for the response.

I would like to implement the BLE DFU.

The error I'm getting is related to #include <mgmt/mcumgr/smp_bt.h>.

fatal error: mgmt/mcumgr/smp_bt.h: No such file or directory
    9 | #include <mgmt/mcumgr/smp_bt.h>

[matan_spada]

I will explain what I mean.

For example, in the last two steps of the "DFU over bluetooth" section (shown below), it seems that these are things related to the sample "ble_dfu_peripheral_lbs" and I don't understand how to do it in any other sample (for example, I want to implement the DFU support it in the blinky sample).

"

• Remove the LBS Service UUID from the scan response packet, and replace it with the SMP service UUID:

  BT_DATA_BYTES(BT_DATA_UUID128_ALL,
  		      0x84, 0xaa, 0x60, 0x74, 0x52, 0x8a, 0x8b, 0x86,
  		      0xd3, 0x4c, 0xb7, 0x1d, 0x1d, 0xdc, 0x53, 0x8d),

• Lastly, add these lines right before bt_conn_cb_register:

  printk("build time: " __DATE__ " " __TIME__ "\n");
  os_mgmt_register_group();
  img_mgmt_register_group();
  smp_bt_register();

"

[Hung Bui]

Hi Matan, 

If you are getting started I would suggest to try testing on the lbs example (located at \nrf\samples\bluetooth\peripheral_lbs) . 
After you have tested and managed to do DFU you can start implementing the same to your application. 

You don't have to add the SMP service UUID to the advertising packet if you don't want to. By adding the SMP service UUID to the advertising packet, it's easier for the app on the phone to detect if it has the DFU support or not. It's optional.
You can call 
os_mgmt_register_group();
img_mgmt_register_group();
smp_bt_register();

right after bt_enable() in your code. 

The blinky example doesn't have BLE support by default so more work need to be done. Please try to base your application on a BLE example. 

[matan_spada]

Thanks, I changed to lbs example.

For some reason there is a problem with the compilation of the #include "img_mgmt/img_mgmt.h" library.

Do you know something about it?

[Hung Bui]

Hi Matan, 
How did you install Zephyr ? 
Could you try to compile using VSCode ? 
Could you try my example here to see if you have the same problem ? It built with NCS v2.2.0 and worked fine for me. 

peripheral_lbs_smp.zip

[matan_spada]

First of all, thanks!

I ran the program, the problem was that the order of the includes was incorrect.
I changed it and now it works.

By the way,

1. Is there a specific guide through which I can understand how to implement BLE support in any program or just i should try and understand it from the peripheral_lbs example?

2. Is it possible to also do a DFU OTA for the second stage bootloader?
all the references I saw was old versions.

[Hung Bui]

Hi Matan, 

1. You can start from here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/connectivity/bluetooth/bluetooth-dev.html#

We have some guides in the getting started here:  nRF Connect SDK Bluetooth Low Energy tutorial part 1: Custom Service in Peripheral role 

and here: 
NUS on nRF Connect SDK: The Nordic UART Service with the nRF Connect SDK

I would suggest to study the peripheral_lbs as your base for your application. 

2. Yes it's possible to add an immutable bootloader (B0) so that you can update the MCUboot. Please see here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bootloader/README.html

Basically you need to add CONFIG_SECURE_BOOT into prj.conf to have B0 added. 

[matan_spada]

Thanks a lot.

I will start researching and going over things.

[matan_spada]

Regarding section 2,
I have an app with bootloader B0 and MCUBoot in the second stage.
I have done a DFU OTA for the app itself.

Now I'm trying to do an update to MCUBoot using BLE.
Does it happen the same way the firmware update happens (described in the Add DFU support to your application article) or there is a different way to to it?

[Hung Bui]

Hi Matan, 
It's a bit tricky when doing MCUBoot update. You would need to choose the exact slot you want to update. If your current MCUBoot is running on slot S0  you should use the image for s1 slot : 

signed_by_mcuboot_and_b0_s1_image_update.bin

If your MCUBoot is running on S1 , then you need to use the image for s0: 

signed_by_mcuboot_and_b0_s0_image_update.bin

[matan_spada]

Hi, thanks.
How can I configure that?

I tried to look in the Kconfig for some configuration options but culdn't find any.

In the Kconfig I set  "use secure Bootloader", 
and I enabled MCUBoot by adding these lines:

CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_SECURE_BOOT=y

According to this output, what can I understand about which slots I used?

*** Booting Zephyr OS build v3.2.99-ncs1 ***
Attempting to boot slot 0.
Attempting to boot from address 0x9200.
Verifying signature against key 0.
Hash: 0x0f...a7
Firmware signature verified.
Firmware version 1
*** Booting Zephyr OS build v3.2.99-ncs1 ***
I: Starting bootloader
I: Primary image: magic=bad, swap_type=0x3, copy_done=0x2, image_ok=0x2
I: Secondary image: magic=bad, swap_type=0x0, copy_done=0x1, image_ok=0x1
I: Boot source: none
I: Swap type: none
I: Primary image: magic=bad, swap_type=0x1, copy_done=0x2, image_ok=0x2
I: Secondary image: magic=bad, swap_type=0x0, copy_done=0x1, image_ok=0x1
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0x23000
*** Booting Zephyr OS build v3.2.99-ncs1 ***