lowRISC / lowRISC/opentitan

[racl_ctrl/dv] DV Bring-Up, Smoke Test, V1 Sign-Off

Open
#26,156 2 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

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

Description

racl_ctrl is a recently created HW IP block that is currently only instantiated in Darjeeling. To establish a basic level of confidence in the correctness of the implementation, block-level DV needs to be brought up, a smoke test exercising and checking essential functionality needs to pass, and eventually the block needs to be signed off at V1.

We want to get this done in three phases:

  1. Bring up DV, so that multiple contributors can afterwards work in parallel on tests (or parts thereof) and checks.
  2. Write smoke test and add basic checks to scoreboard; get it to pass with the default seed.
  3. V1 sign off.

Tasks

DV Bring-Up

  • #26157
  • Turn RFC into in-tree specification and documentation (potentially less urgent because the RFC is specific to this module, so it can be used as ground truth for verification checks).
  • DUT instantiated with major interfaces connected
  • All available interface assertion monitors connected
  • X / unknown checks on DUT outputs added
  • Skeleton DV environment created with UVCs
  • TLM connections made from interface monitors to the scoreboard

Smoke Test

  • Smoke test (accessing basic functionality) written and manually checked for correctness
  • Basic checks added to scoreboard
  • CSR / mem test suite activated and passing
  • Smoke test passing basic checks in scoreboard at least for the default seed
  • Smoke test (default seed) enabled in CI

V1 Sign-Off

  • DV document drafted and reviewed
  • Testplan complete and reviewed
  • Smoke test passes for most of the seeds
  • Smoke test passes also in alternative simulator
  • Nightly regression set up
  • DV lint set up and passing
  • Coverage collection set up (doesn't have to be complete yet)

References / Details

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.