DFU Options

RE: DFU Options

Hung Bui — Wed, 25 Apr 2018 13:22:22 GMT

I afraid we don't have a solution like that right now.

But I believe it's shouldn't be too hard to implement.

What you need to do is instead of one node receiving the new image view UART, you change the transportation to BLE using either GATT proxy or normal BLE. Just one node need this modification as it can then spread the image out as we are doing now with the Mesh DFU solution.

RE: DFU Options

Chuppster — Wed, 25 Apr 2018 12:52:34 GMT

Thank you for the reply! If I use side-by-side DFU in MESH, is there a way to update from a proxy provisioner (a phone)? Basically, we want to be able to update from a phone but need to use a MESH network.

RE: DFU Options

Hung Bui — Wed, 25 Apr 2018 12:46:29 GMT

Hi Adrian,

If you have a look here. You can find that we have two option, one is side-by-side dfu update and one is bootloader mode.

In side-by-side DFU, your application works normally when receiving new image and only switch to bootloader to replace the app.

If you don't want to do background DFU, you can do blocking dfu (bootloader mode), the application will switch to bootloader and will not operate in normal mode until a new image is transferred. To switch from application to bootloader, you don't need to press and hold a button but call nrf_mesh_dfu_jump_to_bootloader() to jump.

We currently don't have a solution for BLE + Mesh DFU yet. But it's possible to implement one. Just need a logic to switch to the BLE bootloader when needed.