Zigbee: ip802154_lld_exitSleep() FAILED

[SToma]

Hello,

testing Zigbee_OnOff_Client_SED on P-NUCLEO-WB55. Sources are from version 1.18.0, same as installed stm32wb5x_Zigbee_FFD_fw.bin. Almost no changes to source files except modification channelmask to WPAN_CHANNELMASK_2400MHZ.

After a while (random inteval) device send following debug message, and device can't find network anymore:

[M0] [00007009.694][LLD] !! ip802154_lld_exitSleep() FAILED : LLD state before 2 - time before 2714719056 - sleepTimeStatus 1 - wakeUpStatus 149 - default state after 99 (1) - LLD state after 2

Does anybody have a clue? Any suggestion?

Thanks.

More from log file:

 [M0] [00006358.738][PLATFORM] nwk_scan_req : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800, dur=4

 [M0] [00006362.963][PLATFORM] nwk_handle_scan_conf_rejoin : Error, could not find a parent to rejoin.

 [M0] [00006641.946][PLATFORM] nwk_dataconf_watchdog_timer : Error, never received MCPS-DATA.confirm. Returning status = 0xd6

 [M0] [00006643.447][PLATFORM] nwk_edka_timer_cb : EDKA timed out (parent = 0x0000, timeout = 1, thesh = 1), sending PARENT_LINK_FAILURE to NHLE.

 [M0] [00006643.448][PLATFORM] ZbMonitorHandleStatusInd : Parent link fail, performing end-device rejoin attempt

 [M0] [00006643.449][PLATFORM] nwk_scan_req : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800, dur=4

 [M0] [00006643.450][PLATFORM] nwk_dataconf_watchdog_timer : Error, never received MCPS-DATA.confirm. Returning status = 0xd6

 [M0] [00006644.635][PLATFORM] nwk_handle_beacon_ind : BEACON addr16=0x0000, epid=0x273e0d2825a792bd, ch=15, pan=0x2bb0, depth= 0, lqi=108, cost=3, pjoin=0

 [M0] [00006647.826][PLATFORM] ZbZdoDeviceAnnce : Sending Device_Annce for 0xf287

 [M0] [00006647.827][PLATFORM] nwk_handle_rejoin_rsp : Successfully rejoined to 0x0000.

 [M0] [00007009.694][LLD] !! ip802154_lld_exitSleep() FAILED : LLD state before 2 - time before 2714719056 - sleepTimeStatus 1 - wakeUpStatus 149 - default state after 99 (1) - LLD state after 2

 [M0] [00007012.079][PLATFORM] ZbMonitorHandleStatusInd : Parent link fail, performing end-device rejoin attempt

 [M0] [00007012.080][PLATFORM] nwk_scan_req : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800, dur=4

 [M0] [00007012.083][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007012.086][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007012.088][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007012.091][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007012.094][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007012.096][PLATFORM] nwk_handle_scan_conf_rejoin : Error, could not find a parent to rejoin.

 [M0] [00007013.123][PLATFORM] ZbMonitorHandleStatusInd : Parent link fail, performing end-device rejoin attempt

 [M0] [00007013.124][PLATFORM] nwk_scan_req : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800, dur=4

 [M0] [00007013.127][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007013.129][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007013.132][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007013.135][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007013.137][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007013.140][PLATFORM] nwk_handle_scan_conf_rejoin : Error, could not find a parent to rejoin.

 [M0] [00007014.078][PLATFORM] nwk_edka_timer_cb : EDKA timed out (parent = 0x0000, timeout = 1, thesh = 1), sending PARENT_LINK_FAILURE to NHLE.

 [M0] [00007014.079][PLATFORM] ZbMonitorHandleStatusInd : Parent link fail, performing end-device rejoin attempt

 [M0] [00007014.080][PLATFORM] nwk_scan_req : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800, dur=4

 [M0] [00007014.083][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007014.086][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007014.088][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007014.091][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007014.093][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007014.096][PLATFORM] nwk_handle_scan_conf_rejoin : Error, could not find a parent to rejoin.

 [M0] [00007015.122][PLATFORM] ZbMonitorHandleStatusInd : Parent link fail, performing end-device rejoin attempt

 [M0] [00007015.123][PLATFORM] nwk_scan_req : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800, dur=4

 [M0] [00007015.127][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007015.130][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007015.132][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007015.135][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007015.137][PLATFORM] nwk_handle_scan_conf_rejoin : MLME-SCAN.request (wpan0): type=1, page=0, mask=0x07fff800

 [M0] [00007015.140][PLATFORM] nwk_handle_scan_conf_rejoin : Error, could not find a parent to rejoin.

 [M0] [00007016.125][PLATFORM] ZbMonitorHandleStatusInd : Parent link fail, performing end-device rejoin attempt

[SToma]

No response even from forum master. Anybody? @Ouadi probably? Error roots seems are in the Zigbee library, therefore out of my range. What cause this error?

Thanks, Slavomir

[Ouadi]

Hello @SToma,

Sorry for the delay.

From the logs, it seems like the End device cannot exit the sleep mode and then the parent link fail which leads to unsuccessful rejoin. 

As I understood, you have installed the stm32wb5x_Zigbee_FFD_fw.bin binary for the SED which is not recommended and may introduce some issues especially when entering in the low power mode.

For the SED, only wireless coprocessor binary stm32wb5x_Zigbee_RFD_fw.bin can be used as mentioned in the README file.

Could you please give it a try with the right binary and update the status ?

Thanks

Best regards,

Ouadi

[SToma]

Hello Ouadi,

You are right, RTFM. :(

Anyway, after replace FFD stack with RFD same behavior, and it happen again.

S.T.

APP_ZIGBEE_Init

**********************************************************

WIRELESS COPROCESSOR FW:

VERSION ID = 1.18.0

FW Type : RFD Zigbee stack

Application flashed: OnOff_Client_SED

Channel used: 13

Link Key: ZigBeeAlliance09

Link Key value: 5a 69 67 42 65 65 41 6c 6c 69 61 6e 63 65 30 39 

Clusters allocated are:

onOff Client on Endpoint 17

**********************************************************

[Ouadi]

Hi @SToma,

Thanks for the update.

I have done a short test without reproducing the issue. Could you please share the whole logs from the beginning until the issue message appears ?

What is the configuration on the coordinator side ? It seems that after a period of time, the end device does not find the network anymore, it may be located on the coordinator side as well. 

Could you please share both configurations and logs to help understanding your case ? Thanks

best regards,

Ouadi

[SToma]

Hi Ouadi,

see attached log file. I'm developing device for home assistant zigbee network, and coordinator is kind of Silabs based device. It's probably not a coordinator problem. Joining another devices work still fine. Only reset of the Nucleo helps. Now i have only one NUCLEO-WB55.

After error occurrence probably full initialization of the zigbee stack will help. I can try this, but i think it's not a correct way. And because of no source codes for coprocessor i can only guess.

With RFD seems to me that error happen more often, and earlier after power up. Also seems kind of temperature dependent. But i have no relevant data. Could it be problem of first silicon version? After shield remove i found my Nucleo-WB55 is one from the first pieces populated with ES32WB55.

Regard,

Slavomir

[Ouadi · Accepted solution]

Hello Slavomir,

Actually the nucleo board you are using is among the first development based on the ES32WB55 which is a very early sample of STM32WB product not fully validated and may have some issues corrected in the final STM32WB devices delivered on the market.

I recommend highly to acquire the latest version of the nucleo board that may resolve your issue, if not, a sniffer logs would be appreciated to analyze the radio environment as I'm not able to reproduce the issue with a WB55 coordinator.

Best regards,

Ouadi

[SToma]

Hi Ouadi,

thanks you for your help. I'll buy new nucleo. I should check version of the device earlier. For now we can close this case. Again, thank you.

Regards,

Slavomir