While debugging a faulty RPi I had to find out what are the LED error codes. You might find these useful.
Rasbperry Pi 4
| Long flashes | Short flashes | Meaning |
|---|---|---|
| 0 | 3 | Generic failure to boot |
| 0 | 4 | start.elf not found |
| 0 | 7 | Kernel image not found |
| 0 | 8 | SDRAM failure |
| 0 | 9 | Insufficient SDRAM |
| 0 | 10 | In HALT state |
| 1 | 2 | SD card overcurrent detected |
| 2 | 1 | Partition not FAT |
| 2 | 2 | Failed to read from partition |
| 2 | 3 | Extended partition not FAT |
| 2 | 4 | File signature/hash mismatch – Pi 4 and Pi 5 |
| 3 | 1 | SPI EEPROM error – Pi 4 and Pi 5 |
| 3 | 2 | SPI EEPROM is write protected – Pi 4 and Pi 5 |
| 3 | 3 | I2C error – Pi 4 and Pi 5 |
| 3 | 4 | Secure-boot configuration is not valid |
| 4 | 3 | RP1 not found |
| 4 | 4 | Unsupported board type |
| 4 | 5 | Fatal firmware error |
| 4 | 6 | Power failure type A |
| 4 | 7 | Power failure type B |
If a Raspberry Pi fails to boot for some reason, or has to shut down, in many cases an LED will flash a specific number of times to indicate what happened. The LED will blink for a number of long flashes (0 or more), then produce short flashes, to indicate the exact status. In most cases, the pattern will repeat after a two-second gap.
- Green LED blinks in a regular four blink pattern, it can’t find bootcode (start.elf).
- Green LED blinks in an irregular pattern, booting has started.
- Green LED doesn’t blink, then the EEPROM code may be corrupted.
This is a destroyed Raspberry Pi 5. This is exactly the state that arrived from Berrybase, from Berlin with DHL. Berrybase did not answer. I kept the packaging as they arrived. Shame Berrybase ! Shame DHL !
More information on Raspberry Pi documentation page.
