Some issue of Z-stack #568
zigbee-luo
started this conversation in
General
Replies: 2 comments 2 replies
|
Would you mind making a PR to extend https://github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_3.x.0/firmware.patch ? |
1 reply
|
I have seen your firmware patch file, but I don't know how to make patch file of my fixed code. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
When sending a large number of AF frames with APS retry enabled, it will consume a lot of HEAP space and NWK [Buffer], causing some AF frames that are being retransmitted to be unable to allocate Buffer, resulting in the loss of the AFDATAVNet message for that AF frame. You can modify this issue according to my file.
The coordinator of Texas Instruments hopes to start Trust Center verification on the nodes connected to the network within 600ms after receiving the Associate Indication. However, the timer mode in ZDOJoinIndividualCB cannot guarantee an accurate 600ms delay at certain times when running on CC2652 with RTOS. Of course, this problem will not occur on CC2530 without RTOS.
CC2652, due to its use of RTOS mechanism, if it is necessary to read the next record from the queue, it must first obtain the pointer of the next record from the pointer of the previous record, and then release the pointer of the previous record. However, Texas Instruments' protocol stack often releases the memory pointed to by the pointer of the previous record first, and then retrieves the next record from the pointer of the previous record. This will cause a memory crash on CC2652.
All reactions