timg236
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 645
Joined: Thu Jun 21, 2018 4:30 pm

Sticky: USB-MSD boot EEPROM third update - 2020-06-12

Fri Jun 12, 2020 1:30 pm

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. An APT update will probably be released soon.

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.
  • Reset Ethernet MAC + PHY if final boot mode is not network boot
    See: Kernel warning and network failure when attempting to use the network after bootloader times out. #144
  • Improve handling of multiple bootable USB devices and remove USB_MSD_BOOT_MAX_RETRIES
  • Resolve: No DHCPACK with DHCP relay agent #58
  • Toggle USB root hub port power for 200ms on the first USB MSD boot attempt
    See: Bootloader can't boot via USB-HDD after system reboot #151
  • Update bootloader handover to support uart_2ndstage - requires a newer start.elf firmware which will be via rpi-update.
  • Assert PCIe fundamental reset if the final bootmode was not USB-MSD because the OS might not do this before starting XHCI.

fruitoftheloom
Posts: 24050
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: USB-MSD boot EEPROM update - 2020-06-12

Fri Jun 12, 2020 3:06 pm

.
Success and my 4B 4GB is booting from 2.5" SSD via a USB3 - SATA Adapter.

First step download the BETA firmware, unzip and copy contents to SD Card, boots with green page - SUCCESS

Fresh install Raspberry Pi OS ARMHF on SD Card and apt update / full-upgrade / reboot....

...then rpi-update / reboot

SD Card Copier "SD Card to SSD (new partition UUIDs)", then shutdown and removed SD Card.

Boot Raspberry PI OS from SSD

uname -a
Linux raspberrypi 5.4.45-v7l+ #1321 SMP Wed Jun 10 17:39:20 BST 2020 armv7l GNU/Linux

lsusb
Bus 002 Device 002: ID 2109:0711 VIA Labs, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0c45:7403 Microdia Foot Switch
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

£5.00 USB3 -SATA Adapter
https://www.ebay.co.uk/itm/USB-3-0-To-S ... 3498873786

£10.00 48GB SSD (special offer price no longer offered)
https://www.amazon.co.uk/gp/product/B0824N68KG
Last edited by fruitoftheloom on Sat Jun 13, 2020 12:16 pm, edited 1 time in total.
Thinking outside the box is better than burying your head in the sand...

timg236
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 645
Joined: Thu Jun 21, 2018 4:30 pm

Re: USB-MSD boot EEPROM update - 2020-06-12

Fri Jun 12, 2020 3:33 pm

This is not an official recommendation (because we don't do that) but as another data point these are my personal USB devices which I use for Raspberry Pi hacking and I've been very happy with them so far.

£38.38 - SanDisk SSD PLUS 240 GB Sata III 2.5 Inch Internal SSD,
https://www.amazon.co.uk/USB-SATA-Adapt ... B01N2JIQR7

£7.49 - USB 3.0 to SATA Adapter Cable
https://www.amazon.co.uk/SanDisk-PLUS-S ... B01F9G43WU

£6.48 - SanDisk Ultra 32 GB USB Flash Drive USB 3.0 Up to 100 MB/s Read
https://www.amazon.co.uk/SanDisk-Ultra- ... B00DQG9OZ2

a350wb
Posts: 2
Joined: Fri Jun 12, 2020 6:31 am

Re: USB-MSD boot EEPROM update - 2020-06-12

Fri Jun 12, 2020 3:57 pm

Code: Select all

pi@raspberrypi:~ $ sudo rpi-eeprom-update
BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTLOADER: up-to-date
CURRENT: Fri 12 Jun 2020 10:55:44 AM UTC (1591959344)
 LATEST: Wed 03 Jun 2020 12:53:47 PM UTC (1591188827)
 FW DIR: /lib/firmware/raspberrypi/bootloader/beta
VL805: up-to-date
CURRENT: 000137ad
 LATEST: 000137ad

Code: Select all

 
[    2.025110] usb 1-1.3: new high-speed USB device number 3 using xhci_hcd
[    2.236538] usb 1-1.3: New USB device found, idVendor=7825, idProduct=a2a4, bcdDevice=41.01
[    2.236554] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.236569] usb 1-1.3: Product: Best USB Device
[    2.236584] usb 1-1.3: Manufacturer: ULT-Best
[    2.236598] usb 1-1.3: SerialNumber: 235678C218CA
[    2.243598] scsi host0: uas
[    2.245135] scsi 0:0:0:0: Direct-Access     INTEL SS DSC2CW120A3      4101 PQ: 0 ANSI: 6
[    2.247815] sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB)
[    2.247833] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    2.248072] sd 0:0:0:0: [sda] Write Protect is off
[    2.248089] sd 0:0:0:0: [sda] Mode Sense: 5f 00 00 08
[    2.248556] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.248934] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[    2.253514]  sda: sda1 sda2
using usb sata cable(no external power) to SSD Intel, manage to boot. if plug to USB3 somehow bluetooth will failed . anyone having this problem?

