PATTGEN testbench has been constructed based on the CIP testbench architecture.
Top level testbench is located at hw/ip/pattgen/dv/tb/tb.sv
. It instantiates the PATTGEN DUT module hw/ip/pattgen/rtl/pattgen.sv
. In addition, it instantiates the following interfaces, connects them to the DUT and sets their handle into uvm_config_db
:
pins_if
)The following utilities provide generic helper tasks and functions to perform activities that are common across the project:
All common types and methods defined at the package level can be found in pattgen_env_pkg
. Some of them in use are:
parameter uint NUM_PATTGEN_CHANNELS = 2;
PATTGEN instantiates (already handled in CIP base env) tl_agent which provides the ability to drive and independently monitor random traffic via TL host interface into PATTGEN device.
PATTGEN agent is configured to work device mode. The agent monitor captures patterns generated in channels then sends to the scoreboard for verification Since the DUT does not require any response thus agent driver is fairly simple.
The PATTGEN RAL model is created with the ralgen
FuseSoC generator script automatically when the simulation is at the build stage. It can be created manually by invoking regtool
:
All test sequences reside in hw/ip/pattgen/dv/env/seq_lib
. The pattgen_base_vseq
virtual sequence is extended from cip_base_vseq
and serves as a starting point. All test sequences are extended from pattgen_base_vseq
. It provides commonly used handles, variables, functions and tasks that the test sequences can simple use / call. Some of the most commonly used tasks / functions are as follows:
The pattgen_scoreboard
is primarily used for end to end checking.
sva/pattgen_bind.sv
binds the tlul_assert
assertions to the IP to ensure TileLink interface protocol compliance.We are using our in-house developed regression tool for building and running our tests and regressions. Please take a look at the link for detailed information on the usage, capabilities, features and known issues. Here's how to run a smoke test:
$ $REPO_TOP/util/dvsim/dvsim.py $REPO_TOP/hw/ip/pattgen/dv/pattgen_sim_cfg.hjson -i pattgen_smoke
{{< incGenFromIpDesc “../../data/pattgen_testplan.hjson” “testplan” >}}