Each job needs less code in cva6.yml It also fixes an issue in CVV pipelines, where the CVA6 hash in the dashboard was not the one used in some jobs of the pipeline. |
||
---|---|---|
.github | ||
.gitlab-ci | ||
bin | ||
core-v-cores | ||
cv32e40p | ||
cv32e40s | ||
cv32e40x | ||
cva6 | ||
docs | ||
lib | ||
mk | ||
tools/vptool | ||
util | ||
vendor | ||
vendor_lib | ||
.gitignore | ||
.gitlab-ci.yml | ||
.metrics.json | ||
.readthedocs.yaml | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
GitCheats.md | ||
LICENSE.md | ||
MergeTest.md | ||
NEWS_ARCHIVE.md | ||
README.md |
core-v-verif
Functional verification project for the CORE-V family of RISC-V cores.
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.
For first time users of CORE-V-VERIF, the Quick Start Guide in the CORE-V-VERIF Verification Strategy is the best place to start.
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, cv32e40x, cv32e40s, cva6
Core-specific verification code.
docs
Sources for the Verification Strategy document, DV plans, coding style guidelines 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 and our SV/UVM coding style guidelines.
- 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.