Open FiSh3rWoLf opened 1 month ago
Thanks for the report, @FiSh3rWoLf, and for the pre-submission sleuthing.
Curious we've not seen this one before. I'll need to check if this is specific to Raspberry Pi 5, or if it also affects the Raspberry Pi 4 family.
Applications need to use the blconfig alias and not hardcoded the rmem node https://github.com/raspberrypi/rpi-eeprom/blob/master/rpi-eeprom-update#L117
What happened?
The embedded Raspberry Pi Imager doesn't read IMAGER_REPO_URL in bootloader EEPROM. Imager look for rmem0 but has rmem4 instead.
Version
1.8.5 (Default)
What host operating system were you using?
Windows
Host OS Version
23H2
Selected OS
Raspberry Pi Imager from HTTP Boot (downloaded https://fw-download-alias1.raspberrypi.com/net_install/boot.img on local server)
Which Raspberry Pi Device are you using?
Raspberry Pi 5
What kind of storage device are you using?
NVMe SSD via Third-party PCIe attachment
OS Customisation
Relevant log output