• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 265 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.

CC2652P: End device capacity bug

Giacomo Bosco
Prodigy 10 points
Part Number: CC2652P
Other Parts Discussed in Thread: Z-STACK

Hello,

Referring to this thread https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/867620/cc2530-router-end-device-capacity-false/3209821#3209821 , I want to know if the bug has been solved in 3.x.0 version of Z-STACK, running on coordinator CC26562.

If the bug has not been fixed, is there a method to remove unused devices from the coordinator's memory (via, for example, an api)?

Thanks.

  • 0
    TI__Guru**** 211907 points

    Hello Giacomo,

    Retaining previously-joined devices in the trust center's link key table is not a bug, as this feature allows non-responsive or non-existent devices to easily rejoin the network.  If you need to clear the ZCD_NV_EX_TCLK_TABLE then you can do this with the osal_nv_delete_ex API.  Note that child end devices are automatically removed from the parent's association tables by child-aging behavior, but can also be accomplished through using AssocRemove.

    Regards,
    Ryan