lowRISC / lowRISC/opentitan

[Verilator] Split top_*_verilator into testbench and chip-level module

Open
#6,103 9 comments 0 reactions 0 assignees View on GitHub
Component:RTL Earlgrey-PROD Candidate Priority:P2 TOP:earlgrey Type:Enhancement
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

Split out from https://github.com/lowRISC/opentitan/issues/5221.

- [x] Split the Verilator top into a Verilator chip-level module (with padring and etc.) and a separate Verilator testbench. (#7544)
- [x] Template the Verilator chip-level module
- [ ] Re-enable Verilator JTAG DPI

Contributor guide

Open the contributing guide

Research direction

Start by reading the parent issue #5221 and the completed split tracked in #7544 to understand the Verilator chip-level module and testbench boundaries. Then trace the remaining Verilator JTAG DPI path; done means JTAG DPI is re-enabled and the Verilator testbench and chip-level module still work together.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.