CC2652R: CC2652 rejoin issue

userjiabo

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

Hi TI Team,

The End Deivce(CC2652) have joined successfully the Coordinator(CC2538) and send the packets to Coordinator(CC2538).

And the Coordinator always powered,I power off the End Deivce(CC2652) and power on it, the End Deivce(CC2652) rejoin unsuccessfully.

It seem that the the end device(CC2652) keep re-join the network.

But in contrast，the End Deivce(CC2652) always powered,I power off the Coordinator(CC2538) and power on it, the End Deivce(CC2652) rejoin successfully.

This problem have any Suggestion?Using the zigbee3.0.2(CC2538,no development) also have this problem(just call the open the network API).

over 4 years ago

0 YiKai Chen over 4 years ago

Guru 735475 points

Which Z-Stack version and example do you test and see this trouble? Do you revise any code in the example? Can you also provide sniffer log?

0 userjiabo over 4 years ago in reply to YiKai Chen

Genius 4440 points

Thank you YiKai Chen reply!

The End-Device CC2652 use SDK(simplelink_cc13x2_26x2_sdk_3_10_00_53),The Coordinator CC2538 use SDK(zstack 3.0.2)

But I use CC2530(zstack 3.0.2) instead of CC2652 as an End-Device,it had no this issue. it can rejoin successfully Coordinator(CC2538).

The Insert File(zigbee test data 2652 rejoin.psd) is the sniffer log(Use the Packet Sniffer Tool open it).

zigbee test data 2652 rejoin.psd

0 Toby P over 4 years ago in reply to userjiabo

TI__Mastermind 31380 points

Hi,

The NWK packets in the sniffer log are encrypted. Please provide the NWK key.

I joined an out of box CC2652 ZED (3.10 SDK) to an out of box CC2538 ZC. After resetting the ZED, it rejoins successfully.

Can you share what modifications you've introduced into either example?

Regards,
Toby

0 userjiabo over 4 years ago in reply to Toby P

Genius 4440 points

OK, This Insert Files is my end-device(CC2652) join the Coordinator process,

Firstly,The end-device Beacon Request,Secondly,The Coordinator will open the zigbee network.zigbee nwk key.psd

0 YiKai Chen over 4 years ago in reply to userjiabo

Guru 735475 points

Can you specify short address of CC2652R end device in your sniffer log zigbee test data 2652 rejoin.psd?

0 userjiabo over 4 years ago in reply to YiKai Chen

Genius 4440 points

Thank you Toby Pan reply! Is the short address of CC2652R end device randomly assigned? I have communicate with friend, The wireshark packet capture seem that the Coordinator had no Rejoin Response.Please check it.Thanks!

0 Walter Macamos over 4 years ago in reply to YiKai Chen

Genius 5345 points

Hi Toby & YK,

We are working on same issue I mentioned in this thread.

Regards,

Walter

0 userjiabo over 4 years ago in reply to YiKai Chen

Genius 4440 points

I will use CC2530 as the end-device capture the packets log and report to it.

0 YiKai Chen over 4 years ago in reply to userjiabo

Guru 735475 points

It's strange that your device keeps sending data request but it also sends rejoin request. Can you elaborate what modifications you did in your test?

0 Walter Macamos over 4 years ago in reply to YiKai Chen

Genius 5345 points

Hi YK,

1 For device side ZED, we did not modify rejoining zclSampleSw_ProcessCommissioningStatus from the original. So, it will keep sending rejoin packet one lost parent.

2. It will send a report data every 20 seconds if connection up to inform online status to hub.

Regards,

Walter

0 YiKai Chen over 4 years ago in reply to Walter Macamos

Guru 735475 points

I don't see this issue on SDK 3.30. Maybe you can try SDK 3.30 example.

0 Walter Macamos over 4 years ago in reply to YiKai Chen

Genius 5345 points

What are known issue in SDK 3.30? And, what coordinator you are using?

0 YiKai Chen over 4 years ago in reply to Walter Macamos

