• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 57 subscribers
  • Views 1305 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

ZigBee OTA specific files

Jeff Stubler
Prodigy 90 points

I am working on a project where we are trying to use ZigBee OTA to transfer configuration information and log files in addition to upgrading firmware. The ZigBee OTA specification indicates image types for client configuration (0xffc1), but we are also hoping to split the configuration with manufacturer-specific image types; however, Query Device Specific File mandates the use of image types 0xffc0–0xfffe. Is there any way to get around this?

Furthermore, Image Notify specifies that a Query Next Image Request is to be sent. How are devices to be notified for device-specific files? The OTA specification does not describe any recommendations on how Query Device Specific File is to event be triggered (it is manufacturer-specific), and it doesn't appear that Image Notify can be used for this.

  • 0
    Intellectual 300 points
    It is my understanding that the Query Specific File Request Command would be sent after an Image Notify Command is received with an image type value between 0xffc0 – 0xfffe, which should be included when the payload type is either 0x02 or 0x03. It can also be sent out without any other triggers but its own search for a specific file. May I ask what version of the specification are you using?
  • 0 in reply to Sloan
    Prodigy 90 points

    We are using ZCL Rev 6.

    The specifications state that "On receipt of a unicast Image Notify command, the device SHALL always send a Query Next Image request back to the upgrade server." It does not seem to allow for Query Device Specific File, but it seems like it should, right (in the manner that you described, after the particular image type notify is send)?

    At the moment, but this could change, we might not need any image type other than 0xffc1, so our question on that aspect might no longer be relevant.

  • 0 in reply to Jeff Stubler
    Intellectual 300 points

    Well the trigger for the Query Device Specific File is manufacturer specific so you should be able to use any procedure you want, but you are correct that the standard specifies that the device SHALL always send a Query Next Image request, then if you want to use the Image Notify as a trigger you will probably need to try to verify it with the ZigBee Alliance, just to be sure there will not be a compatibility problem in the future if they decide to make changes to that command, it might be that they have already considered it but the spec has not been updated.

    Regards,

    Dalila

  • 0 in reply to Sloan
    Prodigy 90 points
    How do I contact the ZigBee Alliance regarding this?