Skip to content

Lampro-Mellon/LEC-RTL

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 

Repository files navigation

Logical Equivalence Check of Quasar RISC-V Core 2.0 from Lampro Mellon

This repository contains the EL2 SweRV Core, Quasar Core design in RTL, and the setup files. To run logical equivalency check (LEC) using Synopsys Formality on the two designs follow these instructions.

Directory Structure

├── verif
    ├── LEC
    │    ├── LEC_RTL
    │       ├── Imp_BB_RTL                   # Quasar wrapper Black Boxes
    │       ├── Golden_RTL
    │           ├── configs
    │           ├── design
    │               ├── dbg                  # Debugger
    │               ├── dec                  # Decode, Registers and Exceptions 
    │               ├── dmi                  # DMI block
    │               ├── exu                  # EXU (ALU/MUL/DIV)
    │               ├── ifu                  # Fetch & Branch Prediction
    │               ├── include                
    │               ├── lib                  # Bridges and Library
    │               └── lsu                  # Load/Store
    │       ├── docs
    │       └── tools
    │          ├── snapshots
    │             └── defaults
    │    └── formality_work
    │       └── formality_log               # formality log/dump files
    └── sim                                 # Simulation log/dump files

Dependencies

  • Synopsys Formality tool must be installed on the system to run logical equivalence check.

Quickstart guide

  1. Clone the repository
  2. Setup RV_ROOT to point to the path in your local filesystem
  3. Determine your configuration {optional}
  4. Run "make -f $RV_ROOT/tools/Makefile lec"

Getting design files ready for the tool

Following changes have been made in the design files to get them ready for LEC using Formality, if you want to clone the golden design from chipsalliance repository do following changes in the golden design. The directory $RV_ROOT/verif/LEC/LEC_RTL is not available initially when the Quasar RISC-V core is cloned from it's repository. It will be generated when the "make -f $RV_ROOT/tools/Makefile lec" is executed. Once this command is executed, it will generate the RTL for Quasar RISC-V core and place it in the $RV_ROOT/generated_rtl.

Golden Design

Including el2_param.vh in the Golden design (El2 SweRV core) yields syntax error as formality tool does not accept parameter in this format, for further detail please refer to FMR_VLOG-481 formality error message. To fix this issue follow these steps

  1. Remove all pt. from design files
  2. Remove #(.pt(pt)) in module instantiation from design files
  3. Comment out localparam DCCM_WIDTH_BITS in $RV_ROOT/verif/LEC/LEC_RTL/Golden_RTL/design/lsu/el2_lsu_dccm_ctl.sv
  4. Put all paramters from el2_param.vh file to new *.sv file, parameter should be in $RV_ROOT/verif/LEC/LEC_RTL/Golden_RTL/parameter.sv format
  5. Replace el2_param.vh with the parameter.sv file.

Importing el2_pkg in design files yields FMR_VLOG-224 formality error message which states that a reference to the given package should be analyzed before its declaration. In order to resolve this, the packet file which has all the packets should be included in the Quasar top or in the file list.

Implementation design

The Quasar RISC-V core is all set to be checked and loaded directly into Formality without any changes.

Synopsys Formality Constraints/Setup

Constraints

There are some registers which may be potentially constant, when a test pattern is applied to these signals by the tool, it causes design failures. To solve this problem the potionally constant registers were identified, and a constant value is applied to these registers in setup mode. The constant setup file is present in $RV_ROOT/verif/LEC/setup_files/constant_2.0.fms

User Matched Points

The tool matches the compare points on either name based or by signal analysis, but in some cases the tool fails to identify the equivalent points. All these unmatched points are matched manually through "set_user_match" command for default configuration. The unmatched points can be flops, ports, latches or black-box pins, their details are present in the following directory respectively.

  1. $RV_ROOT/verif/LEC/setup_files/DFF_2.0.fms
  2. $RV_ROOT/verif/LEC/setup_files/Functional_match_2.0.fms
  3. $RV_ROOT/verif/LEC/setup_files/Input_ports_2.0.fms
  4. $RV_ROOT/verif/LEC/setup_files/Output_ports_2.0.fms
  5. $RV_ROOT/verif/LEC/setup_files/BB_input_pins_2.0.fms
  6. $RV_ROOT/verif/LEC/setup_files/BB_output_pins_2.0.fms

Note: Quasar Core has been verified on default configuration.