LAUNCHXL-CC26X2R1: Using Simple NV for ProjectZero

Trevor Hsu

We have some questions about Simple NV:

1. In project_zero.c, it uses the Simple NV to store the "Service changed flag"(after receiving "OAD_COMPLETE_EVT" ), but it seems no one to access it, could you help to double check it? May I comment out this portion of code?

2. About customer NV, the range is 0x80 - 0x8F, does it means I have the 16 locations to store data? What is the size of the data that can be stored on each locations(ID)?

3. Do you have any tools to read/write/erase the Simple NV area?

4. What is the maximum size of customer NV? we would like to store 16KB user data, do you have any suggestions to me?

SDK Version: simplelink_cc13x2_26x2_sdk_3_20_00_68

Thanks.

Trevor

over 6 years ago

0 J Lindh over 6 years ago

TI__Guru 57865 points

Hi,

1, I believe it's a mandatory function but I haven`t really seen any customer using it to be frank.

2. Please see the users guide for more info: http://dev.ti.com/tirex/explore/content/simplelink_cc13x2_26x2_sdk_3_20_00_68/docs/ble5stack/ble_user_guide/html/ble-stack-common/flash_memory-cc13x2_26x2.html#flash-vector-table

3. No, unfortunately not.

0 Trevor Hsu over 6 years ago in reply to J Lindh

Genius 4605 points

Hi Joakim,

Thanks for your reply,

Regarding Q2, I tried to write a 1K buffer to 0x80, it didn't work. do yo have any suggestions for me(264B & 512B & 768B can work)?

Could you also help to check the question#4?

Thanks.

Trevor

0 Trevor Hsu over 6 years ago in reply to Trevor Hsu

Genius 4605 points

About Question 2 , we tried to write the 256Byte/512Byte/768 data into ID#0x80, it works. But if I increase the data size to 1K, it won't work. Do you know what the maximum size can be written for each ID???

Could you also help to check the question#4?

Thanks.

Trevor

0 Eirik V over 6 years ago in reply to Trevor Hsu

TI__Guru 56590 points

Hello Trevor,

The Two Page Non Volatile Memory On Chip (NVOCTP) use a 12 bit length field in the header which limit the block size to 4,096 bytes. But This can be much less if for example the stack has stored bonds or other use data that has fragmented the flash sector.

http://dev.ti.com/tirex/content/simplelink_cc13x2_sdk_2_20_00_71/docs/ble5stack/ble_user_guide/html/ble-stack-common/flash_memory_cc26x2_cc13x2.html#two-page-non-volatile-memory-on-chip-nvoctp

The NVSpace used by OSAL is defined in the board file(CC26X2R1_LAUNCHXL.c) and controlled by the NVS driver. For CC26x2 the sector size is 8kB and two sectors are used to enable safe compaction.

#define NVS_REGIONS_BASE 0x48000
#endif //OAD_ONCHIP
#define SECTORSIZE 0x2000
#define REGIONSIZE (SECTORSIZE * 2)

I could successfully write 4 K data after boot with the OSAL SNV example code from the Users Guide:

http://dev.ti.com/tirex/content/simplelink_cc13x2_sdk_2_20_00_71/docs/ble5stack/ble_user_guide/html/ble-stack-common/flash_memory_cc26x2_cc13x2.html#osal-snv-example

This thread also has some juicy details:

e2e.ti.com/.../739001

Bluetooth®︎

Bluetooth forum

LAUNCHXL-CC26X2R1: Using Simple NV for ProjectZero