- Verify all SPI Device IP features by running dynamic simulations with a SV/UVM based testbench
- Develop and run all tests based on the testplan below towards closing code and functional coverage on the IP and all of its sub-modules
- Verify TileLink device protocol compliance with an SVA based testbench
For detailed information on SPI Device design features, please see the SPI_device design specification.
SPI Device testbench has been constructed based on the CIP testbench architecture.
Top level testbench is located at
hw/ip/spi_device/dv/tb/tb.sv. It instantiates the SPI Device DUT module
In addition, it instantiates the following interfaces, connects them to the DUT and sets their handle into
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
spi_device_env_pkg. Some of them in use are:
parameter uint SRAM_OFFSET = 'h800;
parameter uint SRAM_SIZE = 2048;
SPI Device 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 SPI Device.
spi agent is used to drive and monitor SPI items. There are 2 spi_agents in the testbench to serve as a SPI host and a SPI device.
- The host agent is connected to the upstream port to drive stimulus for FW mode, TPM mode and flash mode.
- The device agent is connected to the passthrough port. When host sends a flash transaction with passthrough enabled, the device agent receives it and provides the return data when it’s a read command.
The SPI Device 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
All test sequences reside in
spi_device_base_vseq virtual sequence is extended from
cip_base_vseq and serves as a starting point.
All test sequences are extended from
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:
- spi_device_fw_init: Fully randomize SPI Device control following CSRs and configure TX/RX SRAM FIFO size for FW mode as following
- clock polarity/phase(CPOL, CPHA), bit direction(tx/rx_order), mode, fifo interrupt level(txlvl, rxlvl)
- TX/RX SRAM FIFO size: from 100 to 1900 and higher distribute for TX size / RX size = 1, 1/2 or 2/1
- spi_host_xfer_bytes: Send bytes of data to DUT (SPI Device) through spi_host_driver
- write_device_words_to_send: Write words of data to DUT CSR and update SRAM write pointer, which enables DUT to send data to SPI host.
- read_tx/rx_avail_bytes: Read CSRs to get how many bytes of available space/data in SRAM memory
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:
- common covergroup for interrupts
hw/dv/sv/cip_lib/cip_base_env_cov.sv: Cover interrupt value, interrupt enable, intr_test, interrupt pin
- Other spi_device covergroups are defined the
spi_device_env_covclass, which thoroughly covers all design features. Refer to the testplan covergroups sections for the detail descriptions.
spi_device_scoreboard is primarily used for end to end checking.
It creates the following analysis fifos to retrieve the data monitored by corresponding interface agents:
- tl_a_chan_fifo, tl_d_chan_fifo: These 2 fifos provide transaction items at the end of address channel and data channel respectively
- upstream_spi_host_fifo, upstream_spi_device_fifo: These 2 fifos provides TX/RX words of data from spi_monitor
- TLUL assertions: The
tlul_assertassertions to the IP to ensure TileLink interface protocol compliance.
- Unknown checks on DUT outputs: The RTL has assertions to ensure all outputs are initialized to known values after coming out of reset.
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/spi_device/dv/spi_device_sim_cfg.hjson -i spi_device_smoke