Is it somehow possible to hide the cache access latency? For instance, I'd like to walk over a larger piece of data that is stored in ext. QSPI ROM/RAM and mapped via MMU/cache, and process that data. It could walk the data in cache line sizes (32 bytes). But every time there is a cache miss, things...

My idea was indeed to have 2 flash chips on different CS lines to be used by the MMU / Cache, not as explicit SPI storage via SPI commands. Thanks for confirming that this is not possible

I ran into a similar question .... Does the ESP32 MMU/Cache support multiple flash chips on different CS lines? For example have one flash on CS0 for Vaddr(0) area, one RAM for Vaddr(ram) area on CS1 and another flash chip on CS2 for Vaddr(1-3) area, or something like that? Is that possible or not? ...

I've tried the following modified example, compiled with the GCC 8 toolchain, running on ESP32 240 MHz CPU core. SPI Flash/RAM is 80 MHz QSPI, but it doesn't matter, as the code and data easily fits into the cache. The benchmark loops have been modified to do 4 independent instructions per loop, as ...

BTW, when in error or in doubt ... the cmake compiler tests can be knocked out.. by adding the following to the toolchain file (just as an example): set (CMAKE_C_COMPILER_ID "GNU") set (CMAKE_C_COMPILER_VERSION "7.3.1") set (CMAKE_C_COMPILER_FORCED TRUE) set (CMAKE_CXX_COMPILER_ID "GNU") set (CMAKE_...

I think the components/libraries should be all individual cmake projects, not just sub-targets of the main app project. Sometimes there are situations where one has to use different (and potentially conflicting compiler flags) for libraries, like some libraries requiring a certain optimization level...

Unsuccessful build: FreeRTOS-openocd.c.obj croutine.c.obj event_groups.c.obj list.c.obj port.c.obj queue.c.obj tasks.c.obj timers.c.obj xtensa_init.c.obj xtensa_intr.c.obj xtensa_overlay_os_hook.c.obj Successful build: FreeRTOS-openocd.c.obj croutine.c.obj event_groups.c.obj list.c.obj port.c.obj po...

Let's start with the first one esp-idf/esp32/libesp32.a(crosscore_int.c.obj):(.iram1.literal+0xc): undefined reference to `_frxt_setup_switch' xtensa-esp32-elf-nm esp-idf/freertos/libfreertos.a | grep _frxt_setup_switch U _frxt_setup_switch Others like xt_ints_off, xt_ints_on aren't present at all. ...

Yeah, I know that IDF links its stuff in a link group, so I'm also a bit surprised. But I think I've seen this sometime before, don't remember on which occasion though (sorry, not helpful I know). Linking CXX executable test.elf /usr/local/bin/cmake -E cmake_link_script CMakeFiles/test.elf.dir/link....

When setting up a build (i.e. running cmake for the first time) of a cmake project that links to some of my other libraries, on the first build I get this: Linking CXX executable test.elf esp-idf/esp32/libesp32.a(crosscore_int.c.obj):(.iram1.literal+0xc): undefined reference to `_frxt_setup_switch' ...