Guru 735475 points

1. [FAQ] CC2652R: CC13x2 CC26x2 SDK Zigbee Known Issues and Fixes

2. I use zc_light in SDK 3.30.

0 userjiabo over 4 years ago in reply to YiKai Chen

Genius 4440 points

Thanks YiKai Chen reply,I had not modify on CC2538(as a Coordinator),

And using CC2538(original zstack3.0.2),using the GenericApp example:just on the function(void zclGenericApp_Init(byte task_id)) call the API(bdb_StartCommissioning(BDB_COMMISSIONING_MODE_NWK_STEERING|BDB_COMMISSIONING_MODE_NWK_FORMATION | BDB_COMMISSIONING_MODE_FINDING_BINDING | BDB_COMMISSIONING_MODE_INITIATOR_TL);), the CC2652(SDK3.10) also have this issue.

I had browsed Walter and you reply,The CC2652(SDK3.10) had this issue?

Thanks!

0 YiKai Chen over 4 years ago in reply to userjiabo

Guru 735475 points

I don't test SDK 3.10 to check this issue but I don't see such issue on SDK 3.30. That's why I suggest you to use SDK 3.30.

0 userjiabo over 4 years ago in reply to YiKai Chen

Genius 4440 points

Hi YiKai Chen

I found the CC2538 zstack3.0.2 the source code describe as follows:

// trustcenter allows rejoins using well known or default keys
uint8 zgAllowRejoins = FALSE; // FALSE by default

//if zgAllowRejoins is set to FALSE, the rejoining device will receive a rejoin rsp success and also a leave command.
//The leave command will have set the rejoin parameter = 'zgAllowRejoinsOptions' value.
uint8 zgAllowRejoinsOptions = FALSE; //FALSE by default

I had let two parameters True? eg: zgAllowRejoins = True; zgAllowRejoinsOptions =True;

Thanks!

0 YiKai Chen over 4 years ago in reply to userjiabo

Guru 735475 points

Basically, rejoin should be disable according to Zigbee 3.0 spec because it's insecure.

0 userjiabo over 4 years ago in reply to YiKai Chen

Genius 4440 points

OK,Thanks,YK Chen .This issue had about the CC2538 zstack3.0.2 problem?just update CC2652 sdk3.10 to sdk3.3?

0 YiKai Chen over 4 years ago in reply to userjiabo

Guru 735475 points

TI doesn't provide any Z-Stack update after 3.0.2 for CC253x.

0 Aries Lord over 4 years ago in reply to YiKai Chen

Genius 5310 points

I don't think so. In Silabs's trust center, unsecured-rejoin node will be accepted if it has verified link key.

0 YiKai Chen over 4 years ago in reply to Aries Lord

Guru 735475 points

It's your choice but it will be insecure.

0 userjiabo over 4 years ago in reply to YiKai Chen

Genius 4440 points

Thanks YiKai Chen, I mean is that I Coordinator CC2538 nothing to change, just CC2652 SDK 3.10 instead of SDK 3.3.

0 Walter Macamos over 4 years ago in reply to YiKai Chen

Genius 5345 points

Trying to use sdk3.30.

Questions:

1. my osal_nv_write only 3 paramters:

uint8_t osal_nv_write( uint16_t id, uint16_t len, void *buf )

{
// Legacy items use ZCD_NV_EX_LEGACY as the ID and the id as the sub-id.
return ( osal_nv_write_ex( ZCD_NV_EX_LEGACY, id, len, buf ) );
}

Item #1 change is 4 parameters. Do we need to change?

4. How to add:

for( n = 0; n < gNWK_MAX_DEVICE_LIST; n++ )

