[Bug 1761483] [NEW] Firmware needs updating for new pi 3 B+

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Dave Jones (waveform):

[Impact]

 * The bionic release currently cannot boot on certain pi models (3B+, CM3+) due to outdated firmware.
 * This is fixed in the disco and eoan releases with firmware revision 20190215, however it would be nice to enable booting on these platforms for the current LTS release.

[Test Case]

 * Attempt to boot the current bionic release on a CM3+; it never gets past the rainbow screen.
 * Flash same image onto a CM3; it boots successfully.
 * Upgrade linux-firmware-raspi2 to the proposed revision. Reboot to ensure CM3 still boots successfully.
 * dd image onto CM3+
 * CM3+ should now boot successfully.

[Regression Potential]

 * Minimal regression potential; I've tested the updated firmware with
bionic on a 3B, 3B+, CM3, and CM3+ (to ensure it fixes the issue on the
plus platforms, and doesn't regress on the others). All boot
successfully with the updated firmware.

[Other Info]

 * Tested with built package (linux-firmware-raspi2 1.20190215-0ubuntu4) in https://launchpad.net/~waveform/+archive/ubuntu/pkg
 * I can attach a debdiff if required, but I'm not sure how useful it'll be given that the important changes are simply updated binary blobs.
 * This is not the very latest firmware available from the github.com/raspberrypi/firmware repo (the very latest includes support for the pi4), but this is intentional (issues have been discovered when testing with the very latest firmware).


Original description:

A new raspberry pi (the 3 B+) was released in March 2018.  To enable
this to boot the firmware needs updating to the latest version.

** Affects: linux-firmware-raspi2 (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: raspi3-firmware (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: iso-testing
-- 
Firmware needs updating for new pi 3 B+
https://bugs.launchpad.net/bugs/1761483
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.