[CHERIoT] Verify lockstep behavior for Ibex correctly identifies any faults injected into the new CHERIoT state or revoker
Open
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
This issue has no description.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the Ibex lockstep verification and CHERIoT fault-injection tests, then clarify which faults in the new CHERIoT state or revoker must be detected. Done means the verification correctly identifies the specified injected faults.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100