Just a quick question - I have masked the rpi-eeprom-update service, so the update files aren't removed on reboot. Does this mean they're applied every single time I boot? If the bootloader sees a pieeprom.upd or vl805.bin file then it will read them and compare them to the current images. If there...
Just a quick question - I have masked the rpi-eeprom-update service, so the update files aren't removed on reboot. Does this mean they're applied every single time I boot?
My best guess is that the update isn't actually happening and then upon reboot the temporary update files are removed by the rpi-eeprom-update service.
You're quite right, I checked again and if I reboot twice after changing the settings, the new boot sequence is finally applied!
It sounds like you may have gotten the EEPROM image via a different route. Different distro? Nope, I'm running raspbian, and I followed the instructions on the bootloader page to switch to the beta branch and update from there. As I said, the dumped config stated a boot priority of 0xF41 but this w...
It sounds like you may have gotten the EEPROM image via a different route. Different distro? Nope, I'm running raspbian, and I followed the instructions on the bootloader page to switch to the beta branch and update from there. As I said, the dumped config stated a boot priority of 0xF41 but this w...
Just a small detail but using the EEPROM image from 15/05/20 I initially couldn't get USB booting to work, because the boot order was 0xF21 instead of 0xF41 as described on the bootload configuration page. However, dumping the config to a text file, the boot order was listed as 0xF41. Rewriting the ...
https://www.tomshardware.co.uk/raspberry-pi-4-everything-we-know,news-59876.html I'm half expecting to get shot down in flames for saying this, but please believe me when I say beforehand that I've had tons of use out of the various models of Raspberry Pi that I've bought over the years (about 10 d...