Analyze firmware crash output, decode stack traces, and diagnose embedded system failures.
$ARGUMENTS
What This Skill Does
- Crash Analysis: Parse panic handlers, guru meditation errors, hard faults, watchdog resets
- Stack Trace Decoding: Decode raw addresses to function names using ELF binaries
- Register Dump Interpretation: Analyze CPU register state at crash time
- Root Cause Identification: Correlate crash data with source code to find the bug
- Fix Recommendations: Suggest specific code changes to prevent the crash
Supported Platforms
| Platform |
Crash Types |
| ESP32 (all variants) |
Guru Meditation, LoadProhibited, StoreProhibited, InstrFetchProhibited, watchdog reset, brownout, cache errors |
| ARM Cortex-M (STM32, Teensy, nRF) |
HardFault, MemManage, BusFault, UsageFault, watchdog reset |
| AVR (Arduino Uno/Mega) |
Stack overflow (silent corruption), watchdog reset, undefined opcode |
| RISC-V (ESP32-C3/C6/H2) |
Illegal instruction, load/store fault, breakpoint |
How To Use
With crash output
/embedded-debug
Guru Meditation Error: Core 0 panic'ed (LoadProhibited). Exception was unhandled.
Core 0 register dump:
PC : 0x400d1234 PS : 0x00060030 A0 : 0x800d5678
...
With a description
/embedded-debug Device reboots every 30 seconds, serial shows "rst:0x3 (SW_RESET)"
With a core dump
/embedded-debug Analyze the core dump from the last crash
What You'll Get
- Decoded stack trace with source file and line numbers
- Explanation of the crash type and what triggered it
- Identification of the faulty code path
- Specific fix recommendations with code examples
- Prevention strategies (stack size tuning, watchdog config, null checks)
1---2name: embedded-debug3description: Firmware crash analysis, stack trace decoder, and register dump interpreter for ESP32/ARM/AVR platforms. Use when debugging device crashes, panics, guru meditation errors, hard faults, or analyzing core dumps.4---5
6Analyze firmware crash output, decode stack traces, and diagnose embedded system failures.
7
8$ARGUMENTS
9
10## What This Skill Does
11
121. **Crash Analysis**: Parse panic handlers, guru meditation errors, hard faults, watchdog resets
132. **Stack Trace Decoding**: Decode raw addresses to function names using ELF binaries
143. **Register Dump Interpretation**: Analyze CPU register state at crash time
154. **Root Cause Identification**: Correlate crash data with source code to find the bug
165. **Fix Recommendations**: Suggest specific code changes to prevent the crash
17
18## Supported Platforms
19
20| Platform | Crash Types |
21|----------|-------------|
22| ESP32 (all variants) | Guru Meditation, LoadProhibited, StoreProhibited, InstrFetchProhibited, watchdog reset, brownout, cache errors |
23| ARM Cortex-M (STM32, Teensy, nRF) | HardFault, MemManage, BusFault, UsageFault, watchdog reset |
24| AVR (Arduino Uno/Mega) | Stack overflow (silent corruption), watchdog reset, undefined opcode |
25| RISC-V (ESP32-C3/C6/H2) | Illegal instruction, load/store fault, breakpoint |
26
27## How To Use
28
29### With crash output
30```
31/embedded-debug
32Guru Meditation Error: Core 0 panic'ed (LoadProhibited). Exception was unhandled.
33Core 0 register dump:
34PC : 0x400d1234 PS : 0x00060030 A0 : 0x800d5678
35...
36```
37
38### With a description
39```
40/embedded-debug Device reboots every 30 seconds, serial shows "rst:0x3 (SW_RESET)"
41```
42
43### With a core dump
44```
45/embedded-debug Analyze the core dump from the last crash
46```
47
48## What You'll Get
49
50- Decoded stack trace with source file and line numbers
51- Explanation of the crash type and what triggered it
52- Identification of the faulty code path
53- Specific fix recommendations with code examples
54- Prevention strategies (stack size tuning, watchdog config, null checks)
majiayu000