Hello,
I am working with cc2531, zstack 2.5.1a, using the SE sample app Range Extender configuration. I have modified the fw8Config.cfg to specify
/* Enable ZigBee-Pro */
-DZIGBEEPRO
-DSE_PROFILE
/* Set to 0 for no security, otherwise non-0 */
-DSECURE=1
-DZG_SECURE_DYNAMIC=0
Also I have enabled MT_SYS_KEY_MANAGEMENT so I can access the TCLK table.
The TCLK table of the range extender device has TCLK table entry:
<RX>11:29:58.77 COM48 SYS_OSAL_NV_READ_SRSP (0x6108)
Status: SUCCESS (0x0)
Len: 0x20
Value: ...........!,7BMX.......X....... (0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x0B, 0x16, 0x21, 0x2C, 0x37, 0x42, 0x4D, 0x58, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x58, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00)
The TCLK table of the coordinator has the following entry:
00124b0000000002 000b16212c37424d5800000000000000 00000000 00000000
I have confirmed with a packet sniffer that the coordinator sends ab APS Transport Key encrypted with the proper key. The transport key packet receives the MAC level acknowledgement.
The problem is that my range extender device does not receive the ZDSecMgrTransportKeyInd, also it never hit breakpoints in APSME_TCLinkKeyLoad,
I read the section on secure joining in "Z-Stack Smart Energy Developer’s Guide" The information is quite out of date. It mentions several NV ID's that do not exist.
Is there any document that can show how to make the SE sample applications work with a Zigbee SE 1.x coordinator?
Do you have any recommendations on how to debug the missing transport key indication?