Mike Thompson

Debug Specification for CVA6

1

According to their respective User Manuals, both the CV32E40X and CV32E40S have adopted Version1.0.0-STABLE of the RISC-V Debug Support specification. As this has not yet been ratified by RISC-V International,...

Describe CVA6 for write-through and write-back cache versions

1

In #602, there was a conversation like this: > Is the list of files in the manifest complete? >> Looks okay for the write-through cache version. Of course, the write-back...

This issue is related to #743 and #744, and exists to ensure that the golden configurations and their associated parameters in [ariane_cfg_t](https://github.com/openhwgroup/cva6/blob/master/core/include/ariane_pkg.sv#L36) are described in the CVA6 User Manual. A...

This issue is related to #743. The [ariane_cfg_t](https://github.com/openhwgroup/cva6/blob/master/core/include/ariane_pkg.sv#L36) struct does not "contain" all the parameters needed to fully define all CVA6 configurations. (There is even a [TODO](https://github.com/openhwgroup/cva6/blob/master/core/include/ariane_pkg.sv#L130) comment in the...

The [CVA6 Specification](https://docs.google.com/document/d/11rsoO5WKraMCraSpnsVqmt4hJaCcDG0zq7LTWdXVkf0/edit#heading=h.3qxt8brmoedo) identifies four "golden configurations": 1. cv32a6_imacf_sv32_fpga 2. cv32a6_imac_sv32_fpga 3. cv64a6_imacfd_sv39 4. cv32a6_imac_sv0 Each of these configurations should be easily implemented via a single parameter structure passed to...

Current, `mvendorid` reads as 0x0. I believe it should read as 0x0602 to match the vendor id of all other [CORE-V cores](https://cv32e40p.readthedocs.io/en/latest/control_status_registers/#machine-vendor-id-mvendorid).

(partially) fix RVFI integration issues

3

This PR resolves SV compile errors and warnings flagged by `dsim`: * **bhv/cv32e40p_rvfi.sv**: nonblocking assignments to automatic variables are not allowed (object variables are automatic by default). Dsim won't compile...

Add FPU integration information to the User Manual

3

The [Floating Point Unit chapter of the User Manual](https://github.com/openhwgroup/cv32e40p/blob/master/docs/source/fpu.rst) contains very little information about how the CV32E40P and FPU should be configured to ensure proper operation. There are parameters in...

Testbench Makefiles should use the common manifest (cv32e40p_manifest.flist)

6

This issue is related to the discussion for PR #266. It would good to update the Makefiles below the `tb` directory to use the `cv32e40p_manifest.flist` manifest. That will ensure Designers...

Create a single manifest file for synthesis and simulation

10

Currently, a YAML file and scriptware is used to generate synthesis scripts for CV32E40P. As far as I am aware, the scripts that process the YAML are not documented, and...