DFU download process porting into the application

RE: DFU download process porting into the application

Max Liao — Thu, 16 Apr 2020 06:29:48 GMT

Hi Sigurd.

Thanks for the reply and share the post, it's really helpful.

I had modified it and made it work through BLE transport layer.

Thanks.

RE: DFU download process porting into the application

Sigurd — Tue, 14 Apr 2020 15:45:09 GMT

[quote user="MaxLiao"]Like the DFU download service initiate in the application, not in the bootloader[/quote][quote user="MaxLiao"]Is this possible?[/quote]

Yes, technically it's possible. You might find this post useful: https://devzone.nordicsemi.com/f/nordic-q-a/46336/bootloader-no-transport-dual-bank-dfu-and-dependencies/185176#185176

RE: DFU download process porting into the application

Max Liao — Mon, 23 Mar 2020 10:05:16 GMT

Hi Sigurd

I will use BLE as my transport layer BTY.

RE: DFU download process porting into the application

Max Liao — Fri, 20 Mar 2020 02:01:42 GMT

Hi Sigurd.

Thanks for the reply.

What I mean is to move or porting the download parts of DFU from bootloader to application actually,

To make the firmware download process runs in the application and the image copy still in the bootloader.

Like the DFU download service initiate in the application, not in the bootloader

Is this possible?

If so, then should the download process can be run in the background (If the DFU service is in application)?

Thanks.

RE: DFU download process porting into the application

Sigurd — Thu, 19 Mar 2020 13:49:34 GMT

Hi,

What transport layer would you be using ?

If you want background DFU, and BLE as the transport layer, then this is not something that is supported by the bootloader in the nRF5-SDK. If this is a mandatory requirement for your project(Background DFU over BLE), then the only option I see is to switch to the BLE Mesh bootloader and support mesh in your application. But note that background BLE Mesh DFU takes much longer time than regular BLE DFU.

Edit: You also have the bootloader in examples\iot\bootloader, see this post.