Rpi4 - Bootloader/Firmware Upgrade. It's safe and suggested procedure ?

DjDiabolik

I need to explain the situation:
I have a Rpi4, about five minutes ago i do the periodically check for upgrade/update by retropie_setup including all component like kernel and os.
Apparently all update it's be updated correctly...... during the very first kernel update i have noticed this update:

Calculating upgrade...
The following packages will be upgraded:
  rpi-eeprom

According to some information founded by google this is component for bootloader/firmware of my Rpi4.
But it's not really the bootloader but it's related to the component to update them...

It's correct ?

I have also made other "investigation" over internet and founded a lot of guide... one of them:
https://pimylifeup.com/raspberry-pi-bootloader/

It's contain a part to updating the bootloader by terminal...... i hope i can open SSH from my PC.

Try to run this:

sudo rpi-eeprom-update

The result from my Rpi4 it's that:

*** UPDATE AVAILABLE ***
BOOTLOADER: update available
   CURRENT: Thu  3 Sep 12:11:43 UTC 2020 (1599135103)
    LATEST: Wed  7 Dec 14:24:15 UTC 2022 (1670423055)
   RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
            Use raspi-config to change the release.

  VL805_FW: Dedicated VL805 EEPROM
     VL805: up to date
   CURRENT: 000138a1
    LATEST: 000138a1

Current i see 3 Sep 2020......... latest stable it's 7 Dec 2022.......

Now the question it's:
The same guide contain a procedure to do by SSH or also by using raspi-config.

I have try to found by google some result like "retropie bootloader upgrade" or "retropie bootloader update" but apparently i can't found thread or other similar.

The question it's:

It's safe to update ?
It's suggested to update bootloader on my current (and working good) retropie setup ?
After update i can risk my Pi4 not boot good retropie because current bootloader it's custom or somethigs similar ?

It's someone has tryed to do this ?
It's works ?

Thanks for every info........

EDIT
I have to add a thread found here:
https://retropie.org.uk/forum/topic/33148/a-new-way-to-install-retropie

Contain info about bootloader updgrade but not contain if it's safe or info how i can updgrade it :)

mitu

The procedure to upgrade the EEPROM bootloader is described in https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#raspberry-pi-4-boot-eeprom. The bootloader is updated automatically when needed, so you don't have to do anything manually.
What you see as an 'upgrade' is from release branch of the bootloader, but by default the rpi-eeprom service will upgrade automatically if any critical updates are released - see https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#bootloader-release.

In short, don't bother manually upgrading unless you need a feature from the release or beta branches. The rpi-eeprom service will apply any EEPROM or USB controller firmware upgrades when needed.

DjDiabolik

@mitu mmmmmmmm...
speaking about the official documentation.....

pi@retropie:~ $ vcgencmd bootloader_version
Sep  3 2020 13:11:43
version c305221a6d7e532693cc7ff57fddfc8649def167 (release)
timestamp 1599135103
update-time 0
capabilities 0x00000000

So apparently i don't have particularry issue on my setup.... but usually i like to maintain all my devices updated to current stable release and is some cases (expecially on my windows PC) i also uses some BETA app or similar :)

so you're telling me the LATEST Bootloader dated 7 December 2022 it's a BETA ?
And the current stable it's the 3 Sep 2020 currently installed ?

I don't have need to update then manually by run "rpi-eeprom-update -a " how it's suggested also on official guide ?

DjDiabolik

@mitu another problably general question about bootloader.

Apparently here it's can be found some info about release history:

https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/release-notes.md

So if the "service" rpi-eeprom will upgrade automatically the bootloader because on my current it's "stuck" at release of 7 Sept 2020 ?

Apparently the 7-12-2022 and the 18-01-2023 it's be "promoted" as default and also as stable.
shouldn't I have already found them installed/upgraded in my pi4 ?

mitu

@DjDiabolik said in Rpi4 - Bootloader/Firmware Upgrade. It's safe and suggested procedure ?:

Apparently the 7-12-2022 and the 18-01-2023 it's be "promoted" as default and also as stable.
shouldn't I have already found them installed/upgraded in my pi4 ?

No.

