[Bug 2094834] Re: [FFe] Bump eeprom to support memory timings update in 16GB Pi 5
Launchpad Bug Tracker
2094834 at bugs.launchpad.net
Wed Mar 19 22:37:09 UTC 2025
This bug was fixed in the package rpi-eeprom - 27.5-0ubuntu1
---------------
rpi-eeprom (27.5-0ubuntu1) plucky; urgency=medium
* New upstream release (LP: #2094834)
* Fixes compatibility with Pi 5 16GB memory timings
* d/control: Bump standards version to 4.7.0
* d/control: Remove references to libraspberrypi-bin (oldlib)
* d/rpi-eeprom-firmware.install: Use non-aliased location (/usr/lib)
rpi-eeprom (27.5-1) bookworm; urgency=medium
[ Tim Gover ]
* image: Update 2711 plus 2712 images and enable boot-menu on 2711
* pieeprom-2025-03-03: 2712: Fix bootloader pull configuration on
BCM2712D0 (latest)
* pieeprom-2025-03-10: 2712: Add [boot_partition] filter plus SDRAM init
fixes (latest)
[ Rasmus Villemoes ]
* rpi-eeprom-digest: support specifying keys via PKCS#11 URI
rpi-eeprom (27.4-1) bookworm; urgency=medium
* pieeprom-2025-02-12: 2712: Promote to default release
* license: Update wildcards for firmware
* firmware: 2712: Fixup commit to promote 2025-02-12 release
rpi-eeprom (27.3-1) bookworm; urgency=medium
* gpb: Use pios/bookworm branch
rpi-eeprom (27.2-1) bookworm; urgency=medium
* pieeprom-2025-02-11-2711: Promote to default release
* pieeprom-2025-02-12: 2712: Promote to default release
rpi-eeprom (27.1-1) bookworm; urgency=medium
[ Tim Gover ]
* imager: 2712: Move imager release to 2025-01-22
* pieeprom-2025-01-27: 2712: Add PARTITION_WALK option (latest)
* pieeprom-2025-02-11: 2712: CM5 no-wifi stability improvements (latest)
* pieeprom-2025-02-11: 2711: Walk partitions to delete recovery.bin
(latest)
* pieeprom-2025-02-12: 2712: Fixup change to disable 3.7V WiFi power on
CM5 no-wifi (latest)
[ Serge Schneider ]
* salsa-ci: minimise yaml file and set variables on group level instead
rpi-eeprom (27.0-1) bookworm; urgency=medium
[ Serge Schneider ]
* salsa-ci: remove default runner tag
* salsa-ci: enable aptly
* salsa-ci: set GIT_STRATEGY to 'clone'
* salsa-ci: fix minor typo
* salsa-ci: Add rpi jobs
[ Tim Gover ]
* scripts: Failover to /usr/lib before /lib if FIRMWARE_ROOT is not set
* test: Update test script
* pieeprom-2025-01-22: 2712: Add DT property for hash of signed boot
image (latest)
* 2025-01-22: 2712: Promote 2025-01-22 to default release (default)
rpi-eeprom (26.9-1) bookworm; urgency=medium
[ Tim Gover ]
* pieeprom-2025-01-13: 2712: Improved SDRAM refresh timings for Pi5 -
16GB (latest)
* pieeprom-2025-01-14: 2712: Add set_reboot_order API (latest)
[ Serge Schneider ]
* Add salsa-ci.yml
[ andrum993 ]
* 2712 release-notes.md: correct name of new config parameter
rpi-eeprom (26.8-2) bookworm; urgency=medium
* Move files from /lib to /usr/lib
* Bump standards version to 4.6.2
* Bump compat version to 12
* Update lintian-overrides
rpi-eeprom (26.8-1) bookworm; urgency=medium
[ Tim Gover ]
* pieeprom-2024-12-19: 2712: Disable PWM fan at shutdown (POWER_OFF_ON_HALT=0) (latest)
* pieeprom-2025-01-06: 2712: Stop the fan after fan-probe (latest)
* pieeprom-2025-01-07: 2712: Fixup M.2 HAT+ detection (latest)
* pieeprom-2025-01-08: 2712: Update SDRAM timings for BCM2712D0 products (latest)
rpi-eeprom (26.7-1) bookworm; urgency=medium
[ Tim Gover ]
* rpi-eeprom-update: Add retries and verification to flashrom stage
* rpi-eeprom-config: Increase default timeouts
* rpi-eeprom-config: Remove misleading message about cancelling updates
* rpi-eeprom-update: Update user prompt to indicate how to install update immediately
* pieeprom-2024-12-15: 2712: Add net install to boot menu (latest)
[ Phil Elwell ]
* bug_report template: Be more precise about the UART pins
rpi-eeprom (26.6-1) bookworm; urgency=medium
[ Tim Gover ]
* imager: remove unused boot-conf-default.txt files
* image: 2712: Update config for POWER_OFF_ON_HALT and NET_INSTALL_AT_POWER_ON
* imager: Update 2712 imager release to 2024-11-12
* pieeprom-2024-11-27: 2712: rp1fw: Add FIFO_STATE & DRAIN_TX, fix CAN_ADD_PROGRAM (latest)
* pieeprom-2024-12-07: 2711: 2712: Enable NUMA by default (latest)
rpi-eeprom (26.5-1) bookworm; urgency=medium
[ Tim Gover ]
* pieeprom: 2024-11-12-2712: Promote 2024-11-12 to default release (default)
rpi-eeprom (26.4-1) bookworm; urgency=medium
[ Rasmus Villemoes ]
* rpi-eeprom-digest: honour SOURCE_DATE_EPOCH
[ Tim Gover ]
* 2712: release-notes: Update note for min supported version
* pieeprom: 2024-11-12-2712: Enable initial_turbo=60 by default (latest)
* imager: gitignore: Ignore the imager build directories
-- Dave Jones <dave.jones at canonical.com> Wed, 19 Mar 2025 11:06:58
+0000
** Changed in: rpi-eeprom (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rpi-eeprom in Ubuntu.
https://bugs.launchpad.net/bugs/2094834
Title:
[FFe] Bump eeprom to support memory timings update in 16GB Pi 5
Status in rpi-eeprom package in Ubuntu:
Fix Released
Status in rpi-eeprom source package in Noble:
Confirmed
Status in rpi-eeprom source package in Oracular:
Confirmed
Bug description:
[ Impact ]
The current version of rpi-eeprom in Ubuntu noble cannot be used to
flash the boot EEPROM on the D0 models of the Pi 5. While it won't
automatically attempt to do so (because the version shipped on such
boards is later than ours), if anyone attempts to recover their boot
EEPROM on this board using Ubuntu they will appear to brick the board
(it can be recovered using a rescue SD card, but this is still far
from ideal / obvious).
The version in oracular is slightly more up to date but still has
issues (is unable to drive) the official DSI display. The version in
plucky is more up to date still, and fixes the DSI display, but is not
compatible with the more recent 16GB memory version of the Pi 5.
All the aforementioned issues are fixed in the current variant of rpi-
eeprom upstream. This should be upload to plucky, then SRU'd to
oracular (if still in support at that point) and noble.
[ Test Plan ]
WARNING:
This test plan should only be carried out by those comfortable recovering from flashing a bad rom. The purpose of this test plan is to uncover boot issues. If you are uncomfortable following the bootloader recovery process [1], please do not attempt the test plan.
[1]: https://www.raspberrypi.com/documentation/computers/raspberry-
pi.html#eeprom-boot-flow
NOTE:
The test plan may require adjustment of the BOOT_ORDER value stored in the EEPROM configuration, via rpi-eeprom-config. Testers are strongly advised to leave 0x1 (SD card) somewhere in the modified boot order while testing, to allow for easier recovery in the event of issues.
To cover the upgrade path and boot operation on all relevant models,
the following test plan is proposed for all proposed $series:
* Flash the Ubuntu Server for Raspberry Pi pre-installed image for the relevant series to $media
* Boot the card and wait for cloud-init to complete
* Login
* sudo apt update
* sudo apt install -t $series-proposed rpi-eeprom
* sudo rpi-eeprom-update
* This will report the current bootloader version installed on the board's EEPROM and the latest available
* If EEPROM is out of date: sudo rpi-eeprom-update -a
* If EEPROM is not out of date, force the update:
- For Pi/CM 5: sudo rpi-eeprom-update /lib/firmware/raspberrypi/bootloader-2712/default/pieeprom-2025-01-13.bin
* sudo reboot
* Ensure subsequent boot completes successfully
Repeat this procedure (including freshly flashed image) for the
following models:
* Pi 5 2GB/4GB/8GB/16GB (ensure both C1 and D0 steppings are tested)
* CM5
Repeat this procedure for the following boot $media:
* SD card (where applicable)
* USB-attached SSD (all models)
* NVMe (Pi 5 only)
[ Regression Potential ]
Bumping rpi-eeprom is always potentially risky, given it's flashed to
the board's EEPROM with all the attendant risks running the gamut all
the way up to "bricked boards". In mitigation, the version being
proposed has been used in (the much larger installed base of) RaspiOS
for over a month, and the test plan attempts to cover all affected
boards, with relevant boot media.
With regard to the affected models: this boot firmware is only used on
Pi models from the 4 onwards (including the compute module variants).
However, in the intended version there is only a new bootloader for
the 2712 (Pi 5 variants), hence the Pi 4 (and CM4) can be safely
excluded from testing.
[ Original Description ]
Per commit https://github.com/raspberrypi/rpi-
eeprom/commit/62292b43ad163f49efb4a76e3c2df557bd0df537 in the upstream
repo, rpi-eeprom introduces new timings to improve performance on the
16GB Pi 5 model.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2094834/+subscriptions
More information about the foundations-bugs
mailing list