The Limitations subsection of the Zigbee Section here contains the following paragraph:
- OTA DFU: Migration from the nRF5 SDK for Thread and Zigbee version earlier than v4.0.0 is not supported.
Does it mean, that an application based on the v3.1.0 of Thread and Zigbee SDK, cannot be Zigbee OTA upgraded to an application based on the newest SDK v4.0.0? What is the reason for that?
As I briefly looked through the Zigbee OTA Upgrade Client Example, it is almost the same (excluding the default size of flash with the Zigbee settings). The version of Bootloader settings is 2 as it was, and from the DFU library and bootloader point of view, all looks the same.
Also, here I found the note:
The NVRAM in the stack v3.3.0 is not compatible with NVRAM of the stack version 3.1.0. All previous NVRAM will be automatically erased and filled with default values.
Is this the reason that prevents migration?
If we use the similar flash size for the Zigbee settings, and didn’t use the Zigbee production configuration page, just UICR customer registers, suppose we will be able to make the Zigbee OTA upgrade from the v3.1.0 SDK to v4.0.0 SDK, but the device after the reset will be like after factory reset, so will forget the Zigbee network, etc. Is it right?
So, if my understanding right, then saying exactly, we can make an OTA upgrade, but with the side effect (NVRAM erasing)?
