[manuf] ROM_EXT/Owner FW bootup verification without UART access in Earl Grey provisioning
Open
Nobody has claimed this yet.
Component:Software
Manufacturing
Type:Task
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
Description
Currently, we rely on UART logs (Starting ROM_EXT {major_ver}.{minor_ver}) to verify successful ROM_EXT boot. However, UART access is unavailable in the Earl Grey provisioning environment. To address this, we need to implement an alternative verification method using peripherals like GPIO pins to signal boot status.
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 the ROM_EXT/Owner FW boot sequence and the Earl Grey provisioning environment described in the issue. Compare the existing UART-based “Starting ROM_EXT {major_ver}.{minor_ver}” verification with the available GPIO or other peripheral signals. Done means provisioning can verify successful boot without UART access.
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
- 30/100