As I said in my previous reply (and it's also explained in the linked documentation), rpi-eeprom will do the upgrade only if a critical release is added (not a stable one). If you'd like to follow the stable release channel (instead of critical), you can do so from raspi-config (also explained in the linked documentation).

DjDiabolik

@mitu said in Rpi4 - Bootloader/Firmware Upgrade. It's safe and suggested procedure ?:

@DjDiabolik said in Rpi4 - Bootloader/Firmware Upgrade. It's safe and suggested procedure ?:

Apparently the 7-12-2022 and the 18-01-2023 it's be "promoted" as default and also as stable.
shouldn't I have already found them installed/upgraded in my pi4 ?

No.

As I said in my previous reply (and it's also explained in the linked documentation), rpi-eeprom will do the upgrade only if a critical release is added (not a stable one). If you'd like to follow the stable release channel (instead of critical), you can do so from raspi-config (also explained in the linked documentation).

Yeah it's problably english my very first contender :)

I have look your link to official documentation...... i have understand the bootloader release it's related to Three different way:
DEFAULT
LATEST
and BETA.

If i understand correctly current configuration on Retropie we follow the DEFAULT "branch".
up to here is it right?

Now i have see my Pi4 have the build dated 3 Sept 2020......
If we follow the release-notes.md apparently after this date in theory there are at least two or three versions released as "critical".
that apparently it's the current installed:
https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/release-notes.md#2020-09-14-promote-the-2020-09-03-release-to-be-the-default-eeprom-images

For example that:
https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/release-notes.md#2021-02-22---promote-2021-02-16-to-stable---stable-latest

It's be not released as critical ? and should have it installed automatically in the background then ?

I don't understand the really difference between default and critial... on official it's specified:



N.B. default and latest are symbolic links to the older release names of critical and stable.

So critial = default and latest = stable........ but at this point what's the very last released as "critical" ?

DjDiabolik

@mitu

I don't have idea if you had the chance... But since you've explained the question a bit, I think it's only fair to update you about this my "adventure".

For my personal and addictional knowledge i have try to made a similar question also on raspberrypi official forum.

After the very first reply they explained to me that:
Current Retropie prebuild SD image it's based on a Raspberry Pi OS Buster ok ?
After some research apparently Raspbian Buster it's considered as "Legacy" from about 2021. practically after the release of Bullseye.

After that on Raspberry Pi Buster it's not anymore maintained for OS upgrade but it's granteed only update for security.
Also for Booloader....... the service to maintain bootloader it's not anymore granteed on Rpi OS Buster.

For a coincidence i have also look at my Amazon order history.
I have found info of my Pi4 order...... i have received at my home exactly the 11 Febbruary 2021.
Problably i never received an automatic update for bootloader because.... from my very first time i have boot Retropie on my Pi4 the service for autoupdate that it's not anymore granteed :)

At this point they linked me to a very convenient tools...... that:
https://forums.raspberrypi.com/viewtopic.php?t=283347

It's a great tools....... simply need to extract it:
/home/pi

need to make it executable whit "sudo chmod +x"

After that run it:

from my keyboard attach to my Pi4....... Press F4 to open terminal
run "sudo ./rpi-eeprom-mgr"
From menù launch second voice.......
After the tools show a choice...... very large list of a lot version of Bootloader.... from the list it's also show as STABLE the build dated 11-01-2023.
I have choose it
Choose to reset to default the bootloader option
Confirm to update EEPROM.

After that...... after about i see my Raspberry made a reboot.......

About 30 seconds and Retropie LOGO re-appears on my TV!!!

Apparently all works flawlessy........... if i now open the tools again i can see this:
alt text

Now my bootloade it's UPDATED........... to the very last stable release.

EDIT
Moreover.. github folder "default" it's symlink to "critical" folder. So current 11-01-2023 it's last, default, and released as critical update.
the only mystery is why this release is not seen by current rpi-eeprom-update.

But it's not anymore my trouble...... now i'm updated :)

DjDiabolik

@mitu

Only as purely information:

Yesterday i have turned on my Pi4 for pass some hours on retrogaming.
I do my usually and periodicy check for update by retropie_setup including the kernel and os update.

During that i have noticied another update to components rpi-eeprom....... this time, if correct, as version 16.x.

When all update it's completed, exited from retropie_setup and back to emulationstation i have open the terminal whit F4 and i have tryed to check the status of eeprom by command:

sudo rpi-eeprom-update

Immediatelly after that i have noticed there's an update on side VL805 in pending.....
I don't have touch anythings...... i'm not triggered this update manually how i have do whit the booloader side.

I thinks, in someway, the autoupdate service it's now works.........

From same Terminal i have do:

sudo reboot

Waited my Pi4 reboot whiout any issue...... and now by Bootloader and VL805 as been update to current and last stable release.

I think they fixed that.... because, in the pass, although there were updates it seemed to skip them.