Hello s d2,
It appears the ZC is a third-party solution, is it using the Zigbee 3.0 Specification? It is odd that this coordinator creates an all-0xAA PAN ID and transports a NWK key of 0x00. The Ubiqua log displays a lack of the TC link key update…
Hi Toby,
[Toby]That section also documents the steps of the process. The ZED should request a key after receiving the ZDO Node Descriptor response, but I don't see this on the logs.
[Lei] Yes, you are right. We did not send a key after ZDO Descriptor…
Hi Suhrith,
TC Link Key updates are featured in Zigbee 3.0 and require NV memory table storage for each entry which is why le_top recommended that you increase the value of ZDSECMGR_TC_DEVICE_MAX (equal to the total number of Zigbee 3.0 nodes allowed…
Hi,
This will be fixed in the next SDK (4.10).
The fix is the following:
In bdb_StartCommissioning, replace the contents between the "#ifdef ZG_BUILD_JOINING_TYPE" and "#endif //ZG_BUILD_JOINING_TYPE" with:
#ifdef ZG_BUILD_JOINING_TYPE
//Only…
Joining devices may skip the TCLK exchange procedure by setting requestNewTrustCenterLinkKey to FALSE (ZDSecMGr.c) to allow Z3.0 devices to deploy a custom large network without requiring big tables of TCLK in Coordinator devices. However, this should…
Hi YiKai, Hold li,
The policy on ZC to not request the TCLK is BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE (bdb_interface.h), you should set this to FALSE in order to avoid kick-out of the network a device that do not perform the TCLK exchange (legacy device…
I will paste my changes in z-stack,this may be help more engineer.
bdb.c
extern bool acceptNewUnsolicitedApplicationLinkKey;
/*********************************************************************
* @fn bdb_ProcessNodeDescRsp
*
* …
Part Number: CC2652R Other Parts Discussed in Thread: SYSCONFIG
simplelink_cc13x2_26x2_sdk_3_40_00_02
1. Removing board constraints in SysConfig with "Custom Board" button causes unexpected build or runtime behavior.
Refer to this E2E FAQ: https…
