Open GrayHatGuy opened 7 months ago
I verified this by flashing a Bootloader update to SD card via Raspberry Imager and booting to update eeprom which successfully booted from external USB then I reversed the change updating the latest bootloader from Raspi-config using E1 - Latest to the eeprom and it reverted to factory and refused to boot to external USB.
@timg236
I can't see any difference in behaviour. Selecting Latest/Default uses the embedded EEPROM config from the file in lib/firmware which means the BOOT_ORDER will be blank and therefore default to 0xf41 which is the default SD followed by USB.
I can't see any difference in behaviour. Selecting Latest/Default uses the embedded EEPROM config from the file in lib/firmware which means the BOOT_ORDER will be blank and therefore default to 0xf41 which is the default SD followed by USB.
I could be experiencing other prevailing issues at minimum the menu text return after choosing either seems to indicate default eeproms were updated for both cases
I figured out my problem I had a bad usb to IDE/SATA cable causing intermittent disk rw issues. It does not appear to be eeprom confirmed by using USB thumb drives
When selecting options for bootloader version both E1 - Latest Use latest bootloader version and E2 - Default Use the factory default bootloader Return with message that default bootloader version has been installed to eeprom So E1 does not update to latest and both E1 and E2 return the bootloader to default