Parse crash outputs and decode stack traces from ELF binaries.
npx skills add https://github.com/FastLED/FastLED --skill embedded-debug
Please help me install this Agent Skill. Skill: embedded-debug Source: https://github.com/FastLED/FastLED/tree/main/.claude/skills/embedded-debug Command: npx skills add https://github.com/FastLED/FastLED --skill embedded-debug
Diagnosing firmware crashes on embedded devices can be time-consuming. This skill parses crash outputs, decodes stack traces, and interprets register dumps to accelerate fault localization and remediation.
Provide the crash output or a description of the issue to start analyzing the fault.
High-intent search queries and answers about installing and using this skill.
To decode an ESP32 guru meditation error, you need the crash output and the corresponding ELF binary. This skill parses the panic handler logs, maps raw stack trace addresses to function names using the ELF file, and identifies the exact faulty code path.
Decoding ARM Cortex-M hard faults requires the raw crash output, a CPU register dump, and the compiled ELF binary. The skill translates the register states and maps stack addresses against the ELF to pinpoint the faulty instructions causing the hard fault.
Yes, you can analyze a core dump to find the root cause of a firmware panic. By correlating the crash data and register dump with the source code via the ELF binary, the skill provides concrete remediation steps to prevent reoccurrence.
Yes, decoding embedded crashes works with AVR platforms, ESP32, and ARM Cortex-M devices. The skill handles watchdog resets and hard faults by interpreting CPU register dumps to identify memory corruption or faulty instructions.
An ELF binary is required to analyze a firmware stack trace because it contains the build IDs and debug symbols needed for address mapping. The skill uses the ELF to translate raw memory addresses from the crash dump into exact function names.
The best way to diagnose intermittent ESP32 panics is to capture the crash output and register dump from the field device, then use this skill to correlate the stack trace with your source code. It provides a reproducible workflow to guide firmware fixes.
multicamAnalyze core dumps with gdb to diagnose early startup crashes and segfaults.
zhinkgitBuild CMake-based arm-none-eabi GCC projects and report ELF sizes in JSON.
LeoKemp223Monitor and analyze serial port logs from embedded systems using OpenOCD.
lexlerDefine Domain, Application, and Adapter boundaries with ports and adapters.
