ESP32 "Cache disabled but cached memory region accessed"
While the ESP32 writes or erases its flash, code and constants in flash cannot be read. An interrupt that fires then and touches flash ends in this panic.
Guru Meditation Error: Core 0 panic'ed (Cache error). Cache disabled but cached memory region accessed
Newer chips can print a more specific reason in place of the second line, with the address that was accessed.
What it means
From Espressif's Fatal Errors guide: when ESP-IDF reads, writes, erases or maps flash, it turns the flash cache off. Tasks are suspended and interrupt handlers that are not registered with ESP_INTR_FLAG_IRAM are disabled. An IRAM interrupt handler that runs during that time must have all its code and data in internal RAM.
The usual causes
- An ISR, or a function it calls, without
IRAM_ATTR. Every function on the ISR's path needs it. - Constant data in flash read from the ISR: a lookup table or a string. Mark it
DRAM_ATTR. - Arduino:
attachInterruptwith a handler not markedIRAM_ATTR, running while the sketch writes to flash (Preferences, SPIFFS, LittleFS, OTA). - Logging from the ISR with a normal
ESP_LOGx: its format strings are in flash. UseESP_DRAM_LOGx, or better, no logging in interrupts.
Find the line
The Backtrace: line is a list of PC:SP pairs, innermost call first. To turn the addresses into functions and lines you need the ELF of exactly the build that crashed:
- ESP-IDF:
idf.py monitordecodes it as it prints. For a backtrace you copied,xtensa-esp32-elf-addr2line -pfiaC -e build/app.elf 0x400d1d4b 0x400d1e59(riscv32-esp-elf-addr2lineon the C3, C6 and other RISC-V chips). - Arduino: the ELF is in the sketch's build folder (Sketch → Export Compiled Binary, or the path in the verbose build output).
- In the browser: paste the crash and drop the ELF into the free ESP32 exception decoder. Nothing is uploaded.
When it happens in the field
On your desk the crash prints to the serial monitor. On a device in someone else's building it prints to a port nobody is reading, the chip restarts, and all you hear is that it "sometimes hangs". Pinscope keeps the panic reason and backtrace across the restart, sends them on the next connection and decodes them with the ELF of the build that crashed, so you get the function and line without anyone at the device. Free for three devices. How crash reporting from the field works.
Related errors: Interrupt wdt timeout · IllegalInstruction · Task watchdog got triggered · rst:0x… reset reasons. All ESP32 errors: the list. Messages and causes from ESP-IDF's panic handler and Espressif's Fatal Errors guide.
More
- Remote access to an ESP32 without TLS: what it measured and what it costs
- Reaching an ESP32 web server from outside its network
- Updating ESP32 firmware over the internet, with rollback
- Guru Meditation Error: decoding the backtrace, and crashes from the field
- Remote logging: ESP_LOG without a serial cable
- Heap and stack monitoring in the field
- An ESP32 behind CGNAT, 4G or Starlink
- TLS memory usage on the ESP32, and how to reduce it
- Sharing an ESP32 sensor page with anyone, without port forwarding
- ArduinoOTA over the internet, with a rollback
- ESP32 remote access compared: port forwarding, ngrok, Cloudflare Tunnel, Tailscale
- esp_http_server slow? The 250 ms delay and the fix
- Before the first ESP32 ships: a field support checklist
- ESP32 exception decoder: a Guru Meditation backtrace to lines, in the browser