-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: Not reading EEPROM content in Bootable Imager Image #894
Comments
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 |
I can confirm that I'm hitting the same issue.
Would be glad to hear about a projected timeline for a resolution. Please see the following context:
Boot UART Trace:
Respective network flow observed via Wireshark:
|
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
The text was updated successfully, but these errors were encountered: