is application required to use NVRAM ?

[Anonymous]

Are there any reads or writes with NVRAM that the peripheral or central application is absolutely required to do?

Or, is NVRAM usage optional?

[MichaelF_56]

Within the BCM20732 Tag board environment and 20732S module, the onboard EEPROM includes BD ADDR (Bluetooth Device Address), Patches and Bonding/Pairing information. The application code then links against ROM and patches.

In addition,within the WICED Smart dev environment, the SDK downloads a minidriver to RAM then pushes the application code over the HCI uart to the minidriver which will then write to EEPROM.  From there, the SDK will automatically load the application into available RAM.

[Anonymous]

My question is this:  are there any NVRAM reads or writes that I myself must put into the source code of my peripheral or central application software that I download to my BCM20732?

I have central application software source code for our central embedded board, and peripheral source code for our peripheral board.

Is there any software source code that reads or writes NVRAM that MUST be in our application software source code?

Presently, I'm debugging connection problems, and I'm wondering if there is a NVRAM write operation missing from the central or peripheral application software source code that we write.

[VictorZ_46 · Accepted solution]

If there is nothing in your application that should be persistent between device power cycles, you do not need to save anything in the NVRAM.