USBDEV DV Plan

Goals

  • DV
    • Verify all USBDEV 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.
      • Note that code and functional coverage goals are TBD due to pending evaluation of where / how to source a USB20 UVM VIP.
      • The decision is trending towards hooking up a cocotb (Python) based open source USB20 compliance test suite with this UVM environment.
  • FPV
    • Verify TileLink device protocol compliance with an SVA based testbench.

Current status

Design features

For detailed information on USBDEV design features, please see the USBDEV HWIP technical specification.

Testbench architecture

USBDEV testbench has been constructed based on the CIP testbench architecture.

Block diagram

Block diagram

Top level testbench

Top level testbench is located at hw/ip/usbdev/dv/tb/tb.sv. It instantiates the USBDEV DUT module hw/ip/usbdev/rtl/usbdev.sv. In addition, it instantiates the following interfaces, connects them to the DUT and sets their handle into uvm_config_db:

Common DV utility components

The following utilities provide generic helper tasks and functions to perform activities that are common across the project:

Compile-time configurations

None for now.

Global types & methods

All common types and methods defined at the package level can be found in usbdev_env_pkg. Some of them in use are:

[list a few parameters, types & methods; no need to mention all]

TL_agent

USBDEV testbench 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 USBDEV device.

USB20 Agent

The usb20_agent is currently a skeleton implementation. It does not offer any functionality yet.

UVM RAL Model

The USBDEV RAL model is created with the ralgen FuseSoC generator script automatically when the simulation is at the build stage.

It can be created manually (separately) by running make in the the hw/ area.

Reference models

There are no reference models in use currently.

Stimulus strategy

Test sequences

All test sequences reside in hw/ip/usbdev/dv/env/seq_lib. The usbdev_base_vseq virtual sequence is extended from cip_base_vseq and serves as a starting point. All test sequences are extended from usbdev_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:

  • usbdev_init(): Do basic USB device initialization.

Functional coverage

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:

  • TBD

Self-checking strategy

Scoreboard

The usbdev_scoreboard is primarily used for end to end checking. It creates the following analysis ports to retrieve the data monitored by corresponding interface agents:

  • TBD

Assertions

  • TLUL assertions: The tb/usbdev_bind.sv binds the tlul_assert assertions 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.
  • TBD

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 basic sanity test:

$ cd hw/ip/usbdev/dv
$ make TEST_NAME=usbdev_sanity

Testplan

Milestone Name Description Tests
V1 sanity <p><strong>Goal</strong>: Basic sanity test acessing a major datapath in USBDEV.</p> <p><strong>Stimulus</strong>: Describe the stimulus procedure.</p> <p><strong>Checks</strong>&quot;: Describe the self-check procedure.</p> <ul> <li>add bullets as needed</li> <li>second bullet<br> describe second bullet</li> </ul> <p>Start a new paragraph.</p> usbdev_sanity<br>
V1 csr_hw_reset <p>Verify the reset values as indicated in the RAL specification.</p> <ul> <li>Write all CSRs with a random value.</li> <li>Apply reset to the DUT as well as the RAL model.</li> <li>Read each CSR and compare it against the reset value. it is mandatory to replicate this test for each reset that affects all or a subset of the CSRs.</li> <li>It is mandatory to run this test for all available interfaces the CSRs are accessible from.</li> <li>Shuffle the list of CSRs first to remove the effect of ordering.</li> </ul> usbdev_csr_hw_reset<br>
V1 csr_rw <p>Verify accessibility of CSRs as indicated in the RAL specification.</p> <ul> <li>Loop through each CSR to write it with a random value.</li> <li>Read the CSR back and check for correctness while adhering to its access policies.</li> <li>It is mandatory to run this test for all available interfaces the CSRs are accessible from.</li> <li>Shuffle the list of CSRs first to remove the effect of ordering.</li> </ul> usbdev_csr_rw<br>
V1 csr_bit_bash <p>Verify no aliasing within individual bits of a CSR.</p> <ul> <li>Walk a 1 through each CSR by flipping 1 bit at a time.</li> <li>Read the CSR back and check for correctness while adhering to its access policies.</li> <li>This verify that writing a specific bit within the CSR did not affect any of the other bits.</li> <li>It is mandatory to run this test for all available interfaces the CSRs are accessible from.</li> <li>Shuffle the list of CSRs first to remove the effect of ordering.</li> </ul> usbdev_csr_bit_bash<br>
V1 csr_aliasing <p>Verify no aliasing within the CSR address space.</p> <ul> <li>Loop through each CSR to write it with a random value</li> <li>Shuffle and read ALL CSRs back.</li> <li>All CSRs except for the one that was written in this iteration should read back the previous value.</li> <li>The CSR that was written in this iteration is checked for correctness while adhering to its access policies.</li> <li>It is mandatory to run this test for all available interfaces the CSRs are accessible from.</li> <li>Shuffle the list of CSRs first to remove the effect of ordering.</li> </ul> usbdev_csr_aliasing<br>
V1 csr_mem_rw_with_rand_reset<p>Verify random reset during CSR/memory access.</p> <ul> <li>Run csr_rw sequence to randomly access CSRs</li> <li>If memory exists, run mem_partial_access in parallel with csr_rw</li> <li>Randomly issue reset and then use hw_reset sequence to check all CSRs are reset to default value</li> <li>It is mandatory to run this test for all available interfaces the CSRs are accessible from.</li> </ul> usbdev_csr_mem_rw_with_rand_reset<br>
V1 mem_walk <p>Verify accessibility of all memories in the design.</p> <ul> <li>Run the standard UVM mem walk sequence on all memories in the RAL model.</li> <li>It is mandatory to run this test from all available interfaces the memories are accessible from.</li> </ul> usbdev_mem_walk<br>
V1 mem_partial_access <p>Verify partial-accessibility of all memories in the design.</p> <ul> <li>Do partial reads and writes into the memories and verify the outcome for correctness.</li> <li>Also test outstanding access on memories</li> </ul> usbdev_mem_partial_access<br>
V2 intr_test <p>Verify common intr_test CSRs that allows SW to mock-inject interrupts.</p> <ul> <li>Enable a random set of interrupts by writing random value(s) to intr_enable CSR(s).</li> <li>Randomly &quot;turn on&quot; interrupts by writing random value(s) to intr_test CSR(s).</li> <li>Read all intr_state CSR(s) back to verify that it reflects the same value as what was written to the corresponding intr_test CSR.</li> <li>Check the cfg.intr_vif pins to verify that only the interrupts that were enabled and turned on are set.</li> <li>Clear a random set of interrupts by writing a randomly value to intr_state CSR(s).</li> <li>Repeat the above steps a bunch of times.</li> </ul> usbdev_intr_test<br>
V2 oob_addr_access <p>Access out of bounds address and verify correctness of response / behavior</p>usbdev_tl_errors<br>
V2 illegal_access <p>Drive unsupported requests via TL interface and verify correctness of response / behavior</p> usbdev_tl_errors<br>
V2 outstanding_access <p>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.</p> usbdev_csr_hw_reset<br> usbdev_csr_rw<br> usbdev_csr_aliasing<br> usbdev_same_csr_outstanding<br>
V2 partial_access <p>Do partial accesses.</p> usbdev_csr_hw_reset<br> usbdev_csr_rw<br> usbdev_csr_aliasing<br>