STICKY: USB-MSD boot EEPROM fourth update - 2020-06-15

[timg236]

This is BETA software and the intended audience is people who are already familiar with bootloader/firmware updates and the risks involved

The EEPROM image for the bootloader has been updated in Github and APT.

For convenience, I've created a Github release for an EEPROM rescue image for this https://github.com/raspberrypi/rpi-eepr ... eleases.md so that the EEPROM image can easily be updated via the Raspberry Pi Imager custom image route.

Please try to keep the discussion relevant to USB mass storage boot or new bootloader features (SELF_UPDATE, NETCONSOLE etc) and not other firmware issues (i.e. things that happen before the rainbow splash screen) otherwise, important bug reports might get lost in the noise.

Release notes: -

• Increase the default power off delay to 500ms following more interop testing.
• Make the USB port power off time configurable via the USB_MSD_PWR_OFF_TIME config. The range may be set between 250 and 1000ms. Zero means no port power off.
• Fix some issues in XHCI endpoint configuration where the code was wrong but does not fail with the current VL805 FW.

[hippy]

Does this thread refer to the 'pieeprom-2020-06-15.bin' image or is there a 'pieeprom-2020-06-16.bin' image ?

[itzwolf]

I don't see a 2020-06-16 release, so I presume it is for 2020-06-15.

[re-zero246]

According to https://github.com/raspberrypi/rpi-eepr ... e-notes.md it looks like the release notes for 2020-06-15.

[fruitoftheloom]

I don't see a 2020-06-16 release, so I presume it is for 2020-06-15.

Would appear so: https://github.com/raspberrypi/rpi-eepr ... 6.15-137ad

[basti274]

hi,

when i

sudo rpi-eeprom-update -d -f /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2020-06-15.bin

the pi prompt me to reboot. after reboot its still the old bootloader from April. how can i fix this?

thanks in advance

[re-zero246]

OK, so I thought that I was running the 2020.06.15 from yesterday or the day before when I was trying to boot from a USB drive when infact I had 2020.06.03. I updated to the 2020.06.15, rebooted and it would give me the black screen with the flashing cursor in the upper left hand corner. Long story short, I had to reload the OS and when I did, 2020.06.15 was the bootloader that was presently flashed when I checked the version without apt update and apt full-upgrade. Does anyone have a theory here if my install was a very basic one, nothing extra was installed other than kodi and the chromium media edition?

[re-zero246]

hi,

when i

sudo rpi-eeprom-update -d -f /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2020-06-15.bin

the pi prompt me to reboot. after reboot its still the old bootloader from April. how can i fix this?

thanks in advance

What did you do thus far?
Did you:

sudo apt update
sudo full-upgrade
sudo reboot

#after reboot
sudo systemctl mask rpi-eeprom-update //which disables the automatic update based on your current bootloader channel (stable, beta or critical)
sudo rpi-eeprom-update
sudo rpi-eeprom-update -f /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2020-06-15.bin //or sudo rpi-eeprom-update -d -f /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2020-06-15.bin

[basti274]

hi,

when i

sudo rpi-eeprom-update -d -f /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2020-06-15.bin

the pi prompt me to reboot. after reboot its still the old bootloader from April. how can i fix this?

thanks in advance

What did you do thus far?
Did you:

sudo apt update
sudo full-upgrade
sudo reboot

#after reboot
sudo systemctl mask rpi-eeprom-update //which disables the automatic update based on your current bootloader channel (stable, beta or critical)
sudo rpi-eeprom-update
sudo rpi-eeprom-update -f /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2020-06-15.bin //or sudo rpi-eeprom-update -d -f /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2020-06-15.bin

exactly this, yes.

when i do sudo rpi-eeprom-update, this is what i get:

pi@raspberrypi:~ $ sudo rpi-eeprom-update
BCM2711 detected
Dedicated VL805 EEPROM detected
*** UPDATE REQUIRED ***
BOOTLOADER: update required
CURRENT: Thu 16 Apr 2020 05:11:26 PM UTC (1587057086)
LATEST: Mon 15 Jun 2020 01:36:19 PM UTC (1592228179)
FW DIR: /lib/firmware/raspberrypi/bootloader/beta
VL805: up-to-date
CURRENT: 000137ad
LATEST: 000137ad

[HawaiianPi]

...the pi prompt me to reboot. after reboot its still the old bootloader from April. how can i fix this?

What OS?

Does /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2020-06-15.bin exist (you may need to update/upgrade)?

Do you get any error messages from either rpi-eeprom-update or when the system reboots?

Are there any EEPROM recovery files in your boot partition?

What does vcgencmd bootloader_version show?

You could try downloading the beta recovery from: github.com/raspberrypi/rpi-eeprom/releases/tag/v2020.06.15-137ad

• Make a recovery SD card with Raspberry Pi Imager and the beta recovery
• Boot that SD card in your Pi4B to update the bootloader EEPROM
• When your monitor shows a green screen, it has completed successfully

[timg236]

OK, so I thought that I was running the 2020.06.15 from yesterday or the day before when I was trying to boot from a USB drive when infact I had 2020.06.03. I updated to the 2020.06.15, rebooted and it would give me the black screen with the flashing cursor in the upper left hand corner. Long story short, I had to reload the OS and when I did, 2020.06.15 was the bootloader that was presently flashed when I checked the version without apt update and apt full-upgrade. Does anyone have a theory here if my install was a very basic one, nothing extra was installed other than kodi and the chromium media edition?

What board revision is it?
/proc/cpuinfo

[hippy]

how can i fix this?

Try again ? Boot from the bootable recovery image ? Try with only one bootable device connected, SD Card or USB ?

My usual process worked okay, from having 2020-06-12 previously installed -

Code: Select all

wget https://github.com/raspberrypi/rpi-eeprom/raw/master/firmware/beta/pieeprom-2020-06-15.bin
rpi-eeprom-config pieeprom-2020-06-15.bin > cfg.txt
nano cfg.txt
rpi-eeprom-config --out new.bin --config cfg.txt pieeprom-2020-06-15.bin
sudo rpi-eeprom-update -d -f ./new.bin
sudo reboot

The .bin can of course be pulled from the /lib directory rather than downloaded.

[basti274]

...the pi prompt me to reboot. after reboot its still the old bootloader from April. how can i fix this?

What OS?

Does /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2020-06-15.bin exist (you may need to update/upgrade)?

Do you get any error messages from either rpi-eeprom-update or when the system reboots?

Are there any EEPROM recovery files in your boot partition?

What does vcgencmd bootloader_version show?

You could try downloading the beta recovery from: github.com/raspberrypi/rpi-eeprom/releases/tag/v2020.06.15-137ad

• Make a recovery SD card with Raspberry Pi Imager and the beta recovery
• Boot that SD card in your Pi4B to update the bootloader EEPROM
• When your monitor shows a green screen, it has completed successfully

no, i don´t get any errors. everything seems correct configured.


PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster

[HawaiianPi]

... I had to reload the OS and when I did, 2020.06.15 was the bootloader that was presently flashed when I checked the version without apt update and apt full-upgrade.

That's correct. Unlike previous models, the Pi4B has on-board EEPROM storage for some of the firmware (including the bootloader). So once flashed it will remain until it's replaced by something newer, and that will only happen with a new OS install when a newer version reaches the critical update channel (default setting in /etc/default/rpi-eeprom-update).

So re-installing Raspberry Pi OS should not affect the bootloader or VL805 firmware (even after an update/full-upgrade).

[re-zero246]

OK, so I thought that I was running the 2020.06.15 from yesterday or the day before when I was trying to boot from a USB drive when infact I had 2020.06.03. I updated to the 2020.06.15, rebooted and it would give me the black screen with the flashing cursor in the upper left hand corner. Long story short, I had to reload the OS and when I did, 2020.06.15 was the bootloader that was presently flashed when I checked the version without apt update and apt full-upgrade. Does anyone have a theory here if my install was a very basic one, nothing extra was installed other than kodi and the chromium media edition?

What board revision is it?
/proc/cpuinfo

At the very bottom of cat /proc/cpuinfo
Hardware : BCM2835
Revision : c03112
Serial :
Model : Raspberry Pi 4 Model B Rev 1.2

[re-zero246]

... I had to reload the OS and when I did, 2020.06.15 was the bootloader that was presently flashed when I checked the version without apt update and apt full-upgrade.

That's correct. Unlike previous models, the Pi4B has on-board EEPROM storage for some of the firmware (including the bootloader). So once flashed it will remain until it's replaced by something newer, and that will only happen with a new OS install when a newer version reaches the critical update channel (default setting in /etc/default/rpi-eeprom-update).

So re-installing Raspberry Pi OS should not affect the bootloader or VL805 firmware (even after an update/full-upgrade).

Thanks for that, I appreciate the feedback.

[re-zero246]

So after the clean Pi OS install due to my black screen with flashing cursor (pending feedback on why that may have happened), I tried a SD Card Copier to a USB 3.0 USB stick.
After a shutdown, removal of the SD Card, the USB option doesn't boot the OS.

lq_pic.jpeg (175.93 KiB) Viewed 21070 times

[basti274]

how can i fix this?

Try again ? Boot from the bootable recovery image ? Try with only one bootable device connected, SD Card or USB ?

My usual process worked okay, from having 2020-06-12 previously installed -

Code: Select all

wget https://github.com/raspberrypi/rpi-eeprom/raw/master/firmware/beta/pieeprom-2020-06-15.bin
rpi-eeprom-config pieeprom-2020-06-15.bin > cfg.txt
nano cfg.txt
rpi-eeprom-config --out new.bin --config cfg.txt pieeprom-2020-06-15.bin
sudo rpi-eeprom-update -d -f ./new.bin
sudo reboot

The .bin can of course be pulled from the /lib directory rather than downloaded.

"Try with only one bootable device connected, SD Card or USB ?"

this solves the problem with the bootloader! Thank you!!

now i got the problem that the pi doesn´t boot from the usb stick. UUIDs are correctly changed.

[HawaiianPi]

So after the clean Pi OS install due to my black screen with flashing cursor (pending feedback on why that may have happened), I tried a SD Card Copier to a USB 3.0 USB stick.
After a shutdown, removal of the SD Card, the USB option doesn't boot the OS.

That's because you didn't update the SD card before cloning it.

USB booting a Pi4 requires *.elf and *.dat files that are newer than the ones in the image. Boot from your card again and run sudo apt update && sudo apt full-upgrade -y then either clone it to the USB drive again, or copy the *.elf and *.dat files over.

[HawaiianPi]

...now i got the problem that the pi doesn´t boot from the usb stick. UUIDs are correctly changed.

What does the command sudo rpi-eeprom-update && vcgencmd bootloader_config return?

What OS is on your USB stick?

[re-zero246]

So after the clean Pi OS install due to my black screen with flashing cursor (pending feedback on why that may have happened), I tried a SD Card Copier to a USB 3.0 USB stick.
After a shutdown, removal of the SD Card, the USB option doesn't boot the OS.

That's because you didn't update the SD card before cloning it.

USB booting a Pi4 requires *.elf and *.dat files that are newer than the ones in the image. Boot from your card again and run sudo apt update && sudo apt full-upgrade -y then either clone it to the USB drive again, or copy the *.elf and *.dat files over.

Running the suggested produced the following:
sudo apt update && sudo apt full-upgrade -y
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is masked.
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I will try overwriting all of the *elf and *dat files from /boot to the sdcard's boot part but I am pretty sure that when I tried this before on 2020.06.03, it didn't make any difference and it shouldn't if the copy already includes the files.

[timg236]

So after the clean Pi OS install due to my black screen with flashing cursor (pending feedback on why that may have happened), I tried a SD Card Copier to a USB 3.0 USB stick.
After a shutdown, removal of the SD Card, the USB option doesn't boot the OS.

That's because you didn't update the SD card before cloning it.

USB booting a Pi4 requires *.elf and *.dat files that are newer than the ones in the image. Boot from your card again and run sudo apt update && sudo apt full-upgrade -y then either clone it to the USB drive again, or copy the *.elf and *.dat files over.

sudo apt update && sudo apt full-upgrade -y
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is masked.
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I will try overwriting all of the *elf and *dat files from /boot to the sdcard's boot part but I am pretty sure that when I tried this before on 2020.06.03, it didn't make any difference.

The diagnostics screen displays the the first part of the sha256 hash of the firmware binary files so it’s possible to verify the files against know good files eg rpi firmware repo

[re-zero246]

That's because you didn't update the SD card before cloning it.

USB booting a Pi4 requires *.elf and *.dat files that are newer than the ones in the image. Boot from your card again and run sudo apt update && sudo apt full-upgrade -y then either clone it to the USB drive again, or copy the *.elf and *.dat files over.

sudo apt update && sudo apt full-upgrade -y
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is masked.
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I will try overwriting all of the *elf and *dat files from /boot to the sdcard's boot part but I am pretty sure that when I tried this before on 2020.06.03, it didn't make any difference.

The diagnostics screen displays the the first part of the sha256 hash of the firmware binary files so it’s possible to verify the files against know good files eg rpi firmware repo

I will try that, I have even tried the files from https://github.com/raspberrypi/firmware/boot initially as well with no luck.

[basti274]

...now i got the problem that the pi doesn´t boot from the usb stick. UUIDs are correctly changed.

What does the command sudo rpi-eeprom-update && vcgencmd bootloader_config return?

What OS is on your USB stick?

got it!

but now i have another "small" problem

evertime i reboot via ssh the pi is booting up but i cant connect via ssh. i have to manual reboot (disconnect power) and after reboot i can connect via ssh

[timg236]

sudo apt update && sudo apt full-upgrade -y
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is masked.
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I will try overwriting all of the *elf and *dat files from /boot to the sdcard's boot part but I am pretty sure that when I tried this before on 2020.06.03, it didn't make any difference.

The diagnostics screen displays the the first part of the sha256 hash of the firmware binary files so it’s possible to verify the files against know good files eg rpi firmware repo

I will try that, I have even tried the files from https://github.com/raspberrypi/firmware/boot initially as well with no luck.

The one on the screenshot shows recover4.elf which implies that this is a NOOBS image. NOOBS is not upgradable and since this is beta firmware its not available in the NOOBS image.