Commit d49a1a2d72afcfc3e5fdaf2218975622b88bf5e1
Committed by
GitHub
GitHub
Merge pull request #113 from timg236/pieeprom-2022-01-25
Update bootloader to the latest stable release and use full SDRAM init in MSD / RAMDISK mode.
Showing
16 changed files
with
19 additions
and
5 deletions
eeprom-erase/README.md
0 → 100644
| 1 | +The `erase_eeprom` `config.txt` option causes `recovery.bin` to execute a chip-erase operation on the bootloader SPI EEPROM. | ||
| 2 | +This is a test/debug option and there is no need to manually erase an EEPROM before flashing it. | ||
| 3 | + | ||
| 4 | +If the SPI EEPROM is erased then the Raspberry Pi will not boot until a new EEPROM image has been written via `RPIBOOT` | ||
| 5 | +or the Raspberry Pi Imager (Pi4 and Pi400 only). | ||
| 6 | + | ||
| 7 | +```bash | ||
| 8 | +cd erase-eeprom | ||
| 9 | +../rpiboot -d . | ||
| 10 | +``` |
eeprom-erase/bootcode4.bin
0 → 100644
No preview for this file type
eeprom-erase/config.txt
0 → 100644
msd/bootcode4.bin
No preview for this file type
recovery/bootcode4.bin
No preview for this file type
recovery/pieeprom-2021-02-16.bin deleted
No preview for this file type
recovery/pieeprom-2021-06-14.bin deleted
No preview for this file type
recovery/pieeprom-2021-07-06.bin deleted
No preview for this file type
recovery/pieeprom-2021-11-22.bin deleted
No preview for this file type
recovery/pieeprom.bin
No preview for this file type
recovery/pieeprom.original.bin
No preview for this file type
recovery/pieeprom.sig
secure-boot-msd/bootcode4.bin
No preview for this file type
secure-boot-recovery/README.md
| @@ -51,7 +51,7 @@ cd secure-boot-recovery | @@ -51,7 +51,7 @@ cd secure-boot-recovery | ||
| 51 | ../tools/update-pieeprom.sh -k "${KEY_FILE}" | 51 | ../tools/update-pieeprom.sh -k "${KEY_FILE}" |
| 52 | ``` | 52 | ``` |
| 53 | 53 | ||
| 54 | -`pieeprom.bin` can then be flashed to the bootloader EEPROM via rpiboot. | 54 | +`pieeprom.bin` can then be flashed to the bootloader EEPROM via `rpiboot`. |
| 55 | 55 | ||
| 56 | ## Program the EEPROM image using rpiboot | 56 | ## Program the EEPROM image using rpiboot |
| 57 | * Power off CM4 | 57 | * Power off CM4 |
| @@ -72,9 +72,11 @@ onwards: | @@ -72,9 +72,11 @@ onwards: | ||
| 72 | * The EEPROM configuration file must be signed with the customer private key. | 72 | * The EEPROM configuration file must be signed with the customer private key. |
| 73 | * It is not possible to install an old version of the bootloader that does | 73 | * It is not possible to install an old version of the bootloader that does |
| 74 | support secure boot. | 74 | support secure boot. |
| 75 | -* **It is NOT possible to use a different private key to signed the OS images** | 75 | +* This option requires EEPROM version 2022-01-06 or newer. |
| 76 | +* BETA bootloader releases are not signed with the ROM secure boot key and will | ||
| 77 | + not boot on a system where `revoke_devkey` has been set. | ||
| 76 | 78 | ||
| 77 | -**WARNING: THESE OPTIONS PERMANENTLY THE BCM2711 CHIP AND ARE IRREVERSIBLE.** | 79 | +**WARNING: Modifications to OTP are irreversible. Once `revoke_devkey` has been set it is not possible to unlock secure-boot mode or use a different private key.** |
| 78 | 80 | ||
| 79 | To enable this edit the `config.txt` file in this directory and set | 81 | To enable this edit the `config.txt` file in this directory and set |
| 80 | `program_pubkey=1` | 82 | `program_pubkey=1` |
secure-boot-recovery/bootcode4.bin
No preview for this file type
secure-boot-recovery/pieeprom.original.bin
No preview for this file type