espressif/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2026-04-27 19:13:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'feature/nvs_fd_support' into 'master'

Browse Source 
feat(nvs_flash): Added support for storing flash and double types

Closes IDFGH-9857

See merge request espressif/esp-idf!47045
This commit is contained in:
Radek Tandler
2026-04-15 11:03:57 +02:00
parent 76ef396b49 a5443bbb94
commit 5c8f5fc66d
12 changed files with 1146 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/api-reference/storage/nvs_flash.rst
+4 -1
View File
@@ -35,6 +35,7 @@ NVS operates on key-value pairs. Keys are ASCII strings; the maximum key length
- integer types: ``uint8_t``, ``int8_t``, ``uint16_t``, ``int16_t``, ``uint32_t``, ``int32_t``, ``uint64_t``, ``int64_t``
- zero-terminated string
- variable length binary data (blob)
- floating point types: ``float`` and ``double``
.. note::
@@ -48,7 +49,9 @@ NVS operates on key-value pairs. Keys are ASCII strings; the maximum key length
Before setting new or updating existing key-value pair, free entries in nvs pages have to be available. For integer types, at least one free entry has to be available. For the string value, at least one page capable of keeping the whole string in a contiguous row of free entries has to be available. For the blob value, the size of new data has to be available in free entries.
Additional data types, such as ``float`` and ``double`` might be added later.
.. note::
The floating point types ``float`` and ``double`` are supported regardless of the FPU presence on a particular SoC.
Keys are required to be unique. Assigning a new value to an existing key replaces the old value and data type with the value and data type specified by a write operation.