Kendek
Posts: 265
Joined: Thu Jul 25, 2019 4:39 pm
Location: Kaposvár, Hungary

Re: USB-MSD boot EEPROM update - 2020-06-12

Fri Jun 12, 2020 4:53 pm

timg236 wrote:
Fri Jun 12, 2020 1:30 pm
...
[*] Toggle USB root hub port power for 200ms on the first USB MSD boot attempt
...
I'm really not happy about this on the 8GB Pi4 (1.4).
With pieeprom 06-03 (and earlier), the 4GB Pis (1.1) doesn't cut the power on the USB ports when the system restarts. But the 8GB Pis do that, unfortunately. I was able to handle this with a script;
/lib/systemd/system-shutdown/hdd.reboot:

Code: Select all

#!/bin/sh

[ $1 = reboot ] && [ $(printf /dev/sd[a-z]) != "/dev/sd[a-z]" ] && {
    sleep 0.1s && hdparm -Y /dev/sd[a-z] &
    sleep 3s
  }
Which is worked great, until now. Now with pieeprom 06-12, the 8GB Pi cuts the power on the USB ports twice. And now I have to use this script on 4GB Pis as well, but the hdparm -Y doesn't work (otherwise the restart process would stop here), only the option -y.
My suggestion is that this extra, secondary 200ms power toggle should not be used on 8GB Pis. Because it kills the hard drives.

The UDEV rule for shutdown still works well:

Code: Select all

ACTION=="add|change", SUBSYSTEM=="scsi_disk", RUN+="/bin/sh -c 'echo 1 >/sys/class/scsi_disk/%k/manage_start_stop'"
Last edited by Kendek on Fri Jun 12, 2020 7:48 pm, edited 1 time in total.

rcfa
Posts: 15
Joined: Sun Feb 25, 2018 5:22 am

Re: USB-MSD boot EEPROM update - 2020-06-12

Fri Jun 12, 2020 5:43 pm

So the good news is, I got Kali to run on an RPi4B-8GB off the sd card moved from the sd slot into an USB-SD-card-reader, good enough as proof of concept.

The way I got that done is by doing the rpi-update on a RaspberryPiOS boot SD card, and then copying /boot/start*.elm and /boot/fixup*.dat from the RaspberryPiOS SD card and replacing with these the ones that were on the Kali boot partition.

Now, that;s good enough to bring things up.

The question is, which parts of the /boot partition are kernel independent, i.e. can be copied/updated regardless of the distribution and kernel version being booted, and which not?

The Kali I have has 4.19.xxx custom kernel, so obviously the kernel files themselves are out.

What about bootcode.bin? What about the various *.dtb files? What about the contents of the overlays directory?
Obviously, as far as feasible and compatible, I want to use the latest versions, but also obviously, only as far as they can be expected to work with just about any otherwise valid linux kernel for the RPi.

Thanks!

PiUser10
Posts: 42
Joined: Mon Dec 30, 2013 9:20 am

Re: USB-MSD boot EEPROM update - 2020-06-12

Fri Jun 12, 2020 6:29 pm

