ESP32 IllegalInstruction: the CPU hit something that is not code

The CPU fetched an instruction it does not recognise. ESP-IDF's own guide lists a short set of causes, and one of them catches a lot of C++ code that compiled without a warning.

Guru Meditation Error: Core  0 panic'ed (IllegalInstruction). Exception was unhandled.
Memory dump at 0x400d25e0: 0000f01d 00000000 00000000

Backtrace: 0x400d25e3:0x3ffb5e40 0x4008a4a2:0x3ffb5e60

On RISC-V chips it is Illegal instruction.

The usual causes

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:

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: InstrFetchProhibited · Stack overflow · Cache disabled but cached memory region accessed · LoadProhibited. All ESP32 errors: the list. Messages and causes from ESP-IDF's panic handler and Espressif's Fatal Errors guide.

More