Verify that ROM_EXT can unlock and transfer ownership to a new owner.
Open
Nobody has claimed this yet.
Component:RomExt/E2e/Test
Priority:P1
Type:Task
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
- Start in an locked & owned state with the `fake` owner as owner.
- Unlock the chip into the UnlockedAny state using the `fake` owner unlock key.
- Upload an owner block for the `dummy` owner.
- Activate ownership with the `dummy` activate key.
- Confirm code execution with the `dummy` owner application key.
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 ownership, unlock, activation, and code-execution verification flow and its existing tests. Run the relevant verification entry point with the fake owner, then confirm the sequence reaches UnlockedAny, uploads the dummy owner block, activates with the dummy key, and executes code with the dummy application key.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100