Hi Serdar, I would like to learn whether this issue is still actual. If so, please extend the code with logging of the str variable content prior to the call of nvs functions and result code returned by each of the nvs functions called. Please post the values log. Please include also content of the ...

1)What does disable_dl_encrypt and disable_dl_decrypt does? These 2 options disable encryption/decryption performed directly on the target chip (using the key and encryption algorithm settings taken from target chip). In other words, once you enable these options, you have to work with encrypted ima...

Hello, The NVS subsystem doesn't overwrite the old values in the NVS pages. It marks old value as deleted and finds a free space where it stores the new value. So it works like a running log. At the moment, when no free space is available for new data, the records marked as erased are reclaimed and ...

Hi weimeijia, The CONFIG_APP_BUILD_TYPE_PURE_RAM_APP disables the SPI_FLASH sub system and therefore it is not possible to use the NVS component as it relies on the working SPI_FLASH. In reward, it releases some 26kB of RAM. If your application fits into the memory in default setting (without CONFIG...

HI @jwachsmuth, I would suggest first commenting out the ESP_ERROR_CHECK(esp_eventLoop_create_default()); to see if there is an interference between the nvs initialisation and anything, that may be already running in parallel to it from the event loop. Then you may simply swap the order of the lines...

Hi kevinevans,

You can use ESP IDF examples/storage/ext_flash_fatfs as a starting point to learn, how to let external SPI based flash work with filesystems supported in the ESP IDF.

Hi squirtle321, One more note. You may also try to run tests with the same NVS partition size and vary the number of different key - value pairs to see the influence of active data amount on the Key Hash Map heap overhead. Start with empty NVS, make nvs_init and the heap overhead (nvs partition size...

Hello squirtle321, The RAM footprint of NVS after initialisation is comprised of 2 components: Item Hash List (namespace, key, chunk index) - size depends on number of active key-value pairs Page manager related footprint - size depends on NVS partition size Run your statistics with various NVS part...

Hi Vincecube, The state of NVS flash you are describing - 3 pages are marked as FULL and one page is marked as FREEING is assumed to be inconsistent for nvs_init function. It expects at least one ACTIVE or UNINITIALIZED page when it sees FREEING page. I am not sure what caused the state you describe...

@mtaz78 - Please also check whether you have Enabled PSRAM in menuconfig and set Flash and PSRAM frequiencies to 80MHz