{

uint16_t shortAddr;

osal_nv_read_ex( ZCD_NV_EX_DEVICE_LIST, n, 0, sizeof(shortAddr), &shortAddr );

if( (AssociatedDevList[n].shortAddr == 0xFFFF) && ( shortAddr != 0xFFFF ) )

{

//not delete NVID, fixed by luoyiming 2019-10-16

uint8_t tmpBuf[16];

memset( tmpBuf, 0xFF, sizeof(tmpBuf) );

osal_nv_write_ex( ZCD_NV_EX_DEVICE_LIST, n, sizeof(tmpBuf), tmpBuf );

}

TO >>>>

*/
void ZDApp_SaveNetworkStateEvt( void )
{
#if defined ( NV_RESTORE )
#if defined ( NV_TURN_OFF_RADIO )
// Turn off the radio's receiver during an NV update
uint8_t RxOnIdle;
uint8_t x = false;
ZMacGetReq( ZMacRxOnIdle, &RxOnIdle );
ZMacSetReq( ZMacRxOnIdle, &x );
#endif

// Update the Network State in NV
NLME_UpdateNV( NWK_NV_NIB_ENABLE |
NWK_NV_DEVICELIST_ENABLE |
NWK_NV_BINDING_ENABLE |
NWK_NV_ADDRMGR_ENABLE );

// Reset the NV startup option to resume from NV by
// clearing the "New" join option.
zgWriteStartupOptions( FALSE, ZCD_STARTOPT_DEFAULT_NETWORK_STATE );

#if defined ( NV_TURN_OFF_RADIO )
ZMacSetReq( ZMacRxOnIdle, &RxOnIdle );
#endif
#endif // NV_RESTORE
}

I cannot find #7 in my code

7. Incorrect parsing of ZDO_EXT_SEC_APS_REMOVE_REQ MT command

Correct the order of parsing in function MT_ZdoExtSecApsRemoveReq:

if ( ZG_SECURE_ENABLED && ZG_BUILD_COORDINATOR_TYPE && ZG_DEVICE_COORDINATOR_TYPE ) 
{ 
  nwkAddr = osal_build_uint16( pBuf ); 
  pBuf += 10; 
  
  parentAddr = osal_build_uint16( pBuf ); 
  pBuf -= 8; 
  
  status = ZDSecMgrAPSRemove( nwkAddr, pBuf, parentAddr ); 
}

0 Aries Lord over 4 years ago in reply to YiKai Chen

Genius 5310 points

My meaning is that if a unsecured-rejoin node has got APS Link Key from trust-center when first joining( Associate-Joining), trust center can accept it and encrypt its NWK by APS-Link-Key.

0 YiKai Chen over 4 years ago in reply to Aries Lord

Guru 735475 points

Aries Lord I see Ryan already reply you in your another post ( https://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread/f/158/t/867142 ) about this rejoin topic.

0 Aries Lord over 4 years ago in reply to YiKai Chen

Genius 5310 points

APS link key is an important part of zigbee 3.0. But it seems that z-stack 3.30 has never use APS Link Key.

0 Ryan Brown1 over 4 years ago in reply to Aries Lord

TI__Guru**** 207137 points

Network keys and TC link keys updates are accomplished automatically but APS link keys are application behavior that must be implemented by the user. They are supported in Z-Stack and the APIs have been discussed previously: https://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread/f/158/t/849750

Regards,
Ryan

0 Toby P over 4 years ago in reply to userjiabo

TI__Mastermind 31380 points

user5948209,

Is the log zigbee nwk key.psd taken before the log zigbee test data 2652 rejoin.psd ?
If yes, then the reason that the ZC is not responding with a "Rejoin Response" is:

At the end of zigbee_nwk_key.psd, the device 0x086F uses NWK frame counter of 91881 (pkt 81).
At the beginning of zigbee_test_data_2652_rejoin.psd, the device 0x086F is using NWK frame counter of 88393 (pkt 13).

If such is the case, then according to the Zigbee spec, the ZC should drop this frame (no further processing); the receiving device would only process the frame further if the NWK frame counter of a packet is greater than the NWK frame counter last received from that transmitting device. The transmitting device 0x086F is not aware that the ZC is dropping the rejoin requests, so it continues to poll for the response at the default rejoin poll rate of 440 ms (REJOIN_POLL_RATE).

Usually the NWK frame counter is saved in non-volatile storage (NV area in flash) so that the device can use this on a reset. That's what the out-of-box SDK examples do.
I'm not sure what modifications you've made to the example that could affect this, so I highly recommend starting from a clean example project of the SDK.

Please let us know how it goes, and if you require further support through that process.

0 Walter Macamos over 4 years ago in reply to Toby P

Genius 5345 points

Hi Toby,

Do you think the ZED is failing or ZC also?

Regards,

Walter

0 Toby P over 4 years ago in reply to Walter Macamos

TI__Mastermind 31380 points

Based on the details described, it seems to be an issue on ZED side.

0 userjiabo over 4 years ago in reply to Toby P

Genius 4440 points

Hi Toby Pan

OK! I only use a CC2538(zstack3.0.2 a clean example project as Coordinator), and CC2652(SDK3.10 project code) also had this issue,

I just let the CC2538 open the network always.

Secondly! I modify two parameters True(location in ZGlobals.c),it also had this issue.

// trustcenter allows rejoins using well known or default keys
uint8 zgAllowRejoins = FALSE; // FALSE by default

0 Toby P over 4 years ago in reply to userjiabo

TI__Mastermind 31380 points

Thanks for providing an update.

Since the issue is on the ZED (CC2652 in this case), please use a clean example project for CC2652 as well.

You can leave those two FALSE by default.

0 userjiabo over 4 years ago in reply to Toby P

Genius 4440 points

Thans Toby Pan reply，Yes，the second step I will bulid a clean example CC2652 to track this issue!

0 userjiabo over 4 years ago in reply to Toby P

Genius 4440 points

Hi YiKai Chen&Toby Pan, I used wireshark to capture the packet this afternoon.The Inser File is the packet of wireshark about ze(CC2652), had a diffrence about Message Integrity Code

I will build a CC2652 clean example to track this issue tomorrow.

0 userjiabo over 4 years ago in reply to Toby P

Genius 4440 points

One picture is CC2652 successfully rejoin the CC2538 have a rejoin response ,Other it is unsuccessfully rejoin the CC2538 have no rejoin response.

Thanks!

0 userjiabo over 4 years ago in reply to Toby P

Genius 4440 points

Hi Toby Pan

I have a CC2652 demo board and use CC2652 SDK 3.10 clean example(zed_light_CC26X2R1_LAUNCHXL_tirtos_ccs) had no this issue, it can rejoin the CC2538 successfully,But when I use a clean example(zed_sw_CC26X2R1_LAUNCHXL_tirtos_ccs),I press the board the BIN-1(DIO13),it had no any response and the wireshark had not capture the CC2652(Beacon Requst).

The example had a problem? Thanks!

0 userjiabo over 4 years ago in reply to userjiabo

Genius 4440 points

OK, I had buld a ze-sw or ze-light ok rejoin successfully,the next step，I will found the 2652 project had what and where changed.Thanks!

0 Toby P over 4 years ago in reply to userjiabo

TI__Mastermind 31380 points

Any updates? Can you share the modifications you've made to your CC2652 project?

0 userjiabo over 4 years ago in reply to Toby P

Genius 4440 points

Hi,Toby Pan

if this issue was about the answer of the network key clear after rejoin fail?

0 Toby P over 4 years ago in reply to userjiabo

TI__Mastermind 31380 points

It could be. They're using a different stack and I don't know what other modifications they have made in their code, so please use discretion if you apply their solution.

As you've verified, this issue does not happen in unmodified examples.
If you can share any code changes that you've added to the example applications for your use case, it could help to find what's causing this issue.

0 userjiabo over 4 years ago in reply to Toby P

Genius 4440 points

OK，Thanks，sorry，these days I on holiday and had busy other thing.

I will check more details and report to you. I am brown the source code and will report to it.

Thanks again!

Zigbee & Thread

Zigbee & Thread forum

CC2652R: CC2652 rejoin issue