Pi 4B 8GB model, official POE hat, with bottom USB 3.0 port connected to boot SSD, top USB 3.0 port connected to powered USB 3.0 4 port hub
to allow connection of other SSD's for data storage/copying on occasions. I think the USB 3.0 hub is causing a back power condition.

With eeprom 03/06/2020 everything worked as expected (with the external hub powered up at all times)

1) on connecting RJ45 from POE switch the Pi booted from SSD as expected.
2) Reboot from PiOS worked as expected
3) Shutdown (halt) followed by grounding of GPIO PIN 5 caused correct reboot as expected

With eeprom 12/06/2020 cold boot no longer works (with external hub powered up)
1) on connecting the RJ45 from POE the red power LED just flashes, now need to remove power from external hub to get it to continue booting.
2) Reboot from OS works as expected
3) Shutdown (halt) followed by grounding of GPIO PIN 5 caused correct reboot as expected

I guess the change to add 200ms power toggle on first boot must be the cause of option (1) no longer working without pulling the power on
the external USB 3.0 hub.
The power can be restored to the hub following the first boot and options (2) and (3) continue to work until POE power is removed by disconnecting the RJ45 from the switch.

I was very happy with eeprom 03/06/2020 (and may need to flash back to it) as it did not appear to be effected by the back powered hub but
eeprom 12/06/2020 now requires to remember to remove external hub power before initial power on boot.

Do we actually need this 200ms power toggle to be in place ?
It may fix a problem but for some it appears to generates one.

PiUser10
Posts: 42
Joined: Mon Dec 30, 2013 9:20 am

Re: USB-MSD boot EEPROM update - 2020-06-12

Fri Jun 12, 2020 7:35 pm

Update to my last post :-
Flashed back to 03/06/2020 eeprom and problem can be created with this release also.
I found a situation which I did not consider and which I would normally not run into.
The flashing red LED problem ONLY appears to happens if the power to the external USB 3.0 hub has not been interrupted since the
removal of the POE power.
With the Pi in the no POE power mode all that is needed to stop the power LED issue is to unplug the external powered hub
for a few seconds then plug it back in, once the POE power is then applied all appears to boot as normal.
As I normally power everything off on an evening (hence the power to external hub is removed) then power up (hub , monitor etc) before plugging in the POE power on a morning I did not see this red LED flashing behavior.
I will continue to monitor this situation to verify that this is an accurate description of what is happening.
What I really need is a powered external USB 3.0 hub that follows the rules and does not back power what it is connected to !
Having tried 2 so far I have not found one, anyone have any suggestions for such a beast that they have tested ?

RonR
Posts: 1559
Joined: Tue Apr 12, 2016 10:29 pm
Location: US

Re: USB-MSD boot EEPROM update - 2020-06-12

Fri Jun 12, 2020 7:46 pm

ACT LED is still stuck on with no SD card present but enable_uart=1 present in config.txt using 2020-06-12 bootloader.

User avatar
HawaiianPi
Posts: 5968
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: USB-MSD boot EEPROM update - 2020-06-12

Fri Jun 12, 2020 10:33 pm

timg236 wrote:
Fri Jun 12, 2020 1:30 pm
-- Toggle USB root hub port power for 200ms on the first USB MSD boot attempt
My 4B2 system still cold boots and reboots fine, but I'm also running the beta VL805 138a1 firmware (if that matters).

Since this seems to be problematic for others, I wonder if it could be made a bootconfig.txt option?

timg236 wrote:
Fri Jun 12, 2020 1:30 pm
-- Improve handling of multiple bootable USB devices
-- Update bootloader handover to support uart_2ndstage - requires a newer start.elf firmware which will be via rpi-update.
These sound interesting, could you explain those changes in more detail, please?

