Datasheet

Page 31 of 161
nRF8001 Product Specification
Revision 1.2
9 Data storage and memory retention
Data stored in nRF8001 is either stored in volatile or non-volatile memory, depending on the type of data.
In this document, data is differentiated into two categories; static and dynamic data.
Static data:
nRF8001 can be configured through the ACI to hold hardware and protocol parameters, see Part
B, section 22.3 on page 81. Setup data can be written to non-volatile memory for permanent
storage or to volatile memory during application development. Once programmed in non-volatile
memory, the parameters set the circuit to the defined default state on power up or reset.
Dynamic data:
During normal runtime operation, your nRF8001 application will contain the Attributes and acquire
information about peer devices and the services they offer. Your application may also establish a
bonded relationship with a peer device. The information your application acquires as a result of
normal runtime operation, is stored in nRF8001 volatile memory as dynamic data.
9.1 Permanent Storage
nRF8001 includes one time programmable Non-Volatile Memory (NVM). The hardware device setup and
pipe setup as defined in Part B, section 22.3 on page 81
are programmed into the NVM memory for
permanent storage. Once information has been stored in NVM, it cannot be changed.
The nRFgo Studio configuration tool offers two setup file alternatives. One file will store the setup in NVM,
the other will store the setup in volatile memory. For application development, setup storage in volatile
memory will allow adjustments without discarding the device.
Note: Setup storage in volatile memory will be lost when the device is reset or power cycled.
9.2 Volatile Storage
Dynamic data is stored in RAM and will be lost if nRF8001 is power cycled or reset. Typical data stored in
RAM includes profile client information, bonding addresses and keys.
Dynamic data may be read out of nRF8001 and stored in the application controller. Upon power cycling
and attempting to re-enter a connection with a previously established relationship to a peer device, the
data is written back into nRF8001 from the external application controller. This procedure is defined in Part
B, section 22.4.6 on page 87.