cancel
Showing results for 
Search instead for 
Did you mean: 

WICED Smart Bluetooth

user_2112781
Contributor

Hello,

I understood that the application was using the space in VS1 for peering data and also for bleprofile_*NVRAM.

But what is the physical offset from VS1  those functions are using on the EEPROM ?

I would like to access directly the EEPROM via bleappfwu_*Mem and store some information in this VS1 area without messing with the application.

How much do I have left on the 1024 bytes area and at which offset ?

0 Likes
1 Solution
ArvindS_76
Employee

> I would like to access directly the EEPROM via bleappfwu_*Mem and store some information in this VS1 area without messing with the application.

You should always use bleprofile_*NVRAM functions add/modify/delete items to the VS. If you use bleappfwu_*Mem functions with addresses in the VS area, there is a very good chance that you will lose pairing information at best or brick the device at worst.

View solution in original post

3 Replies
ShawnA_01
Employee

This posting has more information on your application using this memory area:  Re: Programming manufacturing data during production.  

ShawnA_01
Employee

There is also this one:  Re: nvram: number of locations to write to

0 Likes
ArvindS_76
Employee

> I would like to access directly the EEPROM via bleappfwu_*Mem and store some information in this VS1 area without messing with the application.

You should always use bleprofile_*NVRAM functions add/modify/delete items to the VS. If you use bleappfwu_*Mem functions with addresses in the VS area, there is a very good chance that you will lose pairing information at best or brick the device at worst.

View solution in original post