[rom_ext] Enter rescue mode when there is no valid owner firmware
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Description
If the ROM_EXT cannot find a valid owner firmware target to boot, then it is nice to have ROM_EXT enter rescue mode and expecting an owner firmware image over the main UART pins. There is nothing better for ROM_EXT to do at that moment, and pre-entering rescue mode can help in the scenarios where the host uart and OT uart have trouble with initial synchronization (this has happened to us in the past).
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 locating the ROM_EXT path that validates and selects an owner firmware target, then review the existing rescue-mode entry and main UART handling. Done means ROM_EXT enters rescue mode and expects an owner firmware image over the main UART when no valid owner firmware target can be booted.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100