Rollback firmware flashing in case iinternal flash error (brick rollback in case bootblock region being WP)
@tlaurion is already working on this.
Since Nov 30, 2024.
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 6
Description
flasrom/flashprog could fail internal flashing.
A simple protection against this would be to
1- backup the current rom in memory
2- do whatever we currently do in flash.sh || flash backup rom in case of error
Be safer against possible user errors with chip specific SPI WP support landing iteratively under flashrom/flashprog and user interest into WP.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing flash.sh and the current flashrom/flashprog internal-flashing flow. Trace how errors are handled, especially when the bootblock region is write-protected. Done means the current ROM is backed up in memory and restored after an internal-flashing error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- embedded-iot, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100