[sysrst_ctrl,sival] Auto-block functionality is not tested in SiVal
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Description
The [auto_block_key_outputs](https://github.com/lowRISC/opentitan/blob/dc22677a68b3f685bad0c2d225b4cf417b8f89c5/hw/ip/sysrst_ctrl/data/sysrst_ctrl_testplan.hjson#L110) testpoint exists in DV but in sival. Currently, the auto-block functionality is not tested in sival at all. Is that an oversight or is that feature just very low priority?
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 hw/ip/sysrst_ctrl/data/sysrst_ctrl_testplan.hjson at the auto_block_key_outputs testpoint, then inspect the existing SiVal tests for sysrst_ctrl. Determine how the auto-block functionality is represented in SiVal and add coverage so the testpoint is exercised there; done means the SiVal results demonstrate that auto-block is tested.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100