Closed ohthehugemanatee closed 8 months ago
Update: I tried updating the bootloader in smaller steps with some success
At that point I started backtracking one release at a time, and any version newer than 2022-04-26 fails to the red screen with 4 long /5 short LED state.
Here's the HDMI diagnostic screen from the latest version I can get into (2022-04-26):
But - from there, the automatic bootloader update seems to work fine. Booting into a fresh bullseye64 image, after the usual automated reboots, I get
$ sudo rpi-eeprom-update -d -a
BOOTLOADER: up to date
CURRENT: Wed Jan 11 17:40:52 UTC 2023 (1673458852)
LATEST: Wed Jan 11 17:40:52 UTC 2023 (1673458852)
RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
Use raspi-config to change the release.
VL805_FW: Dedicated VL805 EEPROM
VL805: up to date
CURRENT:
LATEST: 000138c0
I'll amend the OP: this is clearly a problem with the specific update path, and an intermediate update to 2022-04-26 seems sufficient to resolve.
Describe the bug
Brand new rpi4 8GB with bootloader "Mon Jul 15 12:59:55 UTC 2019 (1563195595)" fails to boot if recovery.bin of the latest "Wed Jan 11 17:40:52 UTC 2023 (1673458852)" EEPROM is present. This happens with a raspbian image, or even with a "bootloader recovery" image. Discovered it when the device failed on the second boot of a fresh bullseye64 image... rpi-eeprom-update.service had automatically downloaded a recovery.bin. Device boots successfully if I remove the file. Unfortunately 1563195595 is before we got the HDMI diagnostic screen on boot, so red screen and 4 long / 5 short LED code is all I have. (update: see first comment)
See discussion on the forum for detail.
Steps to reproduce the behaviour
Device (s)
Raspberry Pi 4 Mod. B
Bootloader configuration.
System
Bootloader logs
I don't have a UART / USB device handy.
USB boot
N/A
NVMe boot
N/A
Network (TFTP boot)
N/A