From 806fbb0834b4b7d871a4f456948f24fa97dfc86d Mon Sep 17 00:00:00 2001 From: Chase <126499565+WildPuppyWin@users.noreply.github.com> Date: Mon, 6 Nov 2023 16:54:35 -0600 Subject: [PATCH 1/3] Update compiling-coreboot.md --- docs/compiling-coreboot.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/compiling-coreboot.md b/docs/compiling-coreboot.md index 8c647b00..06ded23d 100644 --- a/docs/compiling-coreboot.md +++ b/docs/compiling-coreboot.md @@ -30,10 +30,11 @@ Building and flashing your own firmware has the potential to brick your device. * For example, `./build-uefi.sh leona` * Roms will be stored in `~/dev/firmware` 6. **Download flashrom, then give it execute permission.** - * `cd; curl -LO https://elly.rocks/tmp/coreboot-development/flashrom-alderlake; chmod +x flashrom-alderlake` + * `cd; curl -LO https://tree123.org/chrultrabook/utils/flashrom-libpci38; chmod +x flashrom-libpci38` 7. **Flash your custom ROM** - * Backup your current rom, just in case things go wrong: `./flashrom-alderlake -p internal -r current.rom` - * Flash your custom firmware: `sudo ./flashrom-alderlake -p internal -w ~/dev/firmware/coreboot_edk2--mrchromebox_.rom` + * Note: Intel boards should be flashed with `--ifd -i bios` + * Backup your current rom, just in case things go wrong: `./flashrom-libpci38 -p internal -r current.rom` + * Flash your custom firmware: `sudo ./flashrom-libpci38 -p internal -w ~/dev/firmware/coreboot_edk2--mrchromebox_.rom` 8. **Reboot** * Assuming it said `success` on all checks, reboot. From 141b6fd8de636f7f747993f8b104437910379b17 Mon Sep 17 00:00:00 2001 From: Chase <126499565+WildPuppyWin@users.noreply.github.com> Date: Mon, 6 Nov 2023 16:57:45 -0600 Subject: [PATCH 2/3] Update compiling-coreboot.md --- docs/compiling-coreboot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/compiling-coreboot.md b/docs/compiling-coreboot.md index 06ded23d..b7d6e054 100644 --- a/docs/compiling-coreboot.md +++ b/docs/compiling-coreboot.md @@ -32,7 +32,7 @@ Building and flashing your own firmware has the potential to brick your device. 6. **Download flashrom, then give it execute permission.** * `cd; curl -LO https://tree123.org/chrultrabook/utils/flashrom-libpci38; chmod +x flashrom-libpci38` 7. **Flash your custom ROM** - * Note: Intel boards should be flashed with `--ifd -i bios` + * Note: Intel Chromebooks should be flashed with `--ifd -i bios` * Backup your current rom, just in case things go wrong: `./flashrom-libpci38 -p internal -r current.rom` * Flash your custom firmware: `sudo ./flashrom-libpci38 -p internal -w ~/dev/firmware/coreboot_edk2--mrchromebox_.rom` 8. **Reboot** From cc5bddb65513620f9dd93a9e711af156ff418171 Mon Sep 17 00:00:00 2001 From: Chase <126499565+WildPuppyWin@users.noreply.github.com> Date: Mon, 6 Nov 2023 18:26:53 -0600 Subject: [PATCH 3/3] Update compiling-coreboot.md --- docs/compiling-coreboot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/compiling-coreboot.md b/docs/compiling-coreboot.md index b7d6e054..5bd7221d 100644 --- a/docs/compiling-coreboot.md +++ b/docs/compiling-coreboot.md @@ -32,7 +32,7 @@ Building and flashing your own firmware has the potential to brick your device. 6. **Download flashrom, then give it execute permission.** * `cd; curl -LO https://tree123.org/chrultrabook/utils/flashrom-libpci38; chmod +x flashrom-libpci38` 7. **Flash your custom ROM** - * Note: Intel Chromebooks should be flashed with `--ifd -i bios` + * Note: Intel Chromebooks should be flashed with `--ifd -i bios` ex: `sudo ./flashrom -p internal --ifd -i bios -w coreboot.rom` * Backup your current rom, just in case things go wrong: `./flashrom-libpci38 -p internal -r current.rom` * Flash your custom firmware: `sudo ./flashrom-libpci38 -p internal -w ~/dev/firmware/coreboot_edk2--mrchromebox_.rom` 8. **Reboot**