Hello Image may be NSFW.
Clik here to view.
The Goal: Boot Raspberry Pi directly from an SanDisk SSD Plus
The Problem: Unable to enable USB Boot
The Work: A Raspberry Pi 4 Model B is attempting to run a SanDisk SSD Plus. However, there is an issue with enabling USB Boot.
On this device, the current version of raspi-config is Version: 20231012~bullseye. When attempting to enable USB Boot the following error is produced, "No EEPROM bin file found for version 2023-05-11 - aborting."
That said, after running 'sudo rpi-update', the following is produced:
'
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** Performing self-update
*** Relaunching after update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
FW_REV:5f514b4bfbe5bbd2fe020447886c10a035dd9028
BOOTLOADER_REV:8855da988935f0c09ed4cc772103d4c5408a1afb
rpi-eeprom firmware package appears to be too old. Skipping bootloader updates
WANT_32BIT:1 WANT_64BIT:1 WANT_PI4:1 WANT_PI5:0
#############################################################
WARNING: This update bumps to rpi-6.1.y linux tree
See: viewtopic.php?t=344246
'rpi-update' should only be used if there is a specific
reason to do so - for example, a request by a Raspberry Pi
engineer or if you want to help the testing effort
and are comfortable with restoring if there are regressions.
DO NOT use 'rpi-update' as part of a regular update process.
##############################################################
Would you like to proceed? (y/N)
'
To update the "old" rpi-eeprom firmware package, in order to execute bootloader updates, the following command was run:
'
sudo rpi-eeprom-update -a
'
The output:
'
BOOTLOADER: up to date
CURRENT: Thu 11 May 2023 06:26:03 AM UTC (1683786363)
LATEST: Thu 11 May 2023 06:26:03 AM UTC (1683786363)
RELEASE: stable (/lib/firmware/raspberrypi/bootloader/stable)
Use raspi-config to change the release.
VL805_FW: Using bootloader EEPROM
VL805: up to date
CURRENT: 000138c0
LATEST: 000138c0
'
The BOOTLOADER is apparently up to date. Does anyone have a solution?
Clik here to view.
The Goal: Boot Raspberry Pi directly from an SanDisk SSD Plus
The Problem: Unable to enable USB Boot
The Work: A Raspberry Pi 4 Model B is attempting to run a SanDisk SSD Plus. However, there is an issue with enabling USB Boot.
On this device, the current version of raspi-config is Version: 20231012~bullseye. When attempting to enable USB Boot the following error is produced, "No EEPROM bin file found for version 2023-05-11 - aborting."
That said, after running 'sudo rpi-update', the following is produced:
'
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** Performing self-update
*** Relaunching after update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
FW_REV:5f514b4bfbe5bbd2fe020447886c10a035dd9028
BOOTLOADER_REV:8855da988935f0c09ed4cc772103d4c5408a1afb
rpi-eeprom firmware package appears to be too old. Skipping bootloader updates
WANT_32BIT:1 WANT_64BIT:1 WANT_PI4:1 WANT_PI5:0
#############################################################
WARNING: This update bumps to rpi-6.1.y linux tree
See: viewtopic.php?t=344246
'rpi-update' should only be used if there is a specific
reason to do so - for example, a request by a Raspberry Pi
engineer or if you want to help the testing effort
and are comfortable with restoring if there are regressions.
DO NOT use 'rpi-update' as part of a regular update process.
##############################################################
Would you like to proceed? (y/N)
'
To update the "old" rpi-eeprom firmware package, in order to execute bootloader updates, the following command was run:
'
sudo rpi-eeprom-update -a
'
The output:
'
BOOTLOADER: up to date
CURRENT: Thu 11 May 2023 06:26:03 AM UTC (1683786363)
LATEST: Thu 11 May 2023 06:26:03 AM UTC (1683786363)
RELEASE: stable (/lib/firmware/raspberrypi/bootloader/stable)
Use raspi-config to change the release.
VL805_FW: Using bootloader EEPROM
VL805: up to date
CURRENT: 000138c0
LATEST: 000138c0
'
The BOOTLOADER is apparently up to date. Does anyone have a solution?
Statistics: Posted by T3Crypto — Wed Jan 10, 2024 1:44 am