Hello,

Is this possible to modify bootloader code that way, to have runtime detection that Flash and SPIRAM can be run in QIO mode with 80Mhz clock, then set it or fallback to DIO/40Mhz ?

The goal is to have one firmware for different boards with fastest possible IO on each.

Ok, finally i got it to work, my first suspicion that maybe linker scripts need rework were correct. The problem was that libraries names generated by PlatformIO build doesn't match those in esp32.common.ld , so libraries like freertos were not put into IRAM. I learned that after opening issue https...

Does the same issue happen in ESP-IDF, with optimization set to release, and delay changed to 100? No, in this case app run like it should - i don't get it. I supplied pio_build.zip that contains buildlog from PlatformIO and generated .elf file, maybe i missed something and those files help find so...

You can work around this by adding 'volatile' qualifier in two lines in components/spi_flash/cache_utils.c, around line 41: static volatile bool s_flash_op_can_start = false; static volatile bool s_flash_op_complete = false; Ok, it works for building in MSYS2, and Optimization level set to Release....

Thank you, i will try this later.
I looked in the cache_utils.c and i see that those variables are used in spinlocks - why from the beginning are not marked as volatile to avoid stuck, caused by compiler optimization ?

@kolban :
i'm not using Arduino framework at all, and the problem exist also for msys2+esp-idf not only Platformio.

@ESP_igrr :
problem reveal even on simple 02_blink code from esp-idf examples.

I'm from Poland and this is my first post, so Hello Everyone ! :) Thanks to rudi ;-) from this forum I have Nano32. I'm using Platformio and i've managed to modify package https://github.com/platformio/platform-espressif32, for successfull built application (in this example it is 02_blink), against ...