Thread DFU support in nRF Connect SDK

[Bhumika]

We have built our application in nRF SDK for Thread and Zigbee. Since nRF SDK for Thread and Zigbee is in maintenance mode now, we plan to move our application to nRF Connect SDK.

With respect to nRF Connect SDK, I have the following queries:

1. Is DFU OTA supported on Thread in nRF Connect SDK?

2. If yes, can I upgrade my current devices which are based on nRF SDK for Thread and Zigbee and are already installed in the field, via DFU OTA to nRF Connect SDK based application?

We understand that Thread 1.2 specs have good features with respect to high-density network performance and low battery consumption. So, should we move our current implementation which is based on nRF SDK for Thread and Zigbee to nRF Connect SDK?

Looking forward to hear from you.

[Simonr]

Hi

In general, in NCS, DFU is done by getting the DFU image into the second bootloader partition, then rebooting and letting the bootloader do the swap.

How the image gets to the device is up to the application. How to add DFU to an nRF Connect SDK application is described here. I would recommend you find out what sample project you would like to start out with, and then start trying to add DFU to the sample project, and rather ask specific questions if/when you are stuck.

Best regards,

Simon

[Bhumika]

Thank you Simon,

This sounds good.

In this example, there is no provision for DFU over thread protocol.

I need to do DFU over the Thread protocol. Do you have any blog on DFU over the thread protocol in nRF Connect SDK?