From dffe1b0f1f43a113d454ccc74e89fee0ba73d0b3 Mon Sep 17 00:00:00 2001 From: Tim Gover Date: Wed, 26 Jan 2022 10:41:43 +0000 Subject: [PATCH] eeprom-erase: Add option to erase the SPI EEPROM --- eeprom-erase/README.md | 10 ++++++++++ eeprom-erase/bootcode4.bin | Bin 0 -> 89304 bytes eeprom-erase/config.txt | 2 ++ 3 files changed, 12 insertions(+), 0 deletions(-) create mode 100644 eeprom-erase/README.md create mode 100644 eeprom-erase/bootcode4.bin create mode 100644 eeprom-erase/config.txt diff --git a/eeprom-erase/README.md b/eeprom-erase/README.md new file mode 100644 index 0000000..cd22599 --- /dev/null +++ b/eeprom-erase/README.md @@ -0,0 +1,10 @@ +The `erase_eeprom` `config.txt` option causes `recovery.bin` to execute a chip-erase operation on the bootloader SPI EEPROM. +This is a test/debug option and there is no need to manually erase an EEPROM before flashing it. + +If the SPI EEPROM is erased then the Raspberry Pi will not boot until a new EEPROM image has been written via `RPIBOOT` +or the Raspberry Pi Imager (Pi4 and Pi400 only). + +```bash +cd erase-eeprom +../rpiboot -d . +``` diff --git a/eeprom-erase/bootcode4.bin b/eeprom-erase/bootcode4.bin new file mode 100644 index 0000000..b5f0a18 Binary files /dev/null and b/eeprom-erase/bootcode4.bin differ diff --git a/eeprom-erase/config.txt b/eeprom-erase/config.txt new file mode 100644 index 0000000..7fc4d21 --- /dev/null +++ b/eeprom-erase/config.txt @@ -0,0 +1,2 @@ +erase_eeprom=1 +uart_2ndstage=1 -- libgit2 0.21.4