LAUNCHXL-CC1312R1: Use of NVS.h. NVS_open() & NVS_close()

Viktor Cherviakov

Hi TI team, I have a general question about NVS implementation to read / write to external flash (Macronix MX25R)

What is the rule of thumb using NVS_open() and NVS_close().

For each read transaction should I call NVS_open() then do read and then NVS_close() or it is fine to open the region once for multiple read/write transactions and leave it open. What are the implications of the second approach (leaving the region open for multiple read transaction)?

NVS.h does not specify the desired approach

Best,

Viktor

2 months ago

0 Arthur R☑️ 2 months ago

TI__Genius 16876 points

Hi Viktor,

NVH.h is indeed flexible when it comes to that. You do not need to use NVS_close on both internal and external implementations.

I think that you could use NVS_close if you want to do a graceful reset of your application and clean-up all the drivers prior to that, for instance.

Regards,

Arthur

0 Viktor Cherviakov 1 month ago in reply to Arthur R☑️

Prodigy 20 points

Arthur, thanks.

Just want to add some observations that we noticed:

Seems, if there is no real need to call NVS_close after each transaction and NVS_open before a transaction, better not to do that as NVS_open triggers CS line in SPI to change its value and having a power problems at that same moment may corrupt the flash contents

Besy,

Viktor

+1 Arthur R☑️ 1 month ago in reply to Viktor Cherviakov

TI__Genius 16876 points

Hi Viktor,

Thanks for the feedback, I see that your colleague (https://e2e.ti.com/support/rf-microwave-group/rf-microwave/f/rf-microwave-forum/1331975/launchxl-cc1312r1-unwanted-flash-erasing) may have been facing the exact same issue.

Regards,

Arthur

Sub-1 GHz

Sub-1 GHz forum

LAUNCHXL-CC1312R1: Use of NVS.h. NVS_open() & NVS_close()