From cc72bc01ac31e568612b8400e4eab56f788b51fd Mon Sep 17 00:00:00 2001 From: Tim Gover Date: Wed, 4 May 2022 20:58:36 +0100 Subject: [PATCH] msd: Fix support for older EEPROM release in on 2711 --- Readme.md | 2 ++ msd/bootcode4.bin | Bin 105980 -> 0 bytes 2 files changed, 2 insertions(+), 0 deletions(-) diff --git a/Readme.md b/Readme.md index 7e6bfe1..749eba9 100644 --- a/Readme.md +++ b/Readme.md @@ -76,6 +76,8 @@ via RPIBOOT on Compute Module 4. | [secure-boot-msd](secure-boot-msd/README.md) | Scripts for signing the MSD firmware so that it can be used on a secure-boot device | | [secure-boot-example](secure-boot-example/README.md) | Simple Linux initrd with a UART console. +** The `secure-boot-msd`, `rpi-imager-embedded` and `mass-storage-gadget` extensions require that the `2022-04-26` (or newer) bootloader EEPROM release has already been written to the EEPROM using `recovery.bin` ** + ## Booting Linux The `RPIBOOT` protocol provides a virtual file-system to the Raspberry Pi bootloader and GPU firmware. It's therefore possible to boot Linux. To do this, you will need to copy all of the files from a Raspberry Pi boot partition plus create your own diff --git a/msd/bootcode4.bin b/msd/bootcode4.bin index e31e21e..18a22a0 100644 Binary files a/msd/bootcode4.bin and b/msd/bootcode4.bin differ -- libgit2 0.21.4