Rpi4 < $(community_build)

Community Builds, Projects & Packages
1081

good question...

verbage

the built in command;

rpi4_eeprom.sh update #dont run, read below first

just tested it now...

  • is tied to a specific githash... (current as of today)

  • this is kinda good because I'd prefer not to have to troubleshoot devices when testing eeproms are user installed... I need to stay a month or so behind the curve minimum once newer eeproms are released until a few users test out eeproms and report back benefits / problems

NOTE:
future users with CM4+emmc should consult rpi-documentation carefully

if you go to; luci > system > custom commands [rpisupport]

and type in;

eeprom-update

(to use recommended version then reboot)

special-hash-provisions 
eeprom-update 34b752e8be6ba41f27f0348a9711107946150c9a
(possibly on first run only... have not tested this recently after I changed a fair bit of script logic)

it should fetch that (your chosen) more recent hash to work from if a newer one becomes available in the future you wish to test...

command line equivalent

/bin/rpi4_eeprom.sh fetch <HASH> #not needed if you want to use recommended version
/bin/rpi4_eeprom.sh update
reboot
alternatives

the alternatives are;

  • use a raspbian sdcard
  • or use a blank fat32 sdcard with just the update files
  • the typical 'vcgencmd' commands as listed in all the raspberrypi documents all function on OpenWrt...
  • 'rpi-support.sh' will also show you firmware information (or just click run in luci)
2 Likes