• State Verified Answer
  • Replies 2 replies
  • Subscribers 73 subscribers
  • Views 770 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 255536
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

ZigBee OTA 3rd Party Device

WestCoastDaz

I have a binary file for a 3rd party device that the manufacturer has asked me to test on their devices.  I have looked through the ZigBee OTA example documentation but it's not clear to me how I should use the OTA server example get the firmware to the 3rd party device. 

Note the 3rd party device doesn't run a Nordic processor.

Thanks,

Darren 

Parents
  • +1

    Hi Darren,

    I don't know how straight forward the process of updating third party devices with this example will be... First step is to read documentation on how this third party device manages device updates? Firmware is usually signed to prevent updating device with untrusted firmware, and the signature is verified before upgrading and the device will not upgrade if the signature doesn't match... my first question would be if this binary file is designed for this third party device (e.g is it officially released by the manufacturer of the device?)? 

    In theory, if the firmware is official it shouldn't matter what OTA server is used... Unless the manufacturer has designed the device to accept firmware from some specific devices, which is also possible...

    If all of the above is OK and the firmware is ready to be given to the OTA server the only step for you would be to create the package for the BLE DFU to the OTA server board or just put the firmware at the proper address in the OTA server using nrfutil (easiest solution, as it skip image generation): https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nrfutil%2FUG%2Fnrfutil%2Fnrfutil_dfu_zigbee.html

    Best regards,

    Marjeris

Reply
  • +1

    Hi Darren,

    I don't know how straight forward the process of updating third party devices with this example will be... First step is to read documentation on how this third party device manages device updates? Firmware is usually signed to prevent updating device with untrusted firmware, and the signature is verified before upgrading and the device will not upgrade if the signature doesn't match... my first question would be if this binary file is designed for this third party device (e.g is it officially released by the manufacturer of the device?)? 

    In theory, if the firmware is official it shouldn't matter what OTA server is used... Unless the manufacturer has designed the device to accept firmware from some specific devices, which is also possible...

    If all of the above is OK and the firmware is ready to be given to the OTA server the only step for you would be to create the package for the BLE DFU to the OTA server board or just put the firmware at the proper address in the OTA server using nrfutil (easiest solution, as it skip image generation): https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nrfutil%2FUG%2Fnrfutil%2Fnrfutil_dfu_zigbee.html

    Best regards,

    Marjeris

Children
Related
Terms of service