Nrf DFU Application Library

[Mark G.]

Hi all,

I have Nrf52 devices that use Nrf DFU with "Buttonless Secure DFU Service".

I would like to integrated the ability do to firmware update the devices to our "fleet management software". 

I could not find a clear definition of the internal services and characteristics used and what exact control logic / payloads are needed to properly do a firmware update via ble.

I know that the update works with nrf tools like nrf connect. But I need it in my own software. Are there any open libraries / deeper documentation?

Thanks

Best

Mark

[Edvin]

Hello Mark,

It has been a while since I looked into this, and our documentation platform has changed a couple of times since this was released, but it should be able to find the relevant information from here:

https://docs.nordicsemi.com/bundle/nrf5_SDK_v17.1.1/page/lib_bootloader_modules.html

Particularly the message sequence chart is relevant:

https://docs.nordicsemi.com/bundle/nrf5_SDK_v17.1.1/page/lib_dfu_transport_ble.html

Also, this site describes all the opcodes and their parameters:

https://docs.nordicsemi.com/bundle/nrf5_SDK_v17.1.1/page/lib_dfu_transport.html

Another point of interrest that I can think of is the DFU Master Code from this blog post:

https://devzone.nordicsemi.com/guides/short-range-guides/b/software-development-kit/posts/getting-started-with-nordics-secure-dfu-bootloader#h108sjziaxo3m81rkgr1has5r1d72qtu

I know that this is a serial implementation, and not BLE, but the protocol is the same as in BLE. It is just the transport layer that has changed. 

Best regards,

Edvin

[lennyfrank]

Hi Edvin,

Do you know if Nordic has any guidance or examples on handling BLE-specific edge cases during DFU, like packet loss or reconnection after a dropped link? Pips NYT

Thanks!

[Edvin]

Hello,

Packet loss is always handled by the Bluetooth stack, so that is not something you need to take into consideration. It is specified in the specification, so as long as the application that you develop for your management fleet uses a certified Bluetooth controller, then that is already handled for you. All packets are retransmitted until they are acknowledged correctly.

In events of a disconnect, it is a bit up to you. One way is to start over, but it is possible to save the progress, and continue where you left off. This depends on the configurations in the bootloader, but there should be something in sdk_config.h in your bootloader called "Save progress in flash" or something. It depends on what SDK version you are using for your bootloader. Let me know what version you are using if you can't find it. In SDK 17.1.0, it is called NRF_DFU_SAVE_PROGRESS_IN_FLASH.

So if you disconnect, and resume directly after, the progress will be saved either way, but if your nRF e.g. runs out of battery, or has a reboot for some other reason, then you will need to start over, if this option is not set. 

For the computer side, please read the sections: "Transfer of an init packet" and "Transfer of a firmware image" from the second link in my previous reply.

Best regards,

Edvin