Mesh OTA DFU

RE: Mesh OTA DFU

Joakim Jakobsen — Wed, 21 Aug 2019 08:39:55 GMT

Hi.

Talked to our Mesh team about this:
In theory this is possible. However, it will require a lot of work, and we haven't tested this so we can't promise anything.
You will most likely run into some problems with the format on BLE-DFU, as it doesn't have the same parameters in the metadata (missing app and company ID). A suggestion from the Mesh team was that it could be better to try and add a GATT service in the Mesh-bootloader with a custom format, even though this will lead to quite some extra work on the phone side.

I'm afraid I don't have any more specific information about this.

Best regards,
Joakim Jakobsen

RE: Mesh OTA DFU

EAn — Tue, 20 Aug 2019 14:04:25 GMT

Greetings Joakim Jakobsen and remaining audience of experts,

Has anyone found a workaround this limitation yet? By "this limitation" I mean: not being able to use Mesh DFU and BLE DFU concurrently in the same device.

Is there anyway to use BLE DFU in one of the mesh nodes, and have that node relay the firmware package to the remaining network via Mesh DFU? In my understanding the MeshDFU bootloader is the sole responsible for propagating the chunks of firmware, so my guess is that there would have to be a way of integrating that in the application side in order to keep the BLE-DFU bootloader...

Can anyone validate this?

Thank you very much!

Best regards,

//EA

RE: Mesh OTA DFU

Joakim Jakobsen — Wed, 17 Jul 2019 11:48:47 GMT

I'm afraid the bootloaders can't be combined, because they are quite different.

You can combine Mesh DFU and BLE DFU inside your Mesh network, so that some nodes can be upgraded using BLE DFU and the rest using Mesh DFU. But note that if you choose to have BLE DFU for some nodes, those nodes will not have Mesh DFU.

So that would be up to you to decide if that is something that can work for you.

Best regards,
Joakim

RE: Mesh OTA DFU

mregan11 — Tue, 16 Jul 2019 11:17:24 GMT

I'm wondering if the mesh bootloader and traditional bootloader can be combined, thus offering two ways of updating firmware. The advantages of mesh DFU are obvious, but I think there are also situations where performing a DFU on a handful of devices in a very short amount of time is also beneficial.

RE: Mesh OTA DFU

Joakim Jakobsen — Tue, 16 Jul 2019 06:57:16 GMT

Sorry, not quite sure what you are asking here.

You need to use a different bootloader if you want to use Mesh DFU, opposed to traditional DFU.

Best regards

RE: Mesh OTA DFU

mregan11 — Fri, 12 Jul 2019 12:36:42 GMT

Is it possible for a bootloader to accommodate firmware updating using either mesh OR through a traditional BLE connection?

RE: Mesh OTA DFU

Joakim Jakobsen — Tue, 11 Jun 2019 10:31:09 GMT

Hi.

The bootloaders are quite different in the way they work. But if you want to do this, you can build your application as a Mesh application (without using Mesh) and then use the normal Mesh DFU update process to update your "Mesh" application.

Note that you will need to flash the Mesh bootloader instead of the normal bootloader. Also, using Mesh DFU will use 1 hour for a 100kB image.

Best regards,
Joakim