Design Verification Setup in matcha

Revision 1.1

DV Methodology

Design Verification Methodology in Opentitan has been followed in matcha.

Currently, VCS is used as the major simulator for running DV tests in matcha.

DV Settings

At the root of shodan repo:

export ROOTDIR=`pwd`
export titan_root=$ROOTDIR/hw/opentitan-upstream
export PYTHONPATH=$ROOTDIR/hw/matcha/util:$titan_root/util:$titan_root/util/dvsim:$PYTHONPATH

Run DV tests

cd $ROOTDIR/hw/matcha
util/dvsim_match/ \
    hw/top_matcha/dv/chip_sim_cfg.hjson \
    -i <test_name>

Generate Waveform

To dump waveforms from the simulation, use the -w or --waves option to pass the argument to For example:

util/dvsim_match/ \
    hw/top_matcha/dv/chip_sim_cfg.hjson \
    -i <test_name> \
    -w fsdb

Debug with Verdi

To debug with Verdi:

  1. Generate kdb of the current design with -kdb[=only] option in VCS runs
  2. Invoke Verdi with the following command:
	verdi -dbdir <path to simv.daidir>
  1. Load the waveform (fsdb, vcd, etc)
  2. Trace the signals with Verdi

Run DV tests with bazel in air-gapped environment

Sparrow HW DV Notes describes how to set up the bazel runs on EDACloud.

In an air-gapped environment like EDACloud, DV tests can be invoked from hw/matcha with bazel. Here is the sample bazel command:

bazel run //util/ \
          --distdir=`pwd` \
          -- hw/top_matcha/dv/chip_sim_cfg.hjson \
          -i chip_sw_uart_tx_rx


Known issues

  1. To turn off all the assertions in simulation, add the following lines in
  $assertoff(0, tb.dut);
  1. Comment out lines 204-207 in

to avoid the unnecessary error messages