timg236 wrote:
Fri Jun 12, 2020 3:33 pm
This is not an official recommendation (because we don't do that) but as another data point these are my personal USB devices which I use for Raspberry Pi hacking and I've been very happy with them so far.

£7.49 - USB 3.0 to SATA Adapter Cable
https://www.amazon.co.uk/USB-SATA-Adapt ... B01N2JIQR7
That looks just like the Eluteng adapter cable I use, but the Eluteng is less expensive (£6.99 at time of post).
https://www.amazon.co.uk/dp/B06XCV1W97
timg236 wrote:
Fri Jun 12, 2020 3:33 pm
£6.48 - SanDisk Ultra 32 GB USB Flash Drive USB 3.0 Up to 100 MB/s Read
https://www.amazon.co.uk/SanDisk-Ultra- ... B00DQG9OZ2
I've tested a Samsung Bar Plus 64GB and it works great (nice and fast), but it is a tight fit in the USB port, so I use an inexpensive 90 degree (up) USB 3.0 M-F adapter, which solves 2 problems (less wear on the Pi USB port, and it doesn't stick out as far).


My System Details
  • Raspberry Pi 4 Model B Rev 1.1 (2GB)
  • Official Raspberry Pi 15.3W USB-C Power Supply
  • Eluteng "blue" USB 3.0 to SATA-III adapter cable (174c:55aa ASMedia 1153E?)
  • Silicon Power A55 256GB SATA-III SSD
  • CP2102 USB-TTL UART (used as serial console cable for debugging)
  • Generic open-sided case with Noctua 40x10mm 5V fan.

Code: Select all

$ sudo rpi-eeprom-update && vcgencmd bootloader_config
BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTLOADER: up-to-date
CURRENT: Fri 12 Jun 2020 10:55:44 AM UTC (1591959344)
 LATEST: Wed 03 Jun 2020 12:53:47 PM UTC (1591188827)
 FW DIR: /lib/firmware/raspberrypi/bootloader/beta
VL805: up-to-date
CURRENT: 000138a1
 LATEST: 000137ad
[all]
BOOT_UART=1
WAKE_ON_GPIO=0
POWER_OFF_ON_HALT=1
DHCP_TIMEOUT=45000
DHCP_REQ_TIMEOUT=4000
TFTP_FILE_TIMEOUT=30000
ENABLE_SELF_UPDATE=1
DISABLE_HDMI=0
BOOT_ORDER=0xf41
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

Doug_
Posts: 52
Joined: Tue Oct 08, 2019 6:40 pm

Re: USB-MSD boot EEPROM update - 2020-06-12

Sat Jun 13, 2020 12:30 am

A data point on the USB sticks that may or may not be significant - I have been using a SanDisk Ultra Flair 64Gbyte (boasting 150MB/s read) for some time now and recently ran ‘fstrim -va’ , it was quietly ignored. This suggests it does not support the discard function.

So I’m thinking perhaps these sticks are not best suited for long term use as system drives. At least check them before committing a critical system to one.

On the other hand the 64G Samsung uSD system drive did trim more than 32GB after about 9 months 24/7 running.

Edit: the boot eeprom documentation is here:
https://www.raspberrypi.org/documentati ... _config.md

KPeyanski
Posts: 1
Joined: Sat Jun 13, 2020 5:39 am

Re: USB-MSD boot EEPROM update - 2020-06-12

Sat Jun 13, 2020 6:08 am

Hello there,

I can confirm that the SSD HP P600, 250GB, USB 3.1 is working just fine without any issues so far with the 2020-06-03 firmware.

https://amzn.to/2B7qIDi

Just a quick question, how can I update the firmware from now on without having to repeat the whole procedure with the SD card?

Thanks in advance.

Kendek
Posts: 265
Joined: Thu Jul 25, 2019 4:39 pm
Location: Kaposvár, Hungary

Re: USB-MSD boot EEPROM update - 2020-06-12

Sat Jun 13, 2020 11:53 am

timg236 wrote:
Fri Jun 12, 2020 1:30 pm
...
[*] Toggle USB root hub port power for 200ms on the first USB MSD boot attempt
...
I took three videos about my problem, used same HDD, RPi OS and setup:

1. RPi4 4GB (1.1) with pieeprom 06-12.
Exactly one USB power cut after I executed the reboot command. As you can see and hear, the HDD has performed an emergency head retract to prevents head crash. The Power-Off_Retract_Count S.M.A.R.T. value increases after this action, so that's why need the script with hdparm.

