Open
Conversation
filipleple
commented
Feb 6, 2026
| ### Further reading | ||
|
|
||
| For a more detailed documentation of the implementation, please read the | ||
| [upstream coreboot documentation](WIP.com) |
Signed-off-by: Filip Lewiński <filip.lewinski@3mdeb.com>
filipleple
force-pushed
the
redundancy
branch
from
1ffa469 to
95e7d2e
Compare
SergiiDmytruk
requested changes
Feb 7, 2026
Member
There was a problem hiding this comment.
You forgot to add this file to mkdocs.yml.
|
|
||
| The problem addressed by this functionality is that when a platform's firmware | ||
| crashes during the boot process, the only mode of recovery is usually taking | ||
| apart the platform, attaching a SPI clip and flashing recovery firmware as per |
Member
There was a problem hiding this comment.
Suggested change
| apart the platform, attaching a SPI clip and flashing recovery firmware as per | |
| apart the platform, attaching an SPI clip and flashing recovery firmware as per |
Since letters are pronounced separately and the first one starts with a vowel sound.
Comment on lines
+8
to
+13
| With the Top Swap A/B redundancy, there are two firmware slots - A and B, | ||
| of which A is a read-only golden copy, and B is the update partition. A | ||
| firmware update is going to target the B slot, and boot from it. Should the new | ||
| firmware fail, the platform can be brought back to life by performing a | ||
| **CMOS reset**, which will cause the platform to boot from the safe slot A | ||
| again. |
Member
There was a problem hiding this comment.
Suggested change
| With the Top Swap A/B redundancy, there are two firmware slots - A and B, | |
| of which A is a read-only golden copy, and B is the update partition. A | |
| firmware update is going to target the B slot, and boot from it. Should the new | |
| firmware fail, the platform can be brought back to life by performing a | |
| **CMOS reset**, which will cause the platform to boot from the safe slot A | |
| again. | |
| With the Top Swap A/B redundancy, there are two firmware slots - **A** and **B**, | |
| of which **A** is a read-only golden copy, and **B** is the update partition. A | |
| firmware update is going to target the **B** slot, and boot from it. Should the new | |
| firmware fail, the platform can be brought back to life by performing a | |
| **CMOS reset**, which will cause the platform to boot from the safe slot **A** | |
| again. |
Otherwise "A" as a slot conflicts with "A" as an article.
| physically topmost chunks of the BIOS flash chip, and decide in which order | ||
| to map them - effectively allowing to swap the two chunks. | ||
|
|
||
| * **A/B Slot Setup**: The firmware is divided into two slots: `BOOTBLOCK` and |
Member
There was a problem hiding this comment.
Suggested change
| * **A/B Slot Setup**: The firmware is divided into two slots: `BOOTBLOCK` and | |
| * **A/B Slot Setup**: The top of the firmware is divided into two slots: `BOOTBLOCK` and |
To be more accurate.
| these additional steps: | ||
|
|
||
| ```bash | ||
| sudo flashrom -w coreboot.rom --fmap -i TOPSWAP -i COREBOOT_TS |
Member
There was a problem hiding this comment.
Need -p internal? Don't remember it becoming optional.
Worth adding --noverify-all (-N) option? Otherwise active ME can cause verification failure.
| ## Further reading | ||
|
|
||
| For a more detailed documentation of the implementation, please read the | ||
| [upstream coreboot documentation](WIP.com) |
Member
There was a problem hiding this comment.
nit:
Suggested change
| [upstream coreboot documentation](WIP.com) | |
| [upstream coreboot documentation](WIP.com). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
issue: Dasharo/dasharo-issues#1487
ref: prot-1815