lowRISC / lowRISC/opentitan

[dv] Explore how reset handling can be improved

Open
#27,375 3 comments 0 reactions 6 assignees View on GitHub

@matutem is already working on this.

Since Jun 24, 2025.

Component:DV IP:all
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

Reset handling is in general very flaky in module level DV. `stress_test_all_with_reset` does some form of reset, but this needs to be more generic and dv_base_vseq.sv or cip_base_vseq.sv should actually support it.

Change in reset handling will have implications across the board for DV in OT and a migration plan for individual modules might be needed.

Experiments will be done on AC_RANGE_CHECK to prove some of the concepts

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.