• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 55 subscribers
  • Views 503 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.

CC2652P7: The device cannot join the zigbee standard gateway

liu minghui
Prodigy 30 points

Part Number: CC2652P7
Other Parts Discussed in Thread: CC2652P

We now have a door lock device using cc2652p and the protocol stack is simplelink_cc13x2_26x2_sdk_5_10_00_48. The door lock can be added to our private gateway normally, and the private gateway does not encrypt when sending the transport key. However, when the ZigBee 3.0 standard gateway is added, it cannot access the network normally. By capturing the packet, it is found that the gateway has sent the transport key and used the default TC link key for encryption, but the device state is DEV_END_DEVICE_UNAUT. May I ask what causes the device side to fail to decrypt? Is there any way to locate the cause

  • 0
    TI__Guru**** 222787 points

    Hi liu,

    Can you provide the sniffer log you captured?  Can you compare the join process against your working private gateway solution?  Have you made sure to reset your CC2652P to factory settings, or erased all memory and re-programmed, before attempting to join the new gateway?  You can change the requestNewTrustCenterLinkKey (in zd_sec_mgr.c) to FALSE if the a new TC link key request should not be sent by the door lock device.

    Regards,
    Ryan