Hi. I disabled now the two options CONFIG_ESP32_WIFI_IRAM_OPT and CONFIG_ESP32_WIFI_RX_IRAM_OPT. With this there is enough space in the IRAM segment. According to the idf.py size-components the libc.a and libesp32.a need much more space in IRAM when the external PSRAM is enabled. Also the total imag...

Hi. I have a ESP32 project based on ESP-IDF branch /release/v4.0, which uses Wifi and BLE (Nimble stack). Until now I built the project with disabled external RAM and idf.py size-components gave the following sizes: Total sizes: DRAM .data size: 17816 bytes DRAM .bss size: 49064 bytes Used static DR...

Hi Angus. I tried your patch with the wear_levelling example and the encrypted flag set on the storage partition. Now the low level errors have disapeared, but now I get the high level error when opening a file for writing: I (244) example: Mounting FAT filesystem W (404) vfs_fat_spiflash: f_mount f...

@ESP_igrr I only set the encryped flag in the partition table. But I do not think that enabling encryption via the bootloader would make it work, because the error E (203) wl_flash: initSections(269): result = 0x00000104 points to the code at WL_Flash.cpp line 298/269 result = this->flash_drv->write...

Hi all. I took the wear_levelling example and set the encrypted flag on the storage partition: # Name, Type, SubType, Offset, Size, Flags # Note: if you change the phy_init or app partition offset, make sure to change the offset in Kconfig.projbuild nvs, data, nvs, 0x9000, 0x6000, phy_init, data, ph...