summaryrefslogtreecommitdiff
path: root/Documentation/mainboard
diff options
context:
space:
mode:
authorAngel Pons <th3fanbus@gmail.com>2019-10-24 19:37:50 +0200
committerNico Huber <nico.h@gmx.de>2019-12-13 17:33:06 +0000
commit5232eb1a108c945435b63723c3b53349faabc940 (patch)
tree1d1734e1f132032ca5eba239e0fd20b5e538dc3a /Documentation/mainboard
parent8b4528aae5ebe021d2cfbc3f1ee71360f01dd30c (diff)
downloadcoreboot-5232eb1a108c945435b63723c3b53349faabc940.tar.xz
Doc/mb/gigabyte/ga-h61m-s2pv: Correct IFD section
Change-Id: Ic94dd7381e9a107081011d083286d27005148557 Signed-off-by: Angel Pons <th3fanbus@gmail.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/36301 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: HAOUAS Elyes <ehaouas@noos.fr> Reviewed-by: Nico Huber <nico.h@gmx.de>
Diffstat (limited to 'Documentation/mainboard')
-rw-r--r--Documentation/mainboard/gigabyte/ga-h61m-s2pv.md20
1 files changed, 8 insertions, 12 deletions
diff --git a/Documentation/mainboard/gigabyte/ga-h61m-s2pv.md b/Documentation/mainboard/gigabyte/ga-h61m-s2pv.md
index 06c0ff7e89..84b72ce24b 100644
--- a/Documentation/mainboard/gigabyte/ga-h61m-s2pv.md
+++ b/Documentation/mainboard/gigabyte/ga-h61m-s2pv.md
@@ -39,27 +39,23 @@ leave the backup chip untouched.
The original IFD defines the BIOS region as the whole flash chip. While this is
not an issue if flashing a complete image, it confuses flashrom and trashes the
-flash chip's contents when using the --ifd option. However, this can be easily
-fixed by reading the IFD with flashrom, editing the correct values into it with
-ifdtool and then reflashing it.
-
-Create a layout.txt with the following contents:
+flash chip's contents when using the `--ifd` option. A possible workaround is
+to create a `layout.txt` file with a non-overlapping BIOS region:
00000000:00000fff fd
00180000:003fffff bios
00001000:0017ffff me
-After that, simply run:
+After that, use flashrom with the new layout file. For example, to create a
+backup of the BIOS region and then flash a `coreboot.rom`, do:
```bash
-sudo flashrom -p internal --ifd -i fd -r ifd.rom
-ifdtool -n layout.txt ifd.rom
-sudo flashrom -p internal --ifd -i fd -w ifd.rom.new
+sudo flashrom -p internal -l layout.txt -i bios -r backup.rom
+sudo flashrom -p internal -l layout.txt -i bios -w coreboot.rom
```
-After flashing, power cycle the computer to ensure the new IFD is being used.
-If only a reboot is done, the old IFD layout is still seen by flashrom, even if
-the IFD on the flash chip is correctly defining the new region layout.
+Modifying the IFD so that the BIOS region does not overlap would work as well.
+However, this makes DualBIOS unable to recover from a bad flash for some reason.
## Technology