Documentation: Move firmware flashing tutorial to tutorial section

There is no need that the tutorial for flashing firmware has its own
point in the main menu. Thus, move it to the tutorial section.

Change-Id: Ife6d97254af4c006fe01480a78c76303f9cb34bb
Signed-off-by: Felix Singer <felixsinger@posteo.net>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/62424
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Thomas Heijligen <src@posteo.de>
This commit is contained in:
Felix Singer 2022-02-27 22:27:17 +01:00
parent c664056c56
commit d55fa332d8
32 changed files with 26 additions and 26 deletions

View File

@ -260,7 +260,7 @@ questions.
[mailing list]: https://mail.coreboot.org/postorius/lists/coreboot.coreboot.org [mailing list]: https://mail.coreboot.org/postorius/lists/coreboot.coreboot.org
[Getting started]: ../getting_started/index.md [Getting started]: ../getting_started/index.md
[Tutorial]: ../tutorial/index.md [Tutorial]: ../tutorial/index.md
[Flashing firmware tutorial]: ../flash_tutorial/index.md [Flashing firmware tutorial]: ../tutorial/flashing_firmware/index.md
[Coding style]: coding_style.md [Coding style]: coding_style.md
[Code of Conduct]: ../community/code_of_conduct.md [Code of Conduct]: ../community/code_of_conduct.md
[Language style]: ../community/language_style.md [Language style]: ../community/language_style.md

View File

@ -190,4 +190,3 @@ Contents:
* [Utilities](util.md) * [Utilities](util.md)
* [coreboot infrastructure](infrastructure/index.md) * [coreboot infrastructure](infrastructure/index.md)
* [Release notes](releases/index.md) * [Release notes](releases/index.md)
* [Flashing firmware tutorial](flash_tutorial/index.md)

View File

@ -124,7 +124,7 @@ $ sudo flashrom \
```eval_rst ```eval_rst
In addition to the information here, please see the In addition to the information here, please see the
:doc:`../../flash_tutorial/index`. :doc:`../../tutorial/flashing_firmware/index`.
``` ```
### External flashing ### External flashing

View File

@ -58,7 +58,7 @@ The main SPI flash can be accessed using [flashrom]. By default, only
the BIOS region of the flash is writable. If you wish to change any the BIOS region of the flash is writable. If you wish to change any
other region, such as the Management Engine or firmware descriptor, then other region, such as the Management Engine or firmware descriptor, then
an external programmer is required (unless you find a clever way around an external programmer is required (unless you find a clever way around
the flash protection). More information about this [here](../../flash_tutorial/index.md). the flash protection). More information about this [here](../../tutorial/flashing_firmware/index.md).
### External programming ### External programming

View File

@ -115,7 +115,7 @@ region is not readable even by the host.
```eval_rst ```eval_rst
In addition to the information here, please see the In addition to the information here, please see the
:doc:`../../flash_tutorial/index`. :doc:`../../tutorial/flashing_firmware/index`.
``` ```
## Hardware monitoring and fan control ## Hardware monitoring and fan control

View File

@ -130,5 +130,5 @@ You can also control the CPU fan with similar rules:
echo 2000 >/sys/class/hwmon/hwmon2/pwm1_tolerance echo 2000 >/sys/class/hwmon/hwmon2/pwm1_tolerance
[ASUS P5Q]: https://www.asus.com/Motherboards/P5Q [ASUS P5Q]: https://www.asus.com/Motherboards/P5Q
[this guide]: ../../flash_tutorial/int_flashrom.md [this guide]: ../../tutorial/flashing_firmware/int_flashrom.md
[kernel docs]: https://www.kernel.org/doc/Documentation/hwmon/w83627ehf.rst [kernel docs]: https://www.kernel.org/doc/Documentation/hwmon/w83627ehf.rst

View File

@ -142,7 +142,7 @@ Built gigabyte/ga-g41m-es2l (GA-G41M-ES2L)
```eval_rst ```eval_rst
In addition to the information here, please see the In addition to the information here, please see the
:doc:`../../flash_tutorial/index`. :doc:`../../tutorial/flashing_firmware/index`.
``` ```
### Do backup ### Do backup

View File