2. RPi4 8GB (1.4) with pieeprom 06-03.
The behavior is similar to how the 4GB variant behaved. But the USB power cut occurred a bit sooner (simultaneously with Pi's power LED) and lasted longer than 200ms.

3. RPi4 8GB (1.4) with pieeprom 06-12.
Two USB power cut, the secondary 200ms is very harmful to the HDD and the emergency head rectract is inevitable.
The same is true when the bootloader flashes itself, but I can use the flashrom as a workaround.

hippy
Posts: 8235
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: STICKY: USB-MSD boot EEPROM third update - 2020-06-12

Sat Jun 13, 2020 1:29 pm

Not quite sure what's gone wrong but trying to install the 2020-06-12 version, using the same process which had worked before, seems to have reverted me back to the 2020-04-17 version, and I have lost USB booting. Haven't investigated further.

Update : It appears the update undertaken from my USB booted device did not take. Reboots then fall through to booting an SD Card left in the socket which had "critical" set as the Boot Eeproms to track, which I presume took me back to the default critical Boot Eeprom image.

An update/full-upgrade while attempting to fix things then wiped out my 5.4 kernel and downgraded to 4.19, and now rpi-update says that's up to date, and won't let me install 5.4

Good news is I have now managed to burn the 2020-06-12 Boot Eeprom image, so that's done even though I seem to have lost USB boot capability. I'm presuming the firmware on the USB device is not up to date.

One question, would these 'cutting edge' topics on beta software, of interest only to a minority, not be best pursued in some other forum rather than "General Discussions" ?

delerium
Posts: 1
Joined: Sat Jun 13, 2020 12:41 pm

Re: STICKY: USB-MSD boot EEPROM third update - 2020-06-12

Sat Jun 13, 2020 5:42 pm

Raspberry Pi 4, 4 GB. Bootloader 120620 build.

USB boot works with quirks (Orico USB 3.1 enclosure, not recommended I guess, Crucial BX100 SSD), but when I do sudo reboot, it cuts the power from the USB drive and I cannot get the Raspberry to boot until I replug the USB hard drive (or power cycle).

User avatar
HawaiianPi
Posts: 5968
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: STICKY: USB-MSD boot EEPROM third update - 2020-06-12

Sat Jun 13, 2020 10:24 pm

hippy wrote:
Sat Jun 13, 2020 1:29 pm
Reboots then fall through to booting an SD Card left in the socket ...
SD card booting has priority, so if there is a boot SD card in the system, that's what boots (not the USB drive).

hippy wrote:
Sat Jun 13, 2020 1:29 pm
An update/full-upgrade while attempting to fix things then wiped out my 5.4 kernel and downgraded to 4.19, and now rpi-update says that's up to date, and won't let me install 5.4
There is a hidden .firmware file in /boot that you can delete to force a new rpi-update, or if you don't want to overwrite your previous firmware backup, you can try sudo SKIP_BACKUP=1 rpi-update (haven't tried that one myself).

hippy wrote:
Sat Jun 13, 2020 1:29 pm
Good news is I have now managed to burn the 2020-06-12 Boot Eeprom image, so that's done even though I seem to have lost USB boot capability. I'm presuming the firmware on the USB device is not up to date.
An update/full-upgrade will get you the required firmware (just not the 5.4 kernel), so USB boot should still be working.

How did you "burn the 2020-06-12 Boot Eeprom image"?

The simplest way is to download the beta EEPROM recovery image (github.com/raspberrypi/rpi-eeprom/files/4770700/rpi-boot-eeprom-recovery-2020-06-12-vl805-000137ad-BETA.zip) and make a recovery SD card.

delerium wrote:
Sat Jun 13, 2020 5:42 pm
Raspberry Pi 4, 4 GB. Bootloader 120620 build.

USB boot works with quirks (Orico USB 3.1 enclosure, not recommended I guess, Crucial BX100 SSD), but when I do sudo reboot, it cuts the power from the USB drive and I cannot get the Raspberry to boot until I replug the USB hard drive (or power cycle).
Likely a problem with your enclosure. I have no trouble rebooting from SSD with my USB 3.0 to SATA-III adapter cable.

