
Embedded Debug Analyzer: Hardware-Firmware Integration Troubleshooting
Diagnose embedded firmware crashes and hardware integration bugs systematically
What You Can Do
You can analyze firmware crashes, serial logs, and hardware-firmware integration issues using structured debugging techniques. The skill guides you through stack trace interpretation, register analysis, and hardware signal tracing to pinpoint root causes. You'll get actionable debug paths and verification checklists for validating fixes before deployment.
Features
Extract timestamps, debug levels, error messages, and anomaly patterns from raw device logs
Interpret crash dumps, resolve symbols, map addresses to source code, and identify memory corruption
Diagnose peripheral register states, interrupt configuration, and hardware initialization sequence
Correlate firmware events with physical signals (GPIO, SPI, I2C, UART) to isolate integration points
Narrow scope from symptoms to specific driver, firmware module, or hardware interaction systematically
Generate targeted test cases to confirm fixes without regression or masking deeper issues
Walk through hardware-firmware interface validation with reproducible, step-by-step tests
Produce documentation with evidence, reproduction steps, register dumps, and diagnostic timeline
Example Output
Stack Trace Analysis Example:
Crash at 0x08001234 (task.c:115)
PC=0x08001234 [xTaskScheduler]
LR=0x08002AB0 [vTaskDelay]
SP=0x20001000
R0=0xDEADBEEF (uninitialized pointer) ← ROOT CAUSE
Stack corruption detected: 0xFFFFFFFF at frame base
Diagnosis: Null pointer dereference in interrupt handler → buffer overflow → stack corruption → hardfault
Fix: Add null-check guard before pointer dereference in ISR
Verify: Unit test for ISR with null input, regression test full interrupt flow
Serial Log Anomaly Detection:
[00:01:234] INIT: System starting ✓
[00:02:567] I2C: Timeout on slave 0x68 ← FIRST SYMPTOM
[00:02:590] ERROR: Sensor read failed
[00:03:012] CRASH: Hardfault, watchdog reset ← CONSEQUENCE
Pattern: I2C timeout precedes crash by 400ms
Correlation: Firmware does not timeout gracefully; interrupt handler hangs
Root cause hypothesis: I2C slave not responding → ISR blocks → watchdog expires
Test plan: Mock unresponsive I2C slave, verify timeout recovery
What's Included
- SKILL.md: Full embedded debugging methodology and decision tree
- Serial log parsing templates: Structured approach to extracting signals from raw logs
- Stack trace analysis worksheets: Address-to-source mapping, register interpretation guides
- Hardware integration checklists: SPI/I2C/UART/GPIO verification procedures
- Root cause decision tree: Systematic narrowing from symptom to module
- Verification test templates: Test cases for fix validation and regression prevention
- Register state analyzer: Peripheral register interpretation reference
- Reproduction recipe builder: Step-by-step format for capturing and documenting bugs
Who It's For
- Embedded systems engineers debugging firmware integration failures and hardware-firmware boundaries
- Firmware developers troubleshooting peripheral communication issues and boot failures
- Embedded QA engineers investigating sporadic hardware-related test failures
- Hardware engineers validating firmware implementations and protocol compliance
- IoT/consumer electronics teams performing field-issue root cause analysis and triage
Best For
- Unexpected firmware crashes or resets — Diagnose hardfaults, watchdog triggers, and system reboots
- Hardware peripheral communication failures — Debug I2C, SPI, UART, CAN timeouts and corruption
- Boot failures or initialization issues — Trace startup sequence and identify failing hardware setup steps
- Intermittent integration bugs — Correlate timing-sensitive hardware-firmware interactions
- Field-reported issues — Perform structured root cause analysis with limited reproduction data







