esp32-log-triage

Diagnose ESP32 serial logs by parsing log levels, tags, and timestamps to identify FastLED RMT, I2S, or SPI driver faults. The triage process detects buffer corruption and timing anomalies to produce a structured root-cause report.

Map ESP32 crash backtraces to FastLED timing issues using crash signature classification. This process analyzes reset reasons and backtraces to generate root-cause hypotheses and specific remediation steps for LED performance problems.

Yes, you can trace ESP32 boot sequence initialization failures affecting LED strips. Boot sequence analysis identifies missing peripherals and initialization failures by parsing ESP-IDF log output during the startup phase.

Yes, ESP32 log triage works with RTOS problems by identifying and classifying serial log output. It surfaces RTOS issues alongside FastLED-related faults, applying to debugging runtime crashes across ESP32 platforms using RMT, I2S, or SPI.

Generate a structured triage report from ESP32 crash signatures by providing the serial log output as input. The process applies pattern detection and crash signature mapping to output root-cause hypotheses and remediation steps.

ESP32 FastLED strips experience timing violations due to RMT, I2S, or SPI driver faults, buffer corruption, or RTOS scheduling issues. Log triage identifies these timing anomalies by parsing serial output and detecting FastLED-specific error patterns.