Update to default Pi4 bootloader

[no3rpi]

you can force update manual:
1 - download the new eeprom: https://github.com/raspberrypi/rpi-eeprom/releases
2 - extract on your rpi.
3 - if require edit/update eeprom config data: https://www.raspberrypi.org/documentati ... _config.md
4 - flash the new eeprom from dir you extracted the archive:

Code: Select all

# Flash the bootloader EEPROM
# Run 'rpi-eeprom-update -h' for more information
sudo rpi-eeprom-update -d -f ./pieeprom.bin
sudo reboot

this is how it looks updated manual on LibreElec:

Code: Select all

rpi-eeprom-update
BCM2711 detected
BOOTLOADER: up-to-date
CURRENT: Thu Apr 16 17:11:26 UTC 2020 (1587057086)
 LATEST: Tue Sep 10 10:41:50 UTC 2019 (1568112110)
VL805: up-to-date
CURRENT: 000137ad
 LATEST: 000137ad

vcgencmd bootloader_version
Apr 16 2020 18:11:26
version a5e1b95f320810c69441557c5f5f0a7f2460dfb8 (release)
timestamp 1587057086
 

[dickon]

That's weird. The "latest" version that shows is earlier than the "current" version.

'Latest' I *think* just means the latest version available in /lib/firmware/raspberrypi/bootloader/*/ which may or may not match what the latest actually is.

[timg236]

Correct. It's the latest version available on your system. New binaries are delivered via APT

[timg236]

What is the output from rpi-eeprom-update?

Here's what I get

Code: Select all

BCM2711 detected
BOOTLOADER: up-to-date
CURRENT: Fri 17 Jan 17:37:11 UTC 2020 (1579282631)
 LATEST: Tue 10 Sep 10:41:50 UTC 2019 (1568112110)
 FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000137ad
 LATEST: 000137ad

That's not updated is it?

New firmware releases are delivered via APT, the script is really is just a fancy version of ls | sort on the contents of the firmware directories. To get new binaries use APT

Code: Select all

sudo apt update
sudo apt full-upgrade
reboot

Alternatively, you can use the Raspberry Pi Imager to upgrade https://www.raspberrypi.org/downloads/ the EEPROM because this is now the default image.

[DarkElvenAngel]

What is the output from rpi-eeprom-update?

Here's what I get

Code: Select all

BCM2711 detected
BOOTLOADER: up-to-date
CURRENT: Fri 17 Jan 17:37:11 UTC 2020 (1579282631)
 LATEST: Tue 10 Sep 10:41:50 UTC 2019 (1568112110)
 FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000137ad
 LATEST: 000137ad

That's not updated is it?

New firmware releases are delivered via APT, the script is really is just a fancy version of ls | sort on the contents of the firmware directories. To get new binaries use APT

Code: Select all

sudo apt update
sudo apt full-upgrade
reboot

Alternatively, you can use the Raspberry Pi Imager to upgrade https://www.raspberrypi.org/downloads/ the EEPROM because this is now the default image.

I did the full-upgrade and now I have this

Code: Select all

BCM2711 detected                                                   BOOTLOADER: up-to-date                                             CURRENT: Thu 16 Apr 17:11:26 UTC 2020 (1587057086)                  LATEST: Thu 16 Apr 17:11:26 UTC 2020 (1587057086)                  FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000137ad
 LATEST: 000137ad

So I normally do dist-upgrade should I be using full-upgrade instead?

[jamesh]

Here's what I get

Code: Select all

BCM2711 detected
BOOTLOADER: up-to-date
CURRENT: Fri 17 Jan 17:37:11 UTC 2020 (1579282631)
 LATEST: Tue 10 Sep 10:41:50 UTC 2019 (1568112110)
 FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000137ad
 LATEST: 000137ad

That's not updated is it?

New firmware releases are delivered via APT, the script is really is just a fancy version of ls | sort on the contents of the firmware directories. To get new binaries use APT

Code: Select all

sudo apt update
sudo apt full-upgrade
reboot

Alternatively, you can use the Raspberry Pi Imager to upgrade https://www.raspberrypi.org/downloads/ the EEPROM because this is now the default image.

I did the full-upgrade and now I have this

Code: Select all

BCM2711 detected                                                   BOOTLOADER: up-to-date                                             CURRENT: Thu 16 Apr 17:11:26 UTC 2020 (1587057086)                  LATEST: Thu 16 Apr 17:11:26 UTC 2020 (1587057086)                  FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000137ad
 LATEST: 000137ad

So I normally do dist-upgrade should I be using full-upgrade instead?

Not sure, dist-upgrade and full-upgrade are almost the same - we now recommend full-upgrade.

[fruitoftheloom]

So I normally do dist-upgrade should I be using full-upgrade instead?

https://www.raspberrypi.org/documentati ... pdating.md

[DarkElvenAngel]

So I normally do dist-upgrade should I be using full-upgrade instead?

https://www.raspberrypi.org/documentati ... pdating.md

I see things have changed I'm not keeping current with the changes. Thanks

[glovebox]

Hey, I have a curious issue I think is related to the latest bootloader. I've been on the beta bootloader builds and this wasn't an issue till the latest.

OS: Raspbian Buster Lite

• Trying to boot from freshly flashed SD Card
• If I have a USB3 flash drive plugged into one of the USB3 ports. The OS boots but the Wifi doesn't connect.
• With the USB3 flash drive still plugged in, I add a USB device such as a mouse to the USB2 port and reboot. The WiFi now connects to my router.

Also tested:

OS: Raspbian Buster with desktop

• Booting from a freshly flashed SD Card
• With just the USB3 flash drive plugged in, the OS boots, and the WiFi connects - just works.

Output from sudo rpi-eeprom-update

BCM2711 detected
BOOTLOADER: up-to-date
CURRENT: Thu 16 Apr 17:11:26 UTC 2020 (1587057086)
LATEST: Thu 16 Apr 17:11:26 UTC 2020 (1587057086)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000137ad
LATEST: 000137ad


Hmmm, any suggestions appreciated.

Cheers Dave

[Asxetos]

Updated eeprom on my LibreElec, tested boot without SD card and I have a nice debug info; all looks good.

Also tested:

OS: Raspbian Buster with desktop

• With just the USB3 flash drive plugged in, the OS boots, and the WiFi connects - just works.

Help me understand this guys,
Is the "usb booting" code already integrated in the latest bootloader?

[jamesh]

Updated eeprom on my LibreElec, tested boot without SD card and I have a nice debug info; all looks good.

Also tested:

OS: Raspbian Buster with desktop

• With just the USB3 flash drive plugged in, the OS boots, and the WiFi connects - just works.

Help me understand this guys,
Is the "usb booting" code already integrated in the latest bootloader?

Not that I am aware of.

[lingon]

...
Although this won't make much difference to the normal SD-CARD boot configuration the HDMI diagnostics screen should make support easier because users can attach a picture.
...

Is the HDMI-diagnostic bitmap written to the boot media if the storage is available and writing to it succeeds?

[timg236]

...
Although this won't make much difference to the normal SD-CARD boot configuration the HDMI diagnostics screen should make support easier because users can attach a picture.
...

Is the HDMI-diagnostic bitmap written to the boot media if the storage is available and writing to it succeeds?

No. Normally if you see this then there is no boot-media and except for a very special case in recovery.bin the bootloader never writes to boot media.
The expectation is that photographs may be used and in time the QR code might be dynamically generated in order to link to a specific support page.

[glovebox]

Updated eeprom on my LibreElec, tested boot without SD card and I have a nice debug info; all looks good.

Also tested:

OS: Raspbian Buster with desktop

• With just the USB3 flash drive plugged in, the OS boots, and the WiFi connects - just works.

Help me understand this guys,
Is the "usb booting" code already integrated in the latest bootloader?

Not that I am aware of.

I'm booting on the regular Micro SD, but my intention is to move the OS to the USB3 drive, boot from SD Card and run the OS from the USB3 Flash. This has been working very well as per my article at https://dev.to/azure/azure-iot-edge-on- ... -pi-4-22nn.

The USB 3 Flash that is plugged is freshly formatted. This problem happened before setting up the kernel pivot.

Cheers Dave

[lingon]

While waiting for the USB boot to start working I'm running on an eMMC module in my Raspberry Pi 4.

pieeprom-2020-05-15.bin - USB mass storage boot beta

USB boot also requires updated firmware (start.elf)

I tried the upgrade to pieeprom-2020-05-15.bin even though the new start elf is not available. After that I could not boot from the eMMC module in the uSD-eMMC adaptor. Booting from a uSD-card worked fine for me with pieeprom-2020-05-15.bin, so I recovered by going to an older firmware release.

[timg236]

While waiting for the USB boot to start working I'm running on an eMMC module in my Raspberry Pi 4.

pieeprom-2020-05-15.bin - USB mass storage boot beta

USB boot also requires updated firmware (start.elf)

I tried the upgrade to pieeprom-2020-05-15.bin even though the new start elf is not available. After that I could not boot from the eMMC module in the uSD-eMMC adaptor. Booting from a uSD-card worked fine for me with pieeprom-2020-05-15.bin, so I recovered by going to an older firmware release.

What brand is it? I've just tried a RasPiKey by UUGear and that seemed to work ok.

A screenshot of the HDMI diagnostics screen in the error state would be useful

[lingon]

The eMMC module is discussed in this thread: viewtopic.php?f=28&t=248157&hilit=emmc. It is this module: https://www.friendlyarm.com/index.php?r ... uct_id=249.

It got stuck on the rainbow screen without any diagnostics.

I flashed once more the USB beta release. Strangely I could see the HDMI diagnostic screen for brief moment, but then it got stuck on the rainbow screen. I cold booted a few times trying to see the diagnostic screen that flashed and suddenly it started booting?!

rpi-eeprom-update
BCM2711 detected
BOOTLOADER: up-to-date
CURRENT: Fri 15 May 2020 10:05:52 AM UTC (1589537152)
LATEST: Thu 16 Apr 2020 05:11:26 PM UTC (1587057086)
FW DIR: /lib/firmware/raspberrypi/bootloader/beta
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000137ad

[timg236]

The eMMC module is discussed in this thread: viewtopic.php?f=28&t=248157&hilit=emmc. It is this module: https://www.friendlyarm.com/index.php?r ... uct_id=249.

It got stuck on the rainbow screen without any diagnostics.

I flashed once more the USB beta release. Strangely I could see the HDMI diagnostic screen for brief moment, but then it got stuck on the rainbow screen. I cold booted a few times trying to see the diagnostic screen that flashed and suddenly it started booting?!

rpi-eeprom-update
BCM2711 detected
BOOTLOADER: up-to-date
CURRENT: Fri 15 May 2020 10:05:52 AM UTC (1589537152)
LATEST: Thu 16 Apr 2020 05:11:26 PM UTC (1587057086)
FW DIR: /lib/firmware/raspberrypi/bootloader/beta
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000137ad

Please could you try this potential firmware fix? It's a from a dev branch and is otherwise untested so please backup the card first!

release-b5de8c32.zip
https://drive.google.com/drive/folders/ ... sp=sharing

[lingon]

Is that link supposed to be public? I don't get the zip-file and the page prompts for a password.

[trejan]

Is that link supposed to be public? I don't get the zip-file and the page prompts for a password.

Works for me? Try again as timg236 may have fixed the permissions.

Code: Select all

release-b5de8c32.zip
11918566 bytes
SHA256 546A29B8F25844C406D00EBE5D02AC2F5FE50D1AC6CAF628C940E6EA358F4750

[timg236]

It's just a public Google drive share, it worked for me with Microsoft Edge and another browser without being signed into Google so I don't think it's a permission issue

[tofflock]

Is that link supposed to be public? I don't get the zip-file and the page prompts for a password.

Works for me too.
Right click on the big icon-looking image and it offers download near the bottom of the list.
It might then say "scanning for viruses", and then you'll get your browser window asking where you want to save it (if you've configured for a prompt when downloading.

If that doesn't work, restart your browser or reboot & try again.

HTH

PeterF

[lingon]

The download problem was due to too strict cookie settings. I installed that release and the Raspberry Pi 4 cold boots and reboots fine with it from the eMMC module.

vcgencmd version
Jun 3 2020 13:08:21
Copyright (c) 2012 Broadcom
version b5de8c32f4f45a12a1fdfe107254df82965f9d56 (clean) (release) (start)

Is there anything else I could test?

Would it be possible to get the eMMC speed up to DDR50 from 22.98 MB/sec reported by hdparm?

[timg236]

The download problem was due to too strict cookie settings. I installed that release and the Raspberry Pi 4 cold boots and reboots fine with it from the eMMC module.

vcgencmd version
Jun 3 2020 13:08:21
Copyright (c) 2012 Broadcom
version b5de8c32f4f45a12a1fdfe107254df82965f9d56 (clean) (release) (start)

Is there anything else I could test?

Would it be possible to get the eMMC speed up to DDR50 from 22.98 MB/sec reported by hdparm?

Thanks for testing.

It would useful if you could test hdmi_enable_4kp60=1 or core_freq=550 in config.txt because that's slightly more slightly to trigger a race condition.

Bootloader / start.elf performance is unlikely to get any better until the drivers are written to use the new SDHCI controller on 2711 (instead of legacy Aransan EMMC). On Linux the driver should be running at full speed but IIRC the DMA only works in the bottom 1 gigabyte of memory so you could be hitting bounce buffers in that test.

[hippy]

I could see the HDMI diagnostic screen for brief moment, but then it got stuck on the rainbow screen.

On that; would it be possible to add a 'hold diagnostics screen' timeout so one can see what it's done / selected if one doesn't have a a UART monitor to hand ?

It would also be nice if it were possible to have more lines of diagnostics shown on the display.