[Zigbee] ZBOSS Fatal Error at init

RE: [Zigbee] ZBOSS Fatal Error at init

Amanda Hsieh — Mon, 08 Jul 2024 13:58:45 GMT

Hi,

The fix is in the ZBOSS stack, in sdk-nrfxlib.
This nrfxlib revision has been pulled into NCS in this commit:
https://github.com/nrfconnect/sdk-nrf/commit/03357d46827dcea2ed76042b912221af0c587d01

-Amanda H.

RE: [Zigbee] ZBOSS Fatal Error at init

Pawel(embeddedsolutions.pl) — Sun, 07 Jul 2024 10:27:28 GMT

Is it fixed directly in ZBOSS stack or NRF Connect SDK?
May I see the commit implementing that fix?

RE: [Zigbee] ZBOSS Fatal Error at init

Amanda Hsieh — Fri, 05 Jul 2024 12:42:05 GMT

It's fixed by NCS v2.7.0 which is released now.

RE: [Zigbee] ZBOSS Fatal Error at init

Pawel(embeddedsolutions.pl) — Wed, 28 Feb 2024 16:12:45 GMT

Hi,

Thank you for fast response.

End user may not be able to do the factory reset of any of the devices with this "inconvienence" unless customer has jlink programmer to erase the zboss_nvram partition manually.

Assert is generated inside the ZBOSS stack which is a black box so developers are not even able to check some return code and recover the device in such scenario.

I strongly agree with you that recovery mechanism should be implemented in the stack. Thank you for creating Jira ticket for this :)

Regards,

Pawel

RE: [Zigbee] ZBOSS Fatal Error at init

Amanda Hsieh — Tue, 27 Feb 2024 15:03:20 GMT

Hi,

Could be that NVRAM gets corrupted since you turn off the device exactly when it is writing important data to NVRAM.

At the same time, I feel like it's expected that the device might fail if you turn it off while it is joining a network. In such a case I think it should be possible to expect that the end user just factory resets the device as a way to recover it. But I agree that this should be something that is implemented in the stack by default and not something our customers should have to manually implement a fix for. I would create an internal Jira for this.

Regards,
Amanda H.