core-v-verif

Functional verification project for the CORE-V family of RISC-V cores.

NEWS UPDATES:

2021-03-23: The verificaton environment for the cv32e40x is up and running.
2020-12-16: The cv32e40p_v1.0.0 of core-v-verif is released. This tag clones the v1.0.0 release of the CV32E40P CORE-V core and will allow you to reproduce the verification environment as it existed at RTL Freeze.
More news is available in the archive.

Getting Started

First, have a look at the OpenHW Group's website to learn a bit more about who we are and what we are doing.
Reading the CORE-V-VERIF Verification Strategy is strongly recommended.

Getting started with CV32E40P

If you want to run a simulation there are two options:

1. To run the CORE testbench, go to cv32e40p/sim/core and read the README.
2. To run the CV32E40P UVM environment, go to cv32e40p/sim/uvmt and read the README.

Getting started with CVA6

To run CVA6 testbench, go to cva6 directory and read the README.

Directory Structure of this Repo

bin

Various utilities for running tests and performing various verification-related activities in the core-v-verif repository.

core-v-cores

Empty sub-directory into which the RTL from one or more of the CORE-V-CORES repositories is cloned.

cv32e40p

Verification Environments, testbenches, testcases and simulation Makefiles for the CV32E40P core.

cva6

Verification Environments, testbenches, testcases and simulation Makefiles for the CVA6 cores.

docs

Source for GitHub Pages. Contains a pointers to the Verification Strategy document, the CORE-V-DOCS repository, and available coverage reports.

mk

Common simulation Makefiles that support testbenches for all CORE-V cores.

lib

Common components for the all CORE-V verification environments.

vendor_lib

Verification components supported by third-parties.

Contributing

We highly appreciate community contributions. You can get a sense of our current needs by reviewing the GitHub projects associated with this repository. Individual work-items within a project are defined as issues with a task label.

To ease our work of reviewing your contributions, please:

• Review CONTRIBUTING.
• Split large contributions into smaller commits addressing individual changes or bug fixes. Do not mix unrelated changes into the same commit!
• Write meaningful commit messages.
• If asked to modify your changes, do fixup your commits and rebase your branch to maintain a clean history.