CC1352P7: Issue with NVS Read Operation Causing System Crash

Please specify what SDK version you are using, and what SW examples/stacks etc. you are running from the SDK.

Siri

what example are you running, and why are you not using the latest SDK (simplelink_cc13xx_cc26xx_sdk_8_32_00_07)?

Siri

We've been using this SDK version for a long time in our custom application, so upgrading isn't an option for us right now. We used to see this issue very rarely, but we want to get to the bottom of it this time. Interestingly, we found a workaround during testing: if we execute an nvFps.eraseNV operation right before calling nvFps.readItem, the CC1352 recovers and works normally.

You are still not answering my question. 

What SW example are you running / which stack?

nvFps.readItem is not part of the NVS driver (NVS.h File Reference)

I cannot help you without understanding what code you are referring to.

Siri

Our application project is based on the following example project.

Hi,

Is it possible that you're reading NVS at the same time as the TI 15.4-Stack is trying to read NVS?

Did you configure your own NVS region or are you using the same one as the TI 15.4-Stack?

Cheers,

Marie H

We haven't checked whether the TI-15.4 stack uses NVS. Our NVS implementation is as follows:

Hi,

TI 15.4-Stack uses NVS to store network information. If the device is joining or in a network there is a chance it will access NV.

Can you check if this happens if you don't have any collector devices running, i.e. not joining or in a network?

Cheers,

Marie H

Before the 15.4-stack starts, the NVS read operation fails and causes a system crash.

Hi,

Can you verify that the NV initialization code has run at that time?

Cheers,

Marie H

Yes, we have confirmed that it is initialized.