rpi-hardware-troubleshooting

Diagnose Raspberry Pi hardware failures through interactive top-down elimination across all models.

Updated May 29, 2026
One-click install
npx skills add https://github.com/dpetzel/rpi-hardware-troubleshooting-skill --skill rpi-hardware-troubleshooting-dpetzel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rpi-hardware-troubleshooting
Source: https://github.com/dpetzel/rpi-hardware-troubleshooting-skill
Command: npx skills add https://github.com/dpetzel/rpi-hardware-troubleshooting-skill --skill rpi-hardware-troubleshooting-dpetzel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Diagnosing a dead or malfunctioning Raspberry Pi is hard because symptoms like a missing green LED or a rainbow screen can stem from power, storage, EEPROM, or component-level faults. This Skill guides an interactive diagnostic session that eliminates the largest failure categories first, so users avoid wasted tangents and reach a root cause systematically. ## Core Features & Use Cases - Top-Down Elimination Workflow: Works through power, boot signs, storage, core system, peripherals, and the software boundary in order, asking one bisecting question at a time. - Board-Level Reference Data: Fetches test points, voltage maps, PMIC data, and board photos from rpi.dpetzel.info via a sitemap helper script, plus local references for LED codes, boot sequences, and model-specific failure modes (Pi 3 PMIC, LAN9514, Pi 5 rpiboot recovery). - Session Logging & Equipment Awareness: Maintains a resumable rpi-troubleshoot-log.md checklist and tailors measurement suggestions to the user's available tools listed in equipment.md. - Use Case: A user's Pi 3B+ shows a red LED but never boots. The Skill reads their existing repair notes, walks them through measuring PP8 and PP9 with exact probe locations, and identifies a shorted MxL7704 PMIC as the cause. ## Quick Start Ask the agent to help diagnose your Raspberry Pi that won't boot, describing the model and exactly what LED or display behavior you observe.

Frequently Asked Questions about rpi-hardware-troubleshooting

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

FAQPage Schema
How do I diagnose a Raspberry Pi that won't boot?

Start with a top-down elimination approach: confirm power (red LED steady), then boot signs (green LED activity), then storage media, then peripherals. The Skill asks one bisecting question at a time and maps symptoms like blink patterns or rainbow screens to specific boot stages.

What do Raspberry Pi LED blink codes mean?

Green LED blink bursts indicate bootrom errors: 1 blink means start.elf not found, 3 blinks means kernel not found, 8 blinks means SDRAM failure. Pi 3 boards have no onboard EEPROM, so no SD card means no blink codes at all, just a steady red LED.

Why is my Raspberry Pi 3B+ completely dead with only a red LED?

Common causes include a destroyed MxL7704 PMIC (often from shorting 5V to a 3.3V GPIO pin), a dead 19.2MHz crystal, or a tripped polyfuse. Measure PP8 for 3.3V and check resistance from the 3.3V rail to ground to identify a shorted PMIC.

Can I recover a Raspberry Pi 5 with corrupted EEPROM?

Yes, use rpiboot over USB: disconnect power, hold the power button, connect USB-C to a host computer, then run rpiboot with the recovery5 directory to reflash the bootloader EEPROM. Successful USB enumeration also confirms the SoC itself is alive.

Does this troubleshooting approach require special equipment?

No, it adapts to your available tools via an optional equipment.md file. With only a basic multimeter it sticks to DC voltage and continuity checks; with a bench PSU, oscilloscope, or hot air station it suggests current-limited power tests, waveform checks, or component-level rework.

Why did my Pi 4 stop booting when a USB hub or KVM is connected?

Some KVMs and hubs backfeed voltage that stalls the PMIC during power sequencing, leaving the board drawing only about 19mA with no green LED. Removing the device restores normal boot; connect the hub after boot or use one that does not backfeed.