Skip to content

Latest commit

 

History

History
122 lines (98 loc) · 5.13 KB

dv_doc_template.md

File metadata and controls

122 lines (98 loc) · 5.13 KB
Raw

FOO DV document

Goals

  • DV
    • Verify all FOO 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
  • FPV
    • Verify TileLink device protocol compliance with an SVA based testbench

Current status

Design features

For detailed information on FOO design features, please see the [FOO HWIP technical specification]({{</* relref "hw/ip/foo/doc" */>}}).

Testbench architecture

FOO 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/foo/dv/tb/tb.sv. It instantiates the FOO DUT module hw/ip/foo/rtl/foo.sv. In addition, it instantiates the following interfaces 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

[list compile time configurations, if any and what are they used for]

Global types & methods

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

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

TL_agent

FOO 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 FOO device.

UVC/agent 1

[Describe here or add link to its README]

UVC/agent 2

[Describe here or add link to its README]

UVM RAL Model

The FOO 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 hw/ area.

Reference models

[Describe reference models in use if applicable, example: SHA256/HMAC]

Stimulus strategy

Test sequences

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

  • task 1:
  • task 2:

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:

  • cg1:
  • cg2:

Self-checking strategy

Scoreboard

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

  • analysis port1:
  • analysis port2:

Assertions

  • TLUL assertions: The tb/foo_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.
  • assert prop 1:
  • assert prop 2:

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:

$ cd hw/ip/foo/dv
$ make TEST_NAME=foo_smoke

Testplan

{{</* incGenFromIpDesc "../../data/foo_testplan.hjson" "testplan" */>}}