mirror of
https://github.com/espressif/esp-idf.git
synced 2026-08-13 12:46:04 +03:00
Function now always rewrites old value under same key regardless existing data type. Users requiring old API behaviour can enable it by kconfig option CONFIG_NVS_LEGACY_DUP_KEYS_COMPATIBILITY
38 lines
1.9 KiB
Plaintext
38 lines
1.9 KiB
Plaintext
menu "NVS"
|
|
|
|
config NVS_ENCRYPTION
|
|
bool "Enable NVS encryption"
|
|
default y
|
|
depends on SECURE_FLASH_ENC_ENABLED
|
|
help
|
|
This option enables encryption for NVS. When enabled, AES-XTS is used to encrypt
|
|
the complete NVS data, except the page headers. It requires XTS encryption keys
|
|
to be stored in an encrypted partition. This means enabling flash encryption is
|
|
a pre-requisite for this feature.
|
|
|
|
config NVS_COMPATIBLE_PRE_V4_3_ENCRYPTION_FLAG
|
|
bool "NVS partition encrypted flag compatible with ESP-IDF before v4.3"
|
|
depends on SECURE_FLASH_ENC_ENABLED
|
|
help
|
|
Enabling this will ignore "encrypted" flag for NVS partitions. NVS encryption
|
|
scheme is different than hardware flash encryption and hence it is not recommended
|
|
to have "encrypted" flag for NVS partitions. This was not being checked in pre v4.3
|
|
IDF. Hence, if you have any devices where this flag is kept enabled in partition
|
|
table then enabling this config will allow to have same behavior as pre v4.3 IDF.
|
|
|
|
config NVS_ASSERT_ERROR_CHECK
|
|
bool "Use assertions for error checking"
|
|
default n
|
|
help
|
|
This option switches error checking type between assertions (y) or return codes (n).
|
|
|
|
config NVS_LEGACY_DUP_KEYS_COMPATIBILITY
|
|
bool "Enable legacy nvs_set function behavior when same key is reused with different data types"
|
|
default n
|
|
help
|
|
Enabling this will switch the nvs_set family of functions to the legacy mode. When called with same
|
|
key and different data type, existing value stored in NVS remains active and as a side effect, the
|
|
new value is also stored into NVS, although not accessible using respective nvs_get function. Use only
|
|
if your application relies on this NVS API behaviour.
|
|
endmenu
|