Introduction to RISC-V Processor Verification
summary
Processor verification is roughly five times harder than SoC work, so projects use a mix of post‑simulation trace compare and asynchronous continuous compare with an ISS reference model (Imperas/OVPsim Plus), verification IP that formats RTL traces into the model, SystemVerilog functional coverage, and integration with Synopsys VCS/Verdi and Cadence waveforms for code debug. A predictive engine handles interrupts and debug, CV32E40P has taped out using this flow, more than 100 organizations use OVPsim Plus, and four additional cores are in flight.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:40RISCV disconnect
- 1:40Agenda
- 1:58Verification Plan
- 2:51Hello World
- 4:04Instruction Set Simulator
- 5:01Asynchronous Continuous Compare
- 6:12Block Diagram
- 7:09Reference Model
- 9:19Verification IP
- 10:18VBI
- 10:37Functional Coverage
- 11:30Directed Tests
- 12:23Debug
- 13:00Open Hardware
- 14:02Customers and Partners
- 14:48Conclusion
related talks
13mIntroduction to RISC-V Processor Verification
17mDemo: RISC-V Models for Verification, Software Development and Architectural Explor...
21mThe New Verification Ecosystem that Supports RISC-V Verification fo...
21mA Comparative Analysis of RISC-V Architecture Based on the RISC-V SoC DV Experience
09mDemo: Imperas/OVP RISC-V Models: Not Your Grandparents’ ISS
09mExploring RISC-V architectures with VPSim, a virtual prototyping environment
11mDriving SoC Innovation with Synopsys RISC-V Solutions
16mEfficient debug and trace of RISC-V systems: a hardware/software co-design approach
