Lines Matching +full:crc +full:- +full:enabled

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.
22 of: id, data offset in sector, data length, part (unused), and a CRC. This CRC is
25 CRC-32. Use the :kconfig:option:`CONFIG_NVS_DATA_CRC` configuration item to enable
26 the data part CRC.
28 .. note:: The data CRC is checked only when the whole data of the element is read.
29   The data CRC is not checked for a partial read, as it is stored at the end of the
32 .. note:: Enabling the data CRC feature on a previously existing NVS content without
33   data CRC will make all existing data invalid.
42 NVS checks the id-data pair before writing data to flash. If the id-data pair
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.
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,
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
128    NVS can use the internal flash of the SoC.  While the MPU is enabled,
133    multi-threaded application, another thread might intercept the fault
134    and the NVS API will return an ``-ETIMEDOUT`` error.