• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 142 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

CC2674P10: Reporting Issues with Large Message Size and Fragmentation with Z-Stack

CC2674P10: Reporting Issues with Large Message Size and Fragmentation with Z-Stack

Abderrahman Sabiri
Prodigy 40 points
Part Number: CC2674P10
Other Parts Discussed in Thread: Z-STACK

Tool/software:

Hi  Ryan,

Just out of curiosity, I was wondering if you have any updates on why this feature is implemented this way in the Z-Stack?

Thanks in advance!

Best regards,

  • 0
    TI__Guru**** 209487 points

    Hi Abderrahman,

    I apologize that they previous topic was not further addressed, as the R&D Team had not returned my inquiry and you had formulated a valid workaround.  I will once more ping the R&D Team for more information.

    Regards,
    Ryan

  • 0
    TI__Guru**** 209487 points

    The Zigbee R&D Team believes that your workaround should be sufficient for the use case as described. Since you only address bdb_repReport, you may encounter issues if trying to send other fragmented packets in the same fashion elsewhere. However the same workaround can be applied in those cases, where you look up the binding entry and use the address(es) from there. This is a gap in Z-stack and is likely a nontrivial amount of work, so I don't have any forecast as to when this will be resolved in the F2 SDK.

    Regards,
    Ryan