The nRF5 SDK example for Thread and Zigbee OTA takes a long time

[Alexey_B]

Hello DevZone,

I'm using nRF5 SDK for Thread and Zigbee v4.2.0 and trying to test Zigbee OTA example.

I'm following this guide https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_tz_v4.2.0%2Fzigbee_example_ota_examples.html  and there was some troubles that where answered here nRF5 SDK for Thread and Zigbee OTA Example  .

Anyway it worked but the OTA process took me about 1 hour. I tried this example 4 times and the time is the same. In my opinion, this is too slow for a 270Kb package.

Is 1 hour OTA normal or did I just get something wrong?

Maybe I need to use a sniffer to see what errors are causing it to take such a long time. If so, what to look for?

[Hung Bui]

Hi Alexey,

Could you try to capture a sniffer trace of the DFU process ? 

A while ago we have this blog that showed that we updated the client image and it took about 26 minutes arcording to the author. So what you observed of about an hour is a little bit strange. The blog also show you how to setup the sniffer. 

We are suspecting the minimum block period may do something here. But we would need to have a look at the sniffer trace to be sure. 

I assume you use one of NRF52840 as the server ? and another one as the client ? 

[Alexey_B]

Thank you Hong Bui for your reply,

So the example you linked shows an OTA time of around 26 minutes. Is this the expected OTA update time?

I'll be doing some OTA experiments in about a week and I'll be able to provide more data.

[Elfving]

Hello Alex, I will take over this case for now as Hung is away on Tech Tour.

Alexey_B said:

Is this the expected OTA update time?

For the setup described in the blog, yes. Note that an OTA over a mesh network is a complex thing, and the time it takes would likely depend on the network.

Regards,

Elfving