Additional information for Zigbee FOTA

Setup:

Zigbee OTA Update Server:  Digi IX15 Gateway (XBee3 - coordinator)

Endpoint device:  UBlox NORA B126 (nrf5340 - 1 to many end points)

Looking for:

1) And, additional help understanding the client and server size implementations for Zigbee FOTA

2) Further undertstanding of the following limitations documented on the Nordic Zigbee FOTA page.  Does this mean I can't implement Zigbee FOTA for the UBlox NORA B126 chip that is based on nRF5340?  How can a bootloader update be done?  If the upgrade on the nRF5340 fails because fallback recovery is unavailable, does that mean I would end up with a bricked device upon failed f/w update?

  • The Zigbee FOTA upgrades are currently only supported on the nRF52840 DK (PCA10056) and nRF5340 DK (PCA10095).

  • The Zigbee FOTA library does not currently support bootloader upgrades.

  • It is impossible to enable CONFIG_BOOT_SWAP_USING_MOVE Kconfig option. As a result, the fallback recovery is not available and any valid upgrade will overwrite the previous image. The call to the boot_write_img_confirmed() will have no effect.

3)  Heck, I'd even appreciate a synopsis of how the whole FOTA process occurs at a more granualr level.

Background:

i inherited a project comprised of the Nordic nrf5340, Zigbee communications, and the Digi IX15 Gateway used as the Xbee Zigbee coordinator that will also host OTA upgrades.  This is all new for me.

I have read through the Zigbee FOTA documentation, and took a look at the Light Switch example referenced in the Nordic Zigbee FOTA documentation.  I just received a 5340 DevKit that I plan to use for testing and understanding.

The Light Switch example mentions FOTA, but it really doesn't do much to explain the actual FOTA process.  Aside from the fact that my FOTA server is not a Nordic device, I could find very little information on how to implement the FOTA server side.  I understand the stack takes care of some underlining communications, but I am really unclear what needs to be done on both ends.  

I don't want to just copy some code from the Light Switch example.  I want to more thoroughly understand how it works and how to set up both ends.

Thank you,

Tom

Parents
  • Hi, 

    Sorry for the late reply. 

    As we mentioned the Limitations in the doc: 

    Additionally, the following limitations apply on the nRF5340 SoCs:

    • It is required to use external flash to enable the Zigbee FOTA library.

    I haven't found the external flash in UBlox NORA B126 device so this may be the main obstacle. Also, we don't have Zigbee OTA server sample in NCS. The OTA client side is implemented for example in the Light Switch sample.

    What exactly are you trying to achieve? Is it running a Zigbee application with OTA client on UBlox NORA B126?

    Regards,
    Amanda H.

Reply
  • Hi, 

    Sorry for the late reply. 

    As we mentioned the Limitations in the doc: 

    Additionally, the following limitations apply on the nRF5340 SoCs:

    • It is required to use external flash to enable the Zigbee FOTA library.

    I haven't found the external flash in UBlox NORA B126 device so this may be the main obstacle. Also, we don't have Zigbee OTA server sample in NCS. The OTA client side is implemented for example in the Light Switch sample.

    What exactly are you trying to achieve? Is it running a Zigbee application with OTA client on UBlox NORA B126?

    Regards,
    Amanda H.

Children
No Data
Related