
Esp32 Debugging
This handles the full spectrum of ESP32 firmware debugging, from compilation errors to runtime panics. It walks you through Guru Meditation errors with a lookup table for common causes like StoreProhibited and stack overflows, explains how to interpret crash dumps, and covers I2C/SPI/UART communication failures with specific checklists. The skill includes ready-to-run commands for capturing build errors and monitoring serial output, plus practical fixes like adjusting task stack sizes and enabling heap poisoning configs. It's clearly written by someone who's spent time tracking down pointer bugs and I2C address mismatches at 2am. If you're building on ESP-IDF and something crashes, panics, or refuses to compile, start here.
- skills.sh installs
- 313
- GitHub stars
- 7
- last updated
- Aug 21, 2026
Install
$ npx -y skills add laurigates/mcu-tinkering-lab --skill esp32-debugging --agent claude-codeInstalls into .claude/skills of the current project.
Files
ESP32 Firmware Debugging Guide
When to Use This Skill
Apply this skill when the user:
- Encounters compilation errors in ESP-IDF projects
- Sees runtime panics or "Guru Meditation Error" messages
- Has memory-related crashes or stack overflows
- Experiences I2C/SPI/UART communication failures
- Needs help interpreting serial monitor output
$ARGUMENTS may contain error messages or context about the issue.
Debugging Process
Ask for Context First
If the error isn't clear from $ARGUMENTS, ask the user to provide:
- Full error message or panic output
- Which project they're building
- Recent code changes
Sponsors
Details
- Repository
- github.com/laurigates/mcu-tinkering-lab
- Category
- Debugging
- First seen
- Jun 3, 2026