Use Mesh DFU but on a non-mesh BLE example

[Jeffe]

Hi,

Currently I would like to implement mesh dfu (the dfu thats in the nrf5 SDK for Mesh 5.0.0) but on a regular BLE-only application. 

The easiest path I see doing it is to simply take an example from the Mesh SDK, add code from the nrf5 17.1.0 SDK accordingly and enable the DFU. This I already have done successfully.

While it is easy to integrate code from the nrf5 SDK 17.1.0 into a Mesh example, however, I find it not ideal to need to use the nrf5 SDK for Mesh to get the benefits of the mesh DFU, since technically the mesh DFU is not actually truly Bluetooth Mesh but instead uses the nRF OpenMesh protocol. In theory, if I am not mistaken, this means that the Mesh DFU shouldn't need the a Bluetooth Mesh stack to work? But how practical is it to do this is my main question

At a glance, it seems like the OpenMesh DFU is well-integrated with the rest of the Mesh SDK. My question is how difficult would it be to decouple the mesh DFU code from the Mesh SDK? I would like to use the OpenMesh DFU but I don't need the actual rest of the Bluetooth Mesh stack, and the obstacle is that in the current code of the Mesh SDK, the DFU code is initialized within the function that initializes the Bluetooth Mesh stack.

Thanks in advance

[Mttrinh]

Hi,

You are correct that this is theoretically possible to do but it is not particularly easy task to accomplish. Unfortunately, this is something you have to implement yourself.