• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 55 subscribers
  • Views 472 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.

CC2538: Router leaves network unprovoked

Panagiotis Pyrgas
Intellectual 320 points

Part Number: CC2538
Other Parts Discussed in Thread: CC2652R, Z-STACK,

Hello,

I have made a router and a coordinator from the generic app. But when the router joins the network it stays for a few seconds and then it leaves.

I have tried with another router (a heiman sensor) and I didn't encounter this.

I have also tried with another coordinator (cc2652r with generic app) and it also worked.

I have attached a sniffer of the original setup (the router is 0xcdbb)

Sniffer link

  • +1
    TI__Guru**** 220787 points

    Hello Panagiotis,

    The ZC is requesting that this ZR leave most likely because the router does not request a TC Link Key update (requestNewTrustCenterLinkKey = FALSE) which the coordinator requires (BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE = TRUE), therefore the device join is timed out after BDB_DEFAULT_TC_NODE_JOIN_TIMEOUT of 0x0F or 15 seconds.  Z-Stack from the SimpleLink SDK already has BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE set to FALSE and you can do the same for the Z-Stack 3.0.X CC2538 ZC if you would like to observe the same performance.  The heiman sensor most likely requests the TC Link Key update and is thus allowed to stay in the network.  You could also set requestNewTrustCenterLinkKey to TRUE on the ZR if you would like to require TC Link Key updates which is a feature of the Zigbee 3.0 Specification.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Intellectual 320 points

    Setting BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE to FALSE in ZC fixed it.

    Thank you for your help!!!