[Bug 2094834] Re: [SRU] Bump eeprom to support memory timings update in 16GB Pi 5

[Timo Aaltonen]

Hello Dave, or anyone else affected,

Accepted rpi-eeprom into noble-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/rpi-
eeprom/28.14-0ubuntu0.24.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: rpi-eeprom (Ubuntu Noble)
       Status: Confirmed => Fix Committed

** Tags added: verification-needed-noble

-- 
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:
  [SRU] 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:
  Fix Committed
Status in rpi-eeprom source package in Oracular:
  Won't Fix
Status in rpi-eeprom source package in Questing:
  Fix Released

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