$ vcgencmd bootloader_version
Jun 12 2020 11:55:44
version ef583b735977179d4b27711af03419559f982a5e (release)
timestamp 1591959344
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

hippy
Posts: 8235
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: STICKY: USB-MSD boot EEPROM third update - 2020-06-12

Sun Jun 14, 2020 1:54 pm

HawaiianPi wrote:
Sat Jun 13, 2020 10:24 pm
hippy wrote:
Sat Jun 13, 2020 1:29 pm
Reboots then fall through to booting an SD Card left in the socket ...
SD card booting has priority, so if there is a boot SD card in the system, that's what boots (not the USB drive).
Previously I had set the BOOT_ORDER as 0xf214, so right to left, USB (4), SD Card (1), Network Boot (2), repeat (F).

That had all been working fine for a while. It was only after this latest update failed for some reason that it didn't boot the USB device after a reboot - possibly lost/wrong firmware on the USB device, fell through and booted SD Card, which I'm presuming reverted the Boot Eeprom. Though maybe it had been reverted / staged for reversion prior to reboot.

I'm happy to accept that I pulled the carpet from under my own feet and this is beta territory. It was just a bit frustrating have that happen and not be sure why, it being more difficult than I'd expected to get back to where I had been.
HawaiianPi wrote:
Sat Jun 13, 2020 10:24 pm
How did you "burn the 2020-06-12 Boot Eeprom image"?

Code: Select all

wget https://github.com/raspberrypi/rpi-eeprom/raw/master/firmware/beta/pieeprom-2020-06-12.bin
rpi-eeprom-config --out new.bin --config cfg.txt pieeprom-2020-06-12.bin
sudo rpi-eeprom-update -d -f ./new.bin
sudo reboot
That's been my process to update previously which has always worked. That somehow failed after I'd booted to my USB device, did that, then re-booted. After fixing my issues with the SD Card, it then subsequently worked from that.

So it's a bit of a mystery why it all went pear-shaped when done on the USB booted device, when similar had worked before, and after from SD. I haven't looked more deeply at that, identified what's making the USB device non-bootable.

hippy
Posts: 8235
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: STICKY: USB-MSD boot EEPROM third update - 2020-06-12

Sun Jun 14, 2020 3:41 pm

With just the SD Card inserted, usual Boot Screen and booting, works fine, just as it did when I left it yesterday ...

Code: Select all

pi@Pi4B:~ $ uname -a
Linux Pi4B 5.4.45-v7l+ #1321 SMP Wed Jun 10 17:39:20 BST 2020 armv7l GNU/Linux

Code: Select all

pi@Pi4B:~ $ sudo rpi-eeprom-update
BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTLOADER: up-to-date
CURRENT: Fri 12 Jun 10:55:44 UTC 2020 (1591959344)
 LATEST: Wed  3 Jun 12:53:47 UTC 2020 (1591188827)
 FW DIR: /lib/firmware/raspberrypi/bootloader/beta
VL805: up-to-date
CURRENT: 000137ad
 LATEST: 000137ad
So that's "perfect" as far as I can see, 2020-06-12 in place. Onwards and upwards.

Powered down, removed the SD Card and inserted the 'was bootable' USB device. Powered-up ...

Red and green LED on permanently, no HDMI. "Nada"; a typical 'green light of death' situation.

Powered down, inserted SD Card, left the USB device connected, powered-up ...

As expected, HDMI comes on, Boot Screen appears, goes by too fast to read what's happening, boots from SD Card, green LED flashing on accesses, everything works as expected. Desktop appears, USB device mounted, looks as expected.

But darn it, back to 2020-04-16 Boot Eeprom image installed ...

Code: Select all

pi@Pi4B:~ $ uname -a
Linux Pi4B 5.4.45-v7l+ #1321 SMP Wed Jun 10 17:39:20 BST 2020 armv7l GNU/Linux

Code: Select all

pi@Pi4B:~ $ sudo rpi-eeprom-update
BCM2711 detected
Dedicated VL805 EEPROM detected
*** UPDATE REQUIRED ***
BOOTLOADER: update required
CURRENT: Thu 16 Apr 17:11:26 UTC 2020 (1587057086)
 LATEST: Wed  3 Jun 12:53:47 UTC 2020 (1591188827)
 FW DIR: /lib/firmware/raspberrypi/bootloader/beta
