erebion/coreboot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Documentation: Update documentation for Topton X2F-N100

Browse source 
- Clean up section on flashrom vs flashprog
- Clarify flash regions and command used to flash `bios` region only
- Specify command used for external flashing

Change-Id: Icf464f4532b956731040fed97da0726856524c16
Signed-off-by: Matt DeVillier <matt.devillier@gmail.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/87507
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Felix Held <felix-coreboot@felixheld.de>
This commit is contained in:
Matt DeVillier 2025-05-01 16:38:43 -05:00
commit 0b120de7c0
1 changed files with 16 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

28
Documentation/mainboard/topton/adl/x2f-n100.md
View file

@ -28,26 +28,26 @@ Doing so **may kill your device**. You have been warned :)
### Internally ### Internally
Vendor of this motherboard hasn't locked any flash regions, resulting Vendor of this motherboard hasn't locked any flash regions, resulting
in [flashprog] having full access to the SPI chip. in internal programmers such as [flashrom]/[flashprog] having full access
Assuming that user had booted Linux with `iomem=relaxed`, they can: to the SPI chip. Assuming that user had booted Linux with `iomem=relaxed`,
they can:
- Flash coreboot from stock firmware - Flash coreboot from stock firmware
- Flash stock firmware from coreboot - Flash stock firmware from coreboot
- Update coreboot build to a newer version - Update coreboot build to a newer version
Without opening the case and connecting the SPI flasher. Without opening the case and connecting the SPI flasher.
Please note that for AlderLake-N platform you will need to use Note: some users have reported bricked devices when using [flashrom] to
[flashprog] v1.3.0 or newer. flash the board, so the current recommendation is to use [flashprog]
v1.3.0 or newer.
[flashrom] is broken due to regressions, which results in Since we only need to flash the `bios` region of the flash chip, there is
failed flashes, bricking the device. no need to extract the `ifd` or `me` regions from your backup of the stock
firmware. One can flash the `bios` region only using the following command:
`flashprog -p internal --ifd -i bios -w ./build/coreboot.rom -N`
[flashprog] is a better maintained fork of [flashrom], which The `-N` tells [flashprog`] to skip verification on the other regions of the
works flawlessly. flash chip which are not being written.
You can skip extracting `SI_BIOS` and `SI_ME` regions from your ROM
and flash coreboot to `SI_BIOS` region by issuing the following command:
`flashprog -p internal --ifd -i SI_BIOS -w ./build/coreboot.rom`
### Externally ### Externally
@ -57,6 +57,10 @@ Please note that SPI voltage on this board is standard 3.3V, despite
using mobile SoC. using mobile SoC.
Vendor populated this board with Winbond W25Q128JV chip in SOIC-8 package. Vendor populated this board with Winbond W25Q128JV chip in SOIC-8 package.
Flashing coreboot using an external programmer is exactly the same as
using an internal programmer, other than the `programmer` argument:
`flashprog -p <programmer> --ifd -i bios -w ./build/coreboot.rom -N`
## Functionality ## Functionality
### Tested and working ### Tested and working