Lines Matching +full:write +full:- +full:protect

3 Non-Volatile Storage (NVS)
6 Elements, represented as id-data pairs, are stored in flash using a
7 FIFO-managed circular buffer. The flash area is divided into sectors. Elements
10 sector it is checked that identifier - data pairs exist in the sectors in use,
11 if not the id-data pair is copied.
13 The id is a 16-bit unsigned number. NVS ensures that for each used id there is
14 at least one id-data pair stored in flash at all time.
23 only calculated over the metadata and only ensures that a write has been
25 CRC-32. Use the :kconfig:option:`CONFIG_NVS_DATA_CRC` configuration item to enable
35 A write of data to nvs always starts with writing the data, followed by a write
42 NVS checks the id-data pair before writing data to flash. If the id-data pair
43 is unchanged no write to flash is performed.
45 To protect the flash area against frequent erases it is important that there is
52 .. code-block:: c
63 - ``NVS_FLASH_DEVICE`` is a reference to the flash device that will be used. The
65 - ``NVS_SECTOR_SIZE`` is the sector size, it has to be a multiple of
67 - ``NVS_SECTOR_COUNT`` is the number of sectors, it is at least 2, one
69 - ``NVS_STORAGE_OFFSET`` is the offset of the storage area in flash.
88 Each write of the state variable requires 12 bytes of flash storage: 8 bytes
99 - ``NS`` as the number of storage requests per minute,
100 - ``DS`` as the data size in bytes,
101 - ``SECTOR_SIZE`` in bytes, and
102 - ``PAGE_ERASES`` as the number of times the page can be erased,
111 Flash write block size migration
114 changes the supported minimal write block size.
115 The NVS in-flash image will stay compatible unless the
117 Especially, migration between 1,2,4,8-bytes write block sizes is allowed.
127 MPU fault while using NVS, or ``-ETIMEDOUT`` error returned
133    multi-threaded application, another thread might intercept the fault
134    and the NVS API will return an ``-ETIMEDOUT`` error.