-
Fix a secure boot failure when booting from MMC (but not RPIBOOT)
-
Also make the secure-boot-recovery pieeprom.original.bin a symlink to ../pieeprom.original.bin. There's no need to have different binaries so remove duplication.
-
See https://github.com/raspberrypi/usbboot/issues/116
-
The previous version would fail to boot if secure-boot mode was locked via OTP settings.
-
The MSD (and secure-boot variant) bootloader has been updated to fully initialise SDRAM in order to resolve problems when using this method to run Linux ramdisks / initrd. Therefore, MSD boot will not work on a system with a blank or corrupted EEPROM. If so, an error message will be output to the UART and the EEPROM should be programmed using the recovery option.
-
Select the latest, stable bootloader EEPROM release which supports NVMe. Update start4.elf (USB MSD firmware) to top-of-tree.
-
The manufacuring image now enables SELF_UDPATE and NETWORK boot by default in order to make the initial setup for CM4 based products easier. For embedded or physically inaccessible products the bootloader should be updated to disable self-update. Hardware write-protection should also be configured. The symlink from pieeprom-2021-02-16 to pieeprom.original.bin has been replaced with a simple copy of the file because the Windows installer doesn't seem to support symlinks.
-
* Update the EEPROM image to the latest/stable release. * Change the default boot-order to 0xf541 so that USB MSD will boot from the type-A sockets on the CM4 IO board. * Add simple update-pieeprom.sh utility with latest rpi-eeprom-config to make it easier to refresh the EEPROM image with a new configuration.