Page Comparison

This page provides technical details about running the Architecture Compatible Test (ACT) suite to achieve the "RISC-V Compatible™" trademark and logo.  Completion of the test suite is is one step in the process of gaining permission to use the “RISC-V Compatible” Trademark. See the RISC-V Branding Guidelines & Materials webpage for more details and requirements on the other steps.

...

1. Read and understand the Architecture Test Policy.  This document defines the testing which is one of the requirements to use the RISC-V Compatible Trademark, including re-running the tests when the implementation is changed or the ACT test version changes.
2. Review the information in the Profiles summary spreadsheet and decide the base profile and any additional extensions for which the target device wishes to claim compatibility.
3. Build an ISA YAML files for the SAIL golden model and Device Under Test (DUT). The SAIL YAML file should reflect the extensions being targeted for Compatible branding (decided in Step #2), but the DUT YAML should reflect the devices true capabilities.
   Example YAML files are provide in the examples directory of the RISCV-CONFIG GitHub repo (named XXX_isa.yaml).  The YAML syntax for ISA files is documented in the "ISA YAML Spec" section of the RISCV-CONFIG documentation.
   
4. Build Platform YAML file to reflect the DUT.  This same file should be used for all runs of the ACT suite.
   Example YAML files are provide in the examples directory of the RISCV-CONFIG GitHub repo (named XXX_platform.yaml).  The YAML syntax for ISA files is documented in the "Platform YAML Spec" section of the RISCV-CONFIG documentation.
   
5. Install the RISCV-CONFIG tool and use it to configure validate the ISA and Platform YAML files for all extensions included in step #2built in Steps #3 and #4.  See the RISCV-CONFIG documentation for more details.
6. Install the RISCOF Framework, ACT test suite, and SAIL.  Detailed steps for this process can be found in the "Running RISCV-ARCH-TESTS "section of the RISCOF Documentation.
7. Configure RISCOF for a  Device Under Test (DUT) for the target core to be tested.
8. Run the tests using RISCOF against the SAIL golden model and the DUT.
9. Review the test results. to ensure that the DUT test results match the results of the SAIL golden model for all extensions in common.
10. When ready, submit the test results and supporting information per the directions in the “Where to Report Test Results” section of the Architecture Test Policy.
    

...

A RISC-V Technical Session titled "Using Template Repo  to setup/run RISC-V Arch Test Suite under RHEL/Ubuntu" was recorded in April 2023.  It provides information about a member-provided repo (link) that supplements setup of the ACT environment with some extra scripts and files.  Details, including the presentation and recording links are available here.

...