NVRAM CORRUPTION

[Udaykumar07]

Hi ,

I am using skb501 module and which contains nrf52840.I am using nrf5sdk for development for zigbee coordinator because nrf connect sdk is not supportable in this chipset.I am getting serious issue like sometimes NVRAM is corrupting.If I erase NVRAM ,device is recovering but end device info.Now can you tell any issue is there related to NVRAM in nrf5sdk and what is the format of parameters stored in NVRAM in nrf5sdk so that we can work around to get it resolved.Pls give any documents related to persistent storage in NVRAM for zigbee.Can u tell any precautions I should do in application to get rid of this 

[Marte Myrvold]

Hi,

The nRF5 SDK for Thread and Zigbee is deprecated, and the Zigbee stack integrated with the nRF5 SDK version is not eligible for certification.

For new projects, you should use the nRF Connect SDK. The Zigbee R23 add-on is supported on the nRF52840.

Best regards,
Marte

[Udaykumar07]

Correct but skb501 is not supporting  nrf connect sdk ..I have only option to go with nrf5sdk and devices already in market..I am getting this NVRAM issue in site randomly..Please let me know any format or documentation of parameters stored in NVRAM and any input to get this out

[Marte Myrvold]

Hi,

This issue could be related to NCSISB-1204 in known issues: 

NCSISB-1204: Corrupted ZBOSS NVRAM causes an infinite boot loop
NVRAM writing operations are not reset (for example, due to FOTA) and are power-down resistant. In such scenarios, the ongoing NVRAM record-writing operation will not be completed correctly. That means a corrupted NVRAM record. During boot, the ZBOSS stack reads NVRAM content, and in the event of detecting an NVRAM record, it generates a fatal error and leads to the device reset itself. From this point, the device boots, reads NVRAM, and detects corrupted records, which leads to a device reset. If such behavior is constantly repeated, the device will brick.

Unfortunately, this fix includes updating the pre-compiled ZBOSS libraries and is only available in the nRF Connect SDK. Since the nRF5 SDK for Thread and Zigbee is deprecated, it will not receive bug fixes or updates.

Udaykumar07 said:

skb501 is not supporting  nrf connect sdk ..I have only option to go with nrf5sdk

Have you confirmed this with the module maker? I do not see any reason why it should not be possible to use it with the nRF Connect SDK. The module is not officially supported there, but it should be possible to create board files to add support.

Best regards,
Marte

[Udaykumar07]

Thank you for your response. There is no support from the vendor. In nrf5sdk, Only after nvram erase stack will dynamically generate panid, extpanid, channel number, network key and stored in NVRAM.So I will allow stack to  write in NVRAM only at this time (network formation) and In all other cases like nodes join/rejoin , steering on , nrf reset or other cases I will stop stack to write in NVRAM .By this I can solve this NVRAM corruption and this mandatory network parameters already stored in NVRAM so nrf can form same network after reset thereby nodes can be intact with coordinator.                                               Is this solution correct or any impact of node connections if we block NVRAM write in other cases ???

[Gaurav Kapoor]

uday , you can explore locally made indian modules certified which support NCS for thread , zigbee or any nordic protocols. 

tks

Gaurav