esp32-debugging

Diagnose ESP32 firmware compilation errors, runtime panics, and I2C/SPI/UART faults.

6|Updated May 18, 2025

Search Tags:#debugging #esp32 #i2c #compiler-errors #idf #runtime-panic

Ready to run

npx skills add https://github.com/laurigates/mcu-tinkering-lab --skill esp32-debugging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: esp32-debugging
Source: https://github.com/laurigates/mcu-tinkering-lab/tree/main/.claude/skills/esp32-debugging
Command: npx skills add https://github.com/laurigates/mcu-tinkering-lab --skill esp32-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured guidance for diagnosing ESP32 firmware issues, from compile errors to runtime panics and I/O problems.

Core Features & Use Cases

Compilation error analysis: Identify missing includes, undefined references, and type issues with concrete remedies.
Runtime panic analysis: Diagnose Guru Meditation errors, stack overflows, and memory problems.
Memory & I/O debugging: Tools and patterns to inspect heap, stack, and peripheral communications (I2C/SPI/UART).

Quick Start

Build with verbose output to surface errors, 2) Run serial monitor to capture logs, 3) Follow the debugging steps for a reported issue.

Frequently Asked Questions about esp32-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug ESP32 compilation errors in ESP-IDF projects?▼

ESP32 compilation errors often stem from missing includes, undefined references, or type mismatches. Build with verbose output to surface the exact error location, then check header paths, library linkage, and type declarations. The Skill identifies these patterns and provides concrete remedies for each error class.

What causes Guru Meditation errors on ESP32 and how do I fix them?▼

Guru Meditation errors indicate runtime panics from stack overflows, memory corruption, or illegal operations. Capture serial monitor output to locate the faulting instruction, inspect heap and stack usage, then apply targeted fixes. The Skill diagnoses panic codes and guides you through memory inspection tools.

How do I troubleshoot I2C, SPI, and UART communication failures on ESP32?▼

I/O faults stem from pin configuration, clock timing, protocol violations, or device responses. Enable verbose logging on the peripheral, decode serial output for protocol-level errors, and verify electrical connections and timing parameters. The Skill provides step-by-step diagnosis for each communication protocol.

Can I use ESP32 debugging techniques for stack overflow and memory crash diagnosis?▼

Yes. Stack overflows and memory crashes leave diagnostic traces in crash dumps and serial logs. The Skill covers memory layout inspection, heap fragmentation analysis, and stack depth profiling to isolate corruption sources and prevent recurrence.

What's the quickest way to start debugging an ESP32 firmware issue?▼

Build with verbose output to capture compilation details, run the serial monitor to log runtime behavior, then match observed errors against the Skill's debugging workflows. Each path provides command examples and root-cause identification steps for faster resolution.