@ -94,6 +94,6 @@ Schematic of this laptop can be found on [Lab One].
[HP EliteBook 2560p]: https://support.hp.com/us-en/product/hp-elitebook-2560p-notebook-pc/5071201 [HP EliteBook 2560p]: https://support.hp.com/us-en/product/hp-elitebook-2560p-notebook-pc/5071201
[Maintenance and Service Guide]: http://h10032.www1.hp.com/ctg/Manual/c03011618 [Maintenance and Service Guide]: http://h10032.www1.hp.com/ctg/Manual/c03011618
[flashing tutorial]: ../../flash_tutorial/ext_power.md [flashing tutorial]: ../../tutorial/flashing_firmware/ext_power.md
[Lab One]: https://www.laboneinside.com/hp-elitebook-2560p-schematic-diagram/ [Lab One]: https://www.laboneinside.com/hp-elitebook-2560p-schematic-diagram/
[bug #141]: https://ticket.coreboot.org/issues/141 [bug #141]: https://ticket.coreboot.org/issues/141

View File

@ -38,7 +38,7 @@ This information is valid for all supported models, except T430s, [T431s](t431s.
* ROM chip size should be set to 12MiB. * ROM chip size should be set to 12MiB.
```eval_rst ```eval_rst
Please also have a look at :doc:`../../flash_tutorial/index`. Please also have a look at :doc:`../../tutorial/flashing_firmware/index`.
``` ```
## Splitting the coreboot.rom ## Splitting the coreboot.rom
@ -90,4 +90,4 @@ Tests on Lenovo W530 showed no issues with a stripped and shrunken ME firmware.
[me_cleaner]: ../../northbridge/intel/sandybridge/me_cleaner.md [me_cleaner]: ../../northbridge/intel/sandybridge/me_cleaner.md
[external programmer]: ../../flash_tutorial/index.md [external programmer]: ../../tutorial/flashing_firmware/index.md

View File

@ -70,5 +70,5 @@ the remaining space for the `bios` partition.
[me_cleaner]: ../../northbridge/intel/sandybridge/me_cleaner.md [me_cleaner]: ../../northbridge/intel/sandybridge/me_cleaner.md
[external programmer]: ../../flash_tutorial/index.md [external programmer]: ../../tutorial/flashing_firmware/index.md
[flashing tutorial]: ../../flash_tutorial/index.md [flashing tutorial]: ../../tutorial/flashing_firmware/index.md

View File

@ -361,4 +361,4 @@ Note that you should have an external SPI programmer as a backup method.
It will help you recover if you flash non-working ROM by mistake. It will help you recover if you flash non-working ROM by mistake.
[flash internally]: ../../flash_tutorial/int_flashrom.md [flash internally]: ../../tutorial/flashing_firmware/int_flashrom.md

View File

@ -37,7 +37,7 @@ The chip will either be a Macronix MX25L6405D or a Winbond W25Q64CVSIG.
Do not rely on dots painted in the corner of the chip (such as the blue dot Do not rely on dots painted in the corner of the chip (such as the blue dot
pictured) to orient the pins! pictured) to orient the pins!
[Flashing tutorial](../../flash_tutorial/no_ext_power.md) [Flashing tutorial](../../tutorial/flashing_firmware/no_ext_power.md)
Steps to access the flash IC are described here [T4xx series]. Steps to access the flash IC are described here [T4xx series].

View File

@ -53,5 +53,5 @@ Steps to access the flash IC are described here [T4xx series].
* Suspend (Windows 10) * Suspend (Windows 10)
[T4xx series]: t4xx_series.md [T4xx series]: t4xx_series.md
[flashing tutorial]: ../../flash_tutorial/ext_power.md [flashing tutorial]: ../../tutorial/flashing_firmware/ext_power.md
[T420 / T520 / X220 / T420s / W520 common]: Sandy_Bridge_series.md [T420 / T520 / X220 / T420s / W520 common]: Sandy_Bridge_series.md

View File

@ -9,6 +9,6 @@ the general [flashing tutorial].
Steps to access the flash IC are described here [T4xx series]. Steps to access the flash IC are described here [T4xx series].
[flashing tutorial]: ../../flash_tutorial/ext_power.md [flashing tutorial]: ../../tutorial/flashing_firmware/ext_power.md
[T4xx series]: t4xx_series.md [T4xx series]: t4xx_series.md
[T430 / T530 / X230 / T430s / W530 common]: Ivy_Bridge_series.md [T430 / T530 / X230 / T430s / W530 common]: Ivy_Bridge_series.md

View File

@ -22,5 +22,5 @@ the general [flashing tutorial].
[w530-2]: w530-2.jpg [w530-2]: w530-2.jpg
[flashing tutorial]: ../../flash_tutorial/ext_power.md [flashing tutorial]: ../../tutorial/flashing_firmware/ext_power.md
[T430 / T530 / X230 / T430s / W530 common]: Ivy_Bridge_series.md [T430 / T530 / X230 / T430s / W530 common]: Ivy_Bridge_series.md

View File

@ -18,5 +18,5 @@ the general [flashing tutorial].
Steps to access the flash IC are described here [X2xx series]. Steps to access the flash IC are described here [X2xx series].
[X2xx series]: x2xx_series.md [X2xx series]: x2xx_series.md
[flashing tutorial]: ../../flash_tutorial/ext_power.md [flashing tutorial]: ../../tutorial/flashing_firmware/ext_power.md
[T420 / T520 / X220 / T420s / W520 common]: Sandy_Bridge_series.md [T420 / T520 / X220 / T420s / W520 common]: Sandy_Bridge_series.md

View File

@ -16,4 +16,4 @@ is located at the circled place.
Unlike [most Ivy Bridge ThinkPads](Ivy_Bridge_series.md), X230s has a single 16MiB SPI flash chip. Unlike [most Ivy Bridge ThinkPads](Ivy_Bridge_series.md), X230s has a single 16MiB SPI flash chip.
The general [flashing tutorial](../../flash_tutorial/index.md) has more details. The general [flashing tutorial](../../tutorial/flashing_firmware/index.md) has more details.

View File

@ -43,5 +43,5 @@ Tested:
Linux payload (Heads) and SeaBIOS. Linux payload (Heads) and SeaBIOS.
[flashing tutorial]: ../../flash_tutorial/ext_power.md [flashing tutorial]: ../../tutorial/flashing_firmware/ext_power.md

View File

@ -110,4 +110,4 @@ needed (internally re-routed already).
[Winbond 25Q32BV datasheet]: https://www.winbond.com/resource-files/w25q32bv_revi_100413_wo_automotive.pdf [Winbond 25Q32BV datasheet]: https://www.winbond.com/resource-files/w25q32bv_revi_100413_wo_automotive.pdf
[Fintek F71808A datasheet]: https://www.alldatasheet.com/datasheet-pdf/pdf/459069/FINTEK/F71808A.html [Fintek F71808A datasheet]: https://www.alldatasheet.com/datasheet-pdf/pdf/459069/FINTEK/F71808A.html
[flashlayout]: flashlayout.svg [flashlayout]: flashlayout.svg
[flashing methods]: ../../../flash_tutorial/index.md [flashing methods]: ../../../tutorial/flashing_firmware/index.md

View File

@ -49,6 +49,6 @@ The board features:
## Extra links ## Extra links
[flashrom]: https://flashrom.org/Flashrom [flashrom]: https://flashrom.org/Flashrom
[flashing tutorial]: ../../../../flash_tutorial/ext_power.md [flashing tutorial]: ../../../../tutorial/flashing_firmware/ext_power.md
[Intel FSP2.0]: ../../../../soc/intel/fsp/index.md [Intel FSP2.0]: ../../../../soc/intel/fsp/index.md
[AST2500]: https://www.aspeedtech.com/products.php?fPath=20&rId=440 [AST2500]: https://www.aspeedtech.com/products.php?fPath=20&rId=440

View File

@ -42,7 +42,7 @@ Now, run `make` to build the coreboot image.
```eval_rst ```eval_rst
In addition to the information here, please see the In addition to the information here, please see the
:doc:`../../flash_tutorial/index`. :doc:`../../tutorial/flashing_firmware/index`.
``` ```
### Internal programming ### Internal programming

View File

@ -56,6 +56,6 @@ These issues apply to all boards. Have a look at the board-specific issues, too.
[Supermicro X11 LGA1151 series]: https://www.supermicro.com/products/motherboard/Xeon3000/#1151 [Supermicro X11 LGA1151 series]: https://www.supermicro.com/products/motherboard/Xeon3000/#1151
[OpenBMC]: https://www.openbmc.org/ [OpenBMC]: https://www.openbmc.org/
[flashrom]: https://flashrom.org/Flashrom [flashrom]: https://flashrom.org/Flashrom
[flashing tutorial]: ../../../../flash_tutorial/ext_power.md [flashing tutorial]: ../../../../tutorial/flashing_firmware/ext_power.md
[Intel FSP2.0]: ../../../../soc/intel/fsp/index.md [Intel FSP2.0]: ../../../../soc/intel/fsp/index.md
[AST2400]: https://www.aspeedtech.com/products.php?fPath=20&rId=376 [AST2400]: https://www.aspeedtech.com/products.php?fPath=20&rId=376

View File

@ -105,4 +105,4 @@ seems that it shall not appear on X9SAE even if it is defined.
[X9SAE-V]: https://www.supermicro.com/products/motherboard/xeon/c216/x9sae-v.cfm [X9SAE-V]: https://www.supermicro.com/products/motherboard/xeon/c216/x9sae-v.cfm
[W25Q128FVSG]: https://static.chipdip.ru/lib/093/DOC001093213.pdf [W25Q128FVSG]: https://static.chipdip.ru/lib/093/DOC001093213.pdf
[flashrom]: https://flashrom.org/Flashrom [flashrom]: https://flashrom.org/Flashrom
[flash internally]: ../../flash_tutorial/int_flashrom.md [flash internally]: ../../tutorial/flashing_firmware/int_flashrom.md

View File

@ -81,4 +81,4 @@ Make sure to include all partitions into the ROM:
* ME * ME
* BIOS * BIOS
[external programmer]: ../../../flash_tutorial/index.md [external programmer]: ../../../tutorial/flashing_firmware/index.md

View File

Before

Width:  |  Height:  |  Size: 5.0 KiB

After

Width:  |  Height:  |  Size: 5.0 KiB

View File

Before

Width:  |  Height:  |  Size: 4.5 KiB

After

Width:  |  Height:  |  Size: 4.5 KiB

View File

@ -4,3 +4,4 @@
* [Part 2: Submitting a patch to coreboot.org](part2.md) * [Part 2: Submitting a patch to coreboot.org](part2.md)
* [Part 3: Writing unit tests](part3.md) * [Part 3: Writing unit tests](part3.md)
* [Managing local additions](managing_local_additions.md) * [Managing local additions](managing_local_additions.md)
* [Flashing firmware](flashing_firmware/index.md)