CC2652P: ZED Switch sample - Failed to join Zigbee network (Interview failed because can not get node descriptor)

Hello Haim,

Thanks for the sniffer log.  I am not seeing packets typically sent out by a ZED after joining, such as a Device Announce and End Device Timeout Request.  Node Descriptor Request unicasts should definitely expect a response.  Can you confirm that you are using the default LAUNCHXL-CC1352P-2 ZED switch example (or P-4 depending on your output TX power settings)?  What version of https://www.ti.com/tool/download/SIMPLELINK-LOWPOWER-F2-SDK have you installed, and is all device memory erased before reprogramming?  I do not see the TCLK update exchange, have you set requestNewTrustCenterLinkKey to FALSE for your ZED in this case?

Regards,
Ryan

Thanks Ryan

Yes, I've created CCS project based on this ZED switch example

I'm  using simplelink_cc13xx_cc26xx_sdk_8_31_00_11

I've updated zcl_samplesw.c with my custom board GPIO (buttons and leds) and updated zclSampleSw_processKey() with my buttons instead of the default ones. So I start the Commissioning by pressing a button.

I've set requestNewTrustCenterLinkKey to FALSE and I looked for the usage of requestNewTrustCenterLinkKey

I've found that it is in use in bdb_StartCommissioning()  and in bdb_ProcessNodeDescRsp()

I debugged and see that it never reached these code lines

On initialization there is a call to  bdb_StartCommissioning(mode=0) , it checks  bdbNodeIsOnANetwork (NV) and it is FALSE

On the button click there is a call to  bdb_StartCommissioning(mode=DEFAULT_COMISSIONING_MODE) , and since  bdb_initialization is TRUE is skip most of the function code

I'm attaching my SysCfg header files - maybe it will help

I can debug furthermore or add logs from zigbee2mqtt if it will help

Thanks

Haim

Syscfg.zip

It would be optimal if you could prove that that a default out-of-box CC1352P-2 LaunchPad and code example are able to join the Coordinator without any issues.

If you aren't using the Common UI then you should be defining CUI_DISABLE and removing BOARD_DISPLAY_USE_UART from Properties -> CCS Build -> Arm Compiler -> Predefined Symbols.

You can debug ZDO_ProcessNodeDescReq on your ZED to determine whether it's being processed and what prevents Node_Desc_rsp from being sent out.

Regards,
Ryan

I'm using the example of LP_CC2652PSIP\zstack\zed_sw but I think it should be identical to CC1352P_2_LAUNCHXL\zstack\zed_sw

I'm working with E72-2G4M20S1E (C2652P) on my custom board - I'm not using the LP-CC2652PSIP board

About the UI - I only need it for starting the commissioning (triggered by a button), any other suggestion?

I've tried to debug ZDO_ProcessNodeDescReq  - looks like I don't get it (I've checked at ZDP_IncomingData() - is it the right place?)

Thanks

Haim

Thanks Ryan, I've created a new project based on CC1352P_2_LAUNCHXL and now it is working properly!