Embedded Systems Error Codes

The CPU trapped on a bus access error when reading or writing memory or peripherals.

A debug monitor exception occurred, typically in debug builds or when a debug event triggers an exception.

The firmware attempted to free a heap pointer more than once, corrupting allocator state.

The memory allocator detected corrupted heap metadata, often from out-of-bounds writes or invalid frees.

A dynamic memory allocation failed because the heap is exhausted or fragmented.

A Cortex-M memory protection fault occurred due to an invalid memory access or region violation.

A non-maskable interrupt occurred, often indicating a critical hardware or safety event.

PendSV is commonly used for context switching; being reported as a fault usually indicates an exception handling or stack issue.

A supervisor call handler was invoked; in RTOS systems this can be part of normal operation or indicate a fault if unexpected.

The CPU detected an illegal instruction, undefined state, or invalid execution condition.

A runtime safety check triggered and halted or reset the system.

The system reset because supply voltage dropped below a safe threshold.

A firmware or configuration write to flash storage did not complete successfully.

An embedded runtime hit a fatal exception and reported a panic-style diagnostic.

A Cortex-M style fault handler was triggered due to an invalid memory or instruction condition.

A peripheral bus operation failed due to signaling or device state issues.

The CPU attempted to execute an invalid instruction and trapped into a fault state.

A required memory allocation failed due to exhausted heap or fragmentation.