CC1352R: Simple Peripheral with OAD, store additional data in non volatile memory

user5943842

Part Number: CC1352R
Other Parts Discussed in Thread: SYSCONFIG

Hi,

Currently I am trying to store 2 large string arrays and 2 custom structures in non-volatile memory. It is important that these are not lost on reboot or anything like that.
I believe I should use the NVS driver, as the osal_snv driver only supports the use of 2 pages, which is not enough for my data.

Am I correct to use the NVS driver?
I have already tried to use the example code for the NVS internal. However, when trying nvs_read(), the code hangs indefinitely. The same happens when I try adding NVS regions to the Simple Peripheral with On Chip OAD example code.

Any help would be greatly appreciated!

Thank you.

over 6 years ago

0 Eirik V over 6 years ago

TI__Guru 56590 points

Hello User,

Please use the Simple Non Volatile memory (SNV):

dev.ti.com/.../flash_memory-cc13x2_26x2.html

0 user5943842 over 6 years ago in reply to Eirik V

Expert 1550 points

Hello Eirik,

Thank you for your response!

Two questions:
1) I believe I read somewhere that SNV only supports up to 2 pages of memory? Or is this purely a limitation for the stack?
2) Also, The documentation you sent seems to indicate that OSAL SNV uses the ICall layer. I have added many tasks to the example project, which currently do not use ICall. Do I have to change them to use ICall to enable the use of SNV?

0 Eirik V over 6 years ago in reply to user5943842

TI__Guru 56590 points

Hello User,

1) Yes, it is limited to 2 pages due to the implementation.

2) Yes, your task must be Icall enabled to access the OSAL SNV. The Users Guide describe how to Icall enable a task.

0 user5943842 over 6 years ago in reply to Eirik V

Expert 1550 points

Thank you for your response again Eirik.

Nevertheless I do have one concern. The data I would like to store is bigger than 2 pages. What driver can I best use now that can not use OSAL SNV?

0 Eirik V over 6 years ago in reply to user5943842

TI__Guru 56590 points

Hello user,

You can reserve a space in the linker file and either use the flash directly via Driverlib and read/write to the reserved sectors or try to create an additional NVS configuration that covers this custom region. I have not tested this though. In simplelink_cc13x2_26x2_sdk_3_30_00_03 you can use Sysconfig to add another NVS Driver Configuration and see the required code generated in ti_drivers_config.c.

http://dev.ti.com/tirex/explore/node?node=ADfS7ixpgUmHy56H6NON4Q__krol.2c__LATEST

Bluetooth®︎

Bluetooth forum

CC1352R: Simple Peripheral with OAD, store additional data in non volatile memory