CC2652R: Zigbee CC2652 Coordinator, end devices connectivity

Karthick D

Part Number: CC2652R
Other Parts Discussed in Thread: Z-STACK, SIMPLELINK-CC13X2-26X2-SDK, SYSCONFIG

Dear TI,

I have created a coordinator based on CC2652 and I used the firmware from the C:\Ti\Zigbee_3_0_Linux_Gateway_1_0_1\Firmware\znp. Initially it was working well later when I tried to add further more devices, the coordinator won't allow to add, the devices count is 12, we are facing a strange problem that the device pairs and removes automatically and this keeps on continuing. What could be the problem, I suspect the end device and tried pairing it with another hub it is pairing well, Please help us to resolve this problem.

over 2 years ago

0 YiKai Chen over 2 years ago

Guru 735465 points

Can you provide sniffer log to allow use to check what exactly happens over the air?

0 Ryan Brown1 over 2 years ago

TI__Guru**** 205097 points

Hi Karthick,

If I remember correctly then the ZNP firmware included with the ZIGBEE-LINUX-SENSOR-TO-CLOUD demo software uses the SIMPLELINK-CC13X2-26X2-SDK v3.40 which is quite outdated at this point. I recommend you build a new ZNP image using the latest (v5.20) SDK instead. This will fix any Z-Stack bugs which have been resolved in the past year and allow for you to further configure your Zigbee network settings, for example NWK_MAX_DEVICE_LIST (set through SysConfig -> Z-Stack -> Network -> Network Maximum Device List). There are other variables to consider when increasing network size, please refer to SWRA650 and the Z-Stack User's Guide for more information.

Regards,
Ryan

0 Karthick D over 2 years ago in reply to YiKai Chen

Intellectual 415 points

Ch trace1.psdHere is the trace file for the problem.

0 Ryan Brown1 over 2 years ago in reply to Karthick D

TI__Guru**** 205097 points

The sniffer log contains several Beacon Requests but nothing else. This is not very useful for further debugging the issue.

Regards,
Ryan

0 Karthick D over 2 years ago in reply to Ryan Brown1

Intellectual 415 points

I am facing some problem while taking the trace, btw I need to know how to check the dead nodes in the ZNP, I mean I have added several devices and some devices were not properly removed due to the hardware failure in the end devices, in this situation I feel the device entry is full, in this situation how can I check the device table entries or how to clear the unnecessary entries?

Also is that possible to take backup from one ZNP and restore it to another ZNP?

0 YiKai Chen over 2 years ago in reply to Karthick D

Guru 735465 points

1. Zigbee 3.0 coordinator and router would age out dead end device automatically after child-aging timeout. You don’t need to take care of it by yourself.

2. You can refer to https://www.ti.com/lit/an/swra671/swra671.pdf to backup and restore ZNP/coordinator

0 Karthick D over 2 years ago in reply to YiKai Chen

Intellectual 415 points

Ok one more question, Is the paired Zigbee end devices work if I flash a new firmware?

0 Karthick D over 2 years ago in reply to Ryan Brown1

Intellectual 415 points

As suggested I am trying to update the firmware with latest 5.2 SDK, will the paired devices work without re-adding?

0 Ryan Brown1 over 2 years ago in reply to Karthick D

TI__Guru**** 205097 points

The ZC/ZNP cloning process specifically copies the NV flash memory from the old device to the new one so that network information is retained and can continue without difficulty, thus the devices which have already joined the network do not have to initiate a fresh join procedure as they will be recognized by the cloned ZC/ZNP device. If you are programming new firmware but desire to retain previous device information then make sure the NV memory contents are not overwritten during the firmware update.

Regards,
Ryan

0 YiKai Chen over 2 years ago in reply to Karthick D

Guru 735465 points

If you flash new firmware, the previous network information would be erased and you have to factory reset your device to join the network from scratch.

0 Karthick D over 2 years ago in reply to Ryan Brown1

Intellectual 415 points

What if I use the same PAN ID, Channel ID in the new firmware ?

0 Karthick D over 2 years ago in reply to Ryan Brown1

Intellectual 415 points

The Cloning tool failed to execute

0 Ryan Brown1 over 2 years ago in reply to Karthick D

TI__Guru**** 205097 points

Once again, if you retain NV memory then the previous network information will be restored. Otherwise the devices will have to rejoin even with the same Pan ID and channel since the ZC/ZNP no longer has the network key, TC link keys, associated/routing tables, etc. Please provide more specific information regarding cloning tool issues.

Regards,
Ryan

0 Karthick D over 2 years ago in reply to Ryan Brown1

Intellectual 415 points

I somehow managed to work with the Cloning tool, but it is not reading with from the tables screenshot attached

0 Ryan Brown1 over 2 years ago in reply to Karthick D

TI__Guru**** 205097 points

It is explained in Section 7 of SWRA671 that MT_SYS_KEY_MANAGEMENT must be pre-defined in order to grant access to security key data.

Regards,
Ryan

Zigbee & Thread

Zigbee & Thread forum

CC2652R: Zigbee CC2652 Coordinator, end devices connectivity