VL805: up-to-date
CURRENT: 000137ad
 LATEST: 000137ad
I updated the Boot Eeprom to 2020-06-12. Re-booted with SD Card inserted, USB device removed, and that worked as expected. Still at 2020-06-12 Boot Eeprom. So okay again. A couple of further reboots without USB device connected and it stays the same.

Connect the non-bootable USB device and reboot. SD Boots and we are again reverted back to 2020-04-16.

So just plugging the USB device in and rebooting is reverting the Boot Eeprom.

Which led me to; 'recovery.bin', 'pieeprom.upd' and 'pieeprom.sig' being present on both SD Card /boot and USB device /boot.

Delete all those and reboot and they are gone on USB but reappear on SD. Presumably because what's installed is earlier than what release it's tracking.

Update once again to 2020-06-12. Reboot and, Tada!, USB booted. With USB removed booting from SD card works. With only USB that also works. Without either it falls back to network booting.

So I guess the issue is that Boot Eeprom updates happen before the boot media is determined so it can update from USB before booting SD and update from SD before booting from USB. And then one ends up in a circle of hell when what's updated doesn't match what's just booted.

I guess that if everything matches on everything one is booting, everything is set exactly the same, then everything is fine but when it isn't, that's when things break.

I must admit that I haven't figured out head from tail in the complexity which is Boot Eeprom auto-updating with FREEZE_VERSION, ENABLE_SELF_UPDATE, bootloader_update, 'apt full-upgrade', and the systemd update service. I guess I need to study the documentation. I'd stuck to defaults in the hope of avoiding things going wrong. I didn't think there was any possibility of an auto-downgrade but that seems to be what does happen in some circumstances.

I can't help but think it's far more complicated than it needs to be and I'm not going to be the only one who gets themselves into a complete mess.

Can't we just have it that 'apt full-upgrade' does it all, tells the user to reboot when they need to - or leave them to figure it out for themselves as for other cases, and let them hold back the rpi-eeprom package if they don't want to auto-update ?

thatchunkylad198966
Posts: 275
Joined: Thu Jul 04, 2019 10:21 am
Location: UK, Birmingham

Re: STICKY: USB-MSD boot EEPROM third update - 2020-06-12

Sun Jun 14, 2020 4:09 pm

How do we update to this if we're on 3rd of June eeprom?

EDIT: this one I'm on about: CURRENT: Wed 3 Jun 12:53:47 UTC 2020 (1591188827)

EDIT2: it says it's the latest..... :oops:
One man's trash is another man's treasure! :) Pi's I have; Pi Zero, Pi Zero W, Pi 2 x2, Pi 3 x2, Pi 4 4GB x2.

Herbaldew
Posts: 67
Joined: Wed Feb 07, 2018 2:59 pm
Location: US Mid-Atlantic

Re: STICKY: USB-MSD boot EEPROM third update - 2020-06-12

Sun Jun 14, 2020 4:14 pm

thatchunkylad198966 wrote:
Sun Jun 14, 2020 4:09 pm
How do we update to this if we're on 3rd of June eeprom?
HawaiianPi wrote:
Sat Jun 13, 2020 10:24 pm
The simplest way is to download the beta EEPROM recovery image (github.com/raspberrypi/rpi-eeprom/files/4770700/rpi-boot-eeprom-recovery-2020-06-12-vl805-000137ad-BETA.zip) and make a recovery SD card.

thatchunkylad198966
Posts: 275
Joined: Thu Jul 04, 2019 10:21 am
Location: UK, Birmingham

Re: STICKY: USB-MSD boot EEPROM third update - 2020-06-12

Sun Jun 14, 2020 4:17 pm

