ESP32 Forum

Posted: **Sat Nov 23, 2024 9:02 am**

In the project ESP32-S3R8 with 8MB of PSRAM and external 16MB of Flash is used.

We use custom partition table to have a small NVS partition and a large App partition (15Mb) and no OTA partition.

Project works when App size is less than 8MB and PSRAM is enabled. No error in accessing the NVS partition.
As soon as App size become greater than 8MB and PSRAM is kept enabled. Error generated on accessing the NVS data – (NVS partition not available)
Also even when App size is greater than 8MB but PSRAM is disabled. No error in accessing the NVS partition.

Error message:
E (2081) partition: load_partitions returned 0x101
ESP_ERROR_CHECK failed: esp_err_t 0x105 (ESP_ERR_NOT_FOUND) at 0x420084f8
0x420084f8: app_main at /main.c:18 (discriminator 1)

NVS access error in this code

Code: [Select all] [Expand/Collapse]

#include <stdio.h>
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "nvs_flash.h"
#include "nvs.h"
#include "esp_log.h"
extern uint8_t MyFile_bin_start[] asm("_binary_MyFile_bin_start");
int cnt=0;
void app_main(void)
{
// Initialize NVS
    esp_err_t err = nvs_flash_init();
    if (err == ESP_ERR_NVS_NO_FREE_PAGES || err == ESP_ERR_NVS_NEW_VERSION_FOUND)
    {
        ESP_ERROR_CHECK(nvs_flash_erase());
        err = nvs_flash_init();
    }
    ESP_ERROR_CHECK(err);
    vTaskDelay(20 / portTICK_PERIOD_MS);
    nvs_handle_t nvs_handle;
 
    // Open NVS handle
    err = nvs_open("nvs", NVS_READWRITE, &nvs_handle);
    if (err != ESP_OK)
    {
        ESP_LOGI("MyLog", "Error (%s) opening write NVS handle!\n", esp_err_to_name(err));
        return;
    }
 
    // Read array from NVS under the provided key
    size_t required_size = 1 * sizeof(int);
    err = nvs_get_blob(nvs_handle, "cntData", &cnt, &required_size);
    if (err == ESP_OK)
    {
        ESP_LOGI("MyLog", "Array for key cntData retrieved successfully!\n");
        // for (int i = 0; i < size; i++) {
        //     ESP_LOGI("MyLog","Array[%d] = %d\n", i, arr[i]);
        // }
    }
    else
    {
        ESP_LOGI("MyLog", "Error (%s) reading key %s!\n", esp_err_to_name(err), "cntData");
    }
 
    cnt++;
    // Write array to NVS under the provided key
    err = nvs_set_blob(nvs_handle, "cntData", &cnt, required_size);
    if (err != ESP_OK)
    {
        ESP_LOGI("MyLog", "Error (%s) writing to key %s!\n", esp_err_to_name(err), "cntData");
    }
 
    // Commit write
    err = nvs_commit(nvs_handle);
    if (err != ESP_OK)
    {
        ESP_LOGI("MyLog", "Error (%s) committing!\n", esp_err_to_name(err));
    }
 
    // Close NVS handle
    nvs_close(nvs_handle);
 
    ESP_LOGI("MyLog", "Cnt value: %d", cnt);
    cnt = MyFile_bin_start[0];  //array from external linked bin file 
}

GeSHi © Codebox Plus Extension

Looks like when App size is greater than 8MB + PSRAM is enabled than NVS partition access generates error (load_partitions returned 0x101).

A small project is attached to demonstrate this effect.
In this project an external bin file (MyFile.bin) containing a large size array is accessed from the App. By varying the data size of the bin file, overall app size can be made greater or less than 8MB.

The PSRAM usage is enabled / disabled using the menu-config option. (menuconfig -- ESP PSRAM -- Support for external, SPI-connected RAM)

In the project, at the beginning, a variable is accessed from the NVS storage area, incremented and stored back to NVS.

Any guidance/hint at solving the NVS partition access when App size is greater than 8MB and PSRAM enabled is appreciated.

Custom partition table:
# Name, Type, SubType, Offset, Size, Flags
nvs, data, nvs, 0xA000, 0x6000,
phy_init, data, phy, , 0x1000,
factory, app, factory, 0x100000, 15M,

Posted: **Sun Nov 24, 2024 8:55 am**

Hi @VinayDand,
error 0x101 means out of memory, which can have various reasons in your case. Quick-fix proposal before checking your logs:
try to enable NVS allocations in PSRAM in the menuconfig (idf.py menuconfig):

Component config > NVS > Prefers allocation of in-memory cache structures in SPI connected PSRAM (CONFIG_NVS_ALLOCATE_CACHE_IN_SPIRAM)

Posted: **Sun Nov 24, 2024 1:02 pm**

May have something to do with memory mapping via the MMU. Both the application in flash and the PSRAM are memory-mapped. And NVS tries to also memory-map part of the NVS partition. Might be that the MMU runs out of pages after 8MB of flash + 8MB of PSRAM are mapped in.

Posted: **Mon Nov 25, 2024 2:17 am**

MicroController wrote: ↑
Sun Nov 24, 2024 1:02 pm
May have something to do with memory mapping via the MMU. Both the application in flash and the PSRAM are memory-mapped. And NVS tries to also memory-map part of the NVS partition. Might be that the MMU runs out of pages after 8MB of flash + 8MB of PSRAM are mapped in.

The hardware can handle that situation fine, though... iirc the S3 has 32M of address space, so 8+8M should fit fine in there.

ESP32 Forum

NVS access issue when app size >8MB and PSRAM enabled

NVS access issue when app size >8MB and PSRAM enabled

Re: NVS access issue when app size >8MB and PSRAM enabled

Re: NVS access issue when app size >8MB and PSRAM enabled

Re: NVS access issue when app size >8MB and PSRAM enabled