[otbn,dv] Complete coverage and tests for the various checks that use pre-decode
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
OTBN checks various aspects of decode results against the pre-decode results.
Many of these are tested (by injecting faults) in the `otbn_ctrl_redun` test, but not all (in particular the control flow related signals introduced in https://github.com/lowRISC/opentitan/pull/13092 and https://github.com/lowRISC/opentitan/pull/13069), there also isn't specific coverage for the various checks.
This should be added for V3.
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 with the otbn_ctrl_redun test and the pre-decode checks it exercises, then review the control-flow signals introduced by pull requests 13092 and 13069. Done means the remaining checks, especially those control-flow checks, have fault-injection tests and specific coverage for the V3 work.
Written by the indexing model from the issue text.
Assessment
- Domain
- security, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100