SPI Device DV Plan
- 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
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
Common DV utility components
The following utilities provide generic helper tasks and functions to perform activities that are common across the project:
Global types & methods
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 Device agent
spi agent is used to drive and monitor SPI items. Following special behavior is supported in spi_host_driver
- Toggle clock when SPI is in idle state (csb=1)
- During data transfer, there may be very long delay between each bit or byte of data
UVM RAL Model
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_init: Fully randomize SPI Device control following CSRs and configure TX/RX SRAM FIFO size 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
- TODO, add more
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
- host_spi_data_fifo, device_spi_data_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.
Building and running tests
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
Use default SRAM fifo setting. Seq:
Verify the reset values as indicated in the RAL specification.
Verify accessibility of CSRs as indicated in the RAL specification.
Verify no aliasing within individual bits of a CSR.
Verify no aliasing within the CSR address space.
Verify random reset during CSR/memory access.
Verify accessibility of all memories in the design.
Verify partial-accessibility of all memories in the design.
Create 3 parallel threads
Increase the chance to have fifo full by following
Override spi_device_txrx_vseq to send SPI transfer without checking TX/RX fifo, note:
Drive dummy sck without csb or drive dummy csb without sck, and test no impact on the design
Add extra delay between spi clock edge or extra delay between 2 words data This is to test host pause transfer for a while without turning off csb and then stream in data again
Reset async fifo when SPI interface is idle TODO: fifo may be fetching data from SRAM? What is the actual usage?
Test all supported interrupts:
TODO: Need to clarify the behavior in spec
send spi transfer on byte granularity, and make sure the timer never expires
Send spi transfer on bit granularity
Set fifo size to 4 bytes(minimum), 2k-4bytes(maximum) and others
TODO :only support fw mode now
Backdoor hack memory data to test basic memory ECC behavior limitation:
Run spi_device_fifi_full_vseq with very small delays
Verify common intr_test CSRs that allows SW to mock-inject interrupts.
Access out of bounds address and verify correctness of response / behavior
Drive unsupported requests via TL interface and verify correctness of response / behavior. Below error cases are tested
Drive back-to-back requests without waiting for response to ensure there is one transaction outstanding within the TL device. Also, verify one outstanding when back- to-back accesses are made to the same address.
Access CSR with one or more bytes of data For read, expect to return all word value of the CSR For write, enabling bytes should cover all CSR valid fields