Verify that ROM_EXT can boot an owner stage test program in various locations.
Open
Nobody has claimed this yet.
Component:RomExt/E2e/Test
Type:Task
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
- The test program should be launched via the OTTF.
- The test program should print out the `boot_log` data.
- The test program should be tested in the A slot, the B slot and the virtual slot.
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
Locate the existing ROM_EXT and OTTF boot-test entry points, then trace how owner-stage test programs expose boot_log data. Exercise the program from the A slot, B slot, and virtual slot; done means each location launches through OTTF and prints the boot_log data.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100