Commit 5f5ba38236c0bba621a38c86b3acd8e07753925d
Committed by
GitHub
GitHub
Merge pull request #136 from timg236/bootcode4-no-memsys
msd: Fix support for older EEPROM release in on 2711
Showing
2 changed files
with
2 additions
and
0 deletions
Readme.md
| @@ -76,6 +76,8 @@ via RPIBOOT on Compute Module 4. | @@ -76,6 +76,8 @@ via RPIBOOT on Compute Module 4. | ||
| 76 | | [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 | | 76 | | [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 | |
| 77 | | [secure-boot-example](secure-boot-example/README.md) | Simple Linux initrd with a UART console. | 77 | | [secure-boot-example](secure-boot-example/README.md) | Simple Linux initrd with a UART console. |
| 78 | 78 | ||
| 79 | +** 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` ** | ||
| 80 | + | ||
| 79 | ## Booting Linux | 81 | ## Booting Linux |
| 80 | The `RPIBOOT` protocol provides a virtual file-system to the Raspberry Pi bootloader and GPU firmware. It's therefore possible to | 82 | The `RPIBOOT` protocol provides a virtual file-system to the Raspberry Pi bootloader and GPU firmware. It's therefore possible to |
| 81 | boot Linux. To do this, you will need to copy all of the files from a Raspberry Pi boot partition plus create your own | 83 | boot Linux. To do this, you will need to copy all of the files from a Raspberry Pi boot partition plus create your own |
msd/bootcode4.bin
No preview for this file type