• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 499 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.

WEBENCH® Tools/CC2652R: There may be an issue about OTA server in SDK 3.40（zstack 3.6.0）

Aries Lord
Genius 5390 points
Part Number: CC2652R
Other Parts Discussed in Thread: Z-STACK

Tool/software: WEBENCH® Design Tools

In both zcl_ota.c and  ota_srv_app.c, the ZCL-sequence-number in ZCL-Response-command (OTA cluster) that sent by OTA-Sever is not same with ZCL-sequence-number in ZCL-Request-command. Some other Zigbee 3.0 Devices will match correct ZCL-sequence-number when receiving all ZCL-Response-command, TI's software-team should make their system to be compatible with some other Zigbee 3.0 Devices.

  • 0
    TI__Mastermind 25800 points

    Hi Aries,

    Aries Lord said:
    the ZCL-sequence-number in ZCL-Response-command (OTA cluster) that sent by OTA-Sever is not same with ZCL-sequence-number in ZCL-Request-command

    Do you have a sniffer log you could provide?

    Aries Lord said:
    Some other Zigbee 3.0 Devices will match correct ZCL-sequence-number when receiving all ZCL-Response-command

    Which other devices are you referring to?

    Best Regards,

    Marlyn

  • 0 in reply to Marlyn Rosales Castaneda20
    Genius 5390 points

    1，I have no sniffer of OTA, but in code of OTA-sever, the sequence of ZCL-OTA-Response-Command is generated by zclOTA_SeqNo, which will make the sequence of ZCL-OTA-Response-Command not same with ZCL-OTA-Request-Command.

    2, Such as Silicon-Labs or NXP-Zigbee.

  • 0 in reply to Aries Lord
    TI__Guru**** 219597 points

    To clarify, you believe that the zclIncoming_t -> zclFrameHdr_t -> transSeqNum from zclOTA_ServerHdlIncoming messages should be copied and used as the seqNum of corresponding zcl_SendCommand of zclOTA response messages?  Have you experienced this problem in previous SDKs or is the issue only relevant for v3.40?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Genius 5390 points

    Yes, as I known, in TI's z-stack OTA client will not match seqNum of zclOTA response messages. But I can't make sure if it is Zigbee Alliance 's rule which OTA-client does not need to match seqNum of response messages.

  • 0 in reply to Aries Lord
    TI__Guru**** 219597 points

    Hi Aries,

    This is what I could find regarding ZCL sequence numbers from section 11.13.7.4 of the ZCL v7 Spec:

    "Each Image Block Response command sent as a result of Image Page Request command SHALL have increasing ZCL sequence number. Note that the sequence number MAY not be sequential (for example, if the server is also upgrading another client simultaneously); additionally ZCL sequence numbers are only 8-bit and MAY wrap."

    It is not implied that the server's sequence number should relate to that from the client.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Genius 5390 points

    "Sever's sequence number MAY not be sequential". When server's sequence numbers are relating to that from many clients, sequence numbers that are sent out from server will not be sequential certainly. I have checked Silabs's code, its OTA-Sever will send "QUERY_NEXT_IMAGE_RSP" and "COMMAND_UPGRADE_END_RSP" command whose sequence numbers are relating to that from client.

  • 0 in reply to Aries Lord
    TI__Guru**** 219597 points

    I've forwarded  your concerns to our Software Development Team so that they can further evaluate the modification of our OTA Server example.

    Regards,
    Ryan