-
Reduce the size of the windows installer by removing the optional components. It will now just contain the MSD firmware drive, the new mass-storage gadget (for writing NVMe) and the recovery. The optional components including secure-boot-example and the Raspberry Pi Image can be downloaded from Github without rebuilding this installer. Add a helper batch file and shortcut for launching the mass-storage-gadget.
-
This also resolve a startup issue CM4-S
-
Include the new imager applications and fix the recursive File operations to stop the installer pulling in the .git directory.
-
Initial BETA release for secure-boot. secure-boot adds two new sub-directory to usbboot: * secure-boot-recovery is used to create an EEPROM signed with the customer's RSA private key and configures the 2711 OTP settings permenantely require signed boot images. See secure-boot-recovery/README.md * Once secure-boot is enabled the CM4 MSD mode firmware must also be signed with the customer's RSA private key. See secure-boot-msd/README.md N.B The revoke_devkey and program_jtag_lock are NOT enabled in this initial BETA release.
-
Update this binary to the latest. Also rebuilt the windows installer
-
Select the latest, stable bootloader EEPROM release which supports NVMe. Update start4.elf (USB MSD firmware) to top-of-tree.
-
Update bootcode4.bin to avoid some blocking operations which can cause USB errors.
-
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.
-
Also add extra logging to indicate where the file was loaded from to make it more obvious where a file is loaded from. Update Windows installer
-
* Add 2711 bootcode and FW binaries with the 4 suffix. * Use the device descriptor to select the correct bootcode and hack it so that bootcode.bin translates to bootcode4.bin on a Pi4 allowing the files to remain in the same directory. * Add the latest best for recovery.bin and pieeprom.bin for CM4 * Update the installer. Move the second stage preparation until after the device descriptor has been retrieved because BCM2711 needs a different bootcode.bin. If the '-d' argument specified then check for bootcode.bin in the specified directory and don't fail over to the embedded fmem files. Remove the default 'msd' directory and the references to /usr/share because the behaviour conflicts with the original change to use the fmem files.
