CC2642R: nv open failed on SDK3_20

Jie Lin1

Part Number: CC2642R

We develop our application on SDK sdk_3_20, and find an issue:
We use the API osal_snv_write to save some private data, then use osal_snv_read to get the saved data later. Sometimes osal_snv_read will return 0x0A(NV_OPER_FAILED), or return SUCCESS but the data are all 0. The probability of this issue is not high, we have not find a clue to reproduce this issue.

over 5 years ago

0 desouza over 5 years ago

TI__Guru**** 171979 points

Hi,

Being a rare event turns things a lot harder to track, but I wonder if you are running into one of the limitations mentioned in the OSAL section of our Stack User's Guide:

https://dev.ti.com/tirex/explore/content/simplelink_cc13x2_26x2_sdk_5_10_00_48/docs/ble5stack/ble_user_guide/html/ble-stack-common/flash_memory-cc13x2_26x2.html#limitations-and-intended-use

Did you open the memory browser and looked at the SNV region that corresponds to the data you are trying to read? That might reveal additional details about this.

I couldn't find a report about a known bug or prior discussion that covers such issue on the device and SDK you are using, but I will keep looking and report back in case I find anything.

Hope this helps,

Rafael

Bluetooth®︎

Bluetooth forum

CC2642R: nv open failed on SDK3_20