For detailed information on I2C design features, please see the I2C design specification.
I2C testbench has been constructed based on the CIP testbench architecture.
Top level testbench is located at hw/ip/i2c/dv/tb/tb.sv
. It instantiates the I2C DUT module hw/ip/i2c/rtl/i2c.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 i2c_env_pkg
. Some of them in use are:
parameter uint I2C_FMT_FIFO_DEPTH = 32; parameter uint I2C_RX_FIFO_DEPTH = 32;
I2C 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 I2C device.
I2C agent is configured to work device mode and implemented as reactive agent
The I2C 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/i2c/dv/env/seq_lib
. The i2c_base_vseq
virtual sequence is extended from cip_base_vseq
and serves as a starting point. All test sequences are extended from i2c_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:
To ensure high quality constrained random stimulus, it is necessary to develop a functional coverage model. The following covergroups have been developed to prove that the test intent has been adequately met:
The i2c_scoreboard
is primarily used for end to end checking. It creates the following analysis ports to retrieve the data monitored by corresponding interface agents:
tb/i2c_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/i2c/dv/i2c_sim_cfg.hjson -i i2c_host_smoke
{{< incGenFromIpDesc “../../data/i2c_testplan.hjson” “testplan” >}}