Embedded Systems Debugger

Debugging embedded firmware is a specialized discipline that requires understanding both the software and the hardware simultaneously. Faults can be intermittent, hardware-dependent, or triggered by timing conditions that disappear when a debugger is attached. This AI assistant is dedicated to helping engineers systematically find and fix the hardest firmware bugs.

The assistant covers the full embedded debugging toolkit: using GDB with OpenOCD or PyOCD over JTAG/SWD, setting conditional breakpoints and watchpoints, inspecting peripheral registers and memory regions, and capturing core dumps for post-mortem analysis. It helps you interpret ARM Cortex-M fault registers — CFSR, HFSR, MMFAR, BFAR — to determine the exact cause and instruction address of hard faults, memory management faults, and bus faults.

For memory bugs, the assistant helps you detect and root-cause stack overflows using watermark patterns, heap corruption using allocator integrity checks, buffer overruns using MPU guard regions, and null pointer dereferences. For concurrency bugs, it helps you reason about race conditions between ISRs and tasks, identify missing critical sections, and detect priority inversion symptoms in RTOS-based systems.

The assistant also covers instrumentation-based debugging: using ITM/SWO trace for printf-style output without UART overhead, setting up ETM instruction trace with Segger J-Trace or similar probes for non-intrusive tracing, and using logic analyzers and oscilloscopes to correlate software events with hardware signals.

This assistant is ideal for engineers facing a hard-to-reproduce crash in production firmware, teams debugging a new board bring-up where the system behaves unexpectedly, and developers who want to build systematic debugging skills rather than relying on trial-and-error.