Herbaldew wrote:
Sun Jun 14, 2020 4:14 pm
thatchunkylad198966 wrote:
Sun Jun 14, 2020 4:09 pm
How do we update to this if we're on 3rd of June eeprom?
HawaiianPi wrote:
Sat Jun 13, 2020 10:24 pm
The simplest way is to download the beta EEPROM recovery image (github.com/raspberrypi/rpi-eeprom/files/4770700/rpi-boot-eeprom-recovery-2020-06-12-vl805-000137ad-BETA.zip) and make a recovery SD card.
Yeah can't do that, only sdcard I have is in use right now.
No other way? :mrgreen:
One man's trash is another man's treasure! :) Pi's I have; Pi Zero, Pi Zero W, Pi 2 x2, Pi 3 x2, Pi 4 4GB x2.

User avatar
HawaiianPi
Posts: 5968
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: STICKY: USB-MSD boot EEPROM third update - 2020-06-12

Sun Jun 14, 2020 4:29 pm

thatchunkylad198966 wrote:
Sun Jun 14, 2020 4:17 pm
Yeah can't do that, only sdcard I have is in use right now.
No other way? :mrgreen:
Best solution: get another card. ;) Or you can flash it manually.

Get the new 2020-06-12 bootloader recovery, extract the zip to a folder, and flash it with sudo rpi-eeprom-update -d -f ./pieeprom.bin (followed by a reboot).
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

Kendek
Posts: 265
Joined: Thu Jul 25, 2019 4:39 pm
Location: Kaposvár, Hungary

Re: STICKY: USB-MSD boot EEPROM third update - 2020-06-12

Sun Jun 14, 2020 4:30 pm

thatchunkylad198966 wrote:
Sun Jun 14, 2020 4:17 pm
...
No other way? :mrgreen:
https://github.com/raspberrypi/rpi-eepr ... mware/beta

rpi-eeprom-update option:

Code: Select all

-f Install the given file instead of the latest applicable update
   Ignores the FREEZE_VERSION flag in bootloader and is intended for manual firmware updates.

hippy
Posts: 8235
Joined: Fri Sep 09, 2011 10:34 pm
Location: UK

Re: STICKY: USB-MSD boot EEPROM third update - 2020-06-12

Sun Jun 14, 2020 4:33 pm

thatchunkylad198966 wrote:
Sun Jun 14, 2020 4:17 pm
Yeah can't do that, only sdcard I have is in use right now.
No other way? :mrgreen:
I have spare SD Cards but can't be bothered with all that swapping, especially when booting from something other than SD Card.

This works for me. I did have issues as described above but I don't believe it's the process which is flawed -

Code: Select all

wget https://github.com/raspberrypi/rpi-eeprom/raw/master/firmware/beta/pieeprom-2020-06-12.bin
rpi-eeprom-config pieeprom-2020-06-12.bin > cfg.txt
nano cfg.txt
rpi-eeprom-config --out new.bin --config cfg.txt pieeprom-2020-06-12.bin
sudo rpi-eeprom-update -d -f ./new.bin
sudo reboot
You can use 'vcgencmd bootloader_config > cfg.txt' to get your current settings as 'cfg.txt'.
Last edited by hippy on Sun Jun 14, 2020 4:34 pm, edited 1 time in total.

thatchunkylad198966
Posts: 275
Joined: Thu Jul 04, 2019 10:21 am
Location: UK, Birmingham

Re: STICKY: USB-MSD boot EEPROM third update - 2020-06-12

Sun Jun 14, 2020 4:33 pm

HawaiianPi wrote:
Sun Jun 14, 2020 4:29 pm
thatchunkylad198966 wrote:
Sun Jun 14, 2020 4:17 pm
Yeah can't do that, only sdcard I have is in use right now.
No other way? :mrgreen:
Best solution: get another card. ;) Or you can flash it manually.

Get the new 2020-06-12 bootloader recovery, extract the zip to a folder, and flash it with sudo rpi-eeprom-update -d -f ./pieeprom.bin (followed by a reboot).


Not going to get another sdcard, I ain't wasting my money.
I'll try what you said.

Cheers.
One man's trash is another man's treasure! :) Pi's I have; Pi Zero, Pi Zero W, Pi 2 x2, Pi 3 x2, Pi 4 4GB x2.

Return to “General discussion”