nRF52840(PCA10056DK) ZigBee examples keep rebooting with ZBOSS Error

[arikyang]

Hi,

I am facing a very similar issue like this post.  nRF52840 ZigBee examples keep rebooting with ZBOSS Error 

But I am running DK not PDK. And the stack trace shows the error may be from zb_nvram_load()

All the Zigbee examples have the same error. I have tried both NCS V2.2.0 and 2.1.0  and they are not working. The weird thing is the development environment was working fine. Just all of the sudden, enabling Zigbee will reboot the system.

Thanks in advance.

[arikyang]

I have tried to erase NVRAM for Zigbee below that can recover the board. 

zigbee_erase_persistent_storage(ZB_TRUE);

[Amanda Hsieh]

Hi, 

I cannot reproduce it with NCS v2.2.0 network_coordinator, light_switch, and light_bulb by adding zigbee_erase_persistent_storage(ZB_TRUE); after register_factory_reset_button(FACTORY_RESET_BUTTON); in the samples. 

Could you provide the snippet code or project?

Regards,
Amanda H.

[arikyang]

Our test engineer found out that switching the power off and on frequently can reproduce this issue.

HW: PCA10056

SW: NCS 2.1.0, Zigbee "light switch" example

Zigbee stack reads NVRAM to get connection information while starting. We guess powering off while the stack is accessing NVRAM may cause data to crash. and If the data in NVRAM is messed up, it will fire a fatal error. 

So, what is the best way to handle this case?

many thanks,

[Amanda Hsieh]

Hi, 

Please read and provide the flash memory content or at least the part that ZBOSS NVRAM is stored in - this should allow us to get some sense of what exactly is wrong with the ZBOSS persistent data. Also, it could be useful to get some ZBOSS traces so we can see where in the code the ZBOSS assert was triggered. It seems to me that what it has achieved is forced flash corruption which wouldn't have a place in normal working conditions (Maybe I am wrong.) We are sure why the development environment is not causing issues but hopefully, an analysis of the device's NVRAM could give us an answer to this issue. 

Regards,
Amanda H.