Search Results

Filters
Reset All

Filters

Topic

Show More

Show Less

Content Type

Show More

Show Less

Audience

Tags

Show More

Show Less

1772 Results

  • Register Model Coverage

    Which covergroups get built within a register block object or a register object is determined by a local variable called m_has_cover.

  • The Sequence Library

    UVM provides a class for randomly creating and running sequences. This class is called uvm_sequence_library.

  • Stopping a Sequence

    Once started, sequences should not be stopped.

  • Virtual Sequences

    A virtual sequence is a sequence which controls stimulus generation using several sequencers.

  • Slave Sequences (Responders)

    A slave sequence is used with a driver that responds to events on an interface rather than initiating them. This type of functionality is usually referred to as a responder.

  • Wait for a Signal

    In the general case, synchronizing to hardware events is taken care of in UVM testbenches by drivers (proxy & BFM) and monitors (proxy & BFM).

  • Interrupt Sequences

    In hardware terms, an Interrupt is an event which triggers a new thread of processing.

  • Virtual Sequencers (Not Recommended)

    A virtual sequence is a sequence which controls a stimulus generation process using several sequencers.

  • Command Line Processor

    The UVM command line processor is used to interact with plusargs. Several plusargs are pre-defined and part of the UVM standard.

  • Transaction Methods

    When working with data object classes derived from uvm_objects, including ones derived from uvm_transactions, uvm_sequence_items and uvm_sequences, there are a number of methods which are defined for common operations on the data objects properties.

  • End of Test

    A UVM testbench, if is using the standard phasing, has a number of zero time phases to build and connect the testbench, then a number of time consuming phases, and finally a number of zero time cleanup phases.

  • UVM Driver

    The UVM driver is responsible for communicating at the transaction level with the sequence via TLM communication with the sequencer and converting between the sequence_item on the transaction side and pin-level activity in communicating with the DUT via a virtual interface.

  • UVM Monitor

    The first task of the analysis portion of the testbench is to monitor activity on the DUT. A Monitor, like a Driver, is a constituent of an agent.

  • UVM Factory

    The purpose of the UVM factory is to enable an object of one type to be substituted with an object of a derived type without changing the testbench structure or even the testbench code.

  • Post-Run Phases

    Many analysis components perform their analysis on an ongoing basis during the simulation run.

  • Backdoor Accesses

    The UVM register model facilitates access to hardware registers in the DUT either through front door accesses or back door accesses.

  • Package Organization

    UVM organizes all of its base classes into a SystemVerilog Package.

  • UVM Verification Component

    A UVC ( U VM V erification C omponent) is a Verification Component designed for use in UVM. It is a multi-faceted definition and has different layers of meaning in different contexts.

  • UVM Connect

    Learn about how to use UVM Connect to link UVM and SystemC using TLM.

  • UVMC Connections

    To communicate, verification components must agree on the data they are exchanging and the interface used to exchange that data.

  • UVMC Conversion

    Object transfer requires converters to translate between the two types when crossing the SC-SV language boundary.

  • UVMC Command API

    The UVM Connect Command API gives SystemC users access to key UVM features in SystemVerilog.

  • Questa Verification IP, More than just a BFM

    Today’s advanced UVM environments require more than a standard BFM to support environment reuse, randomized stimulus, generation of traffic scenarios, coverage collection, etc.

  • UART Example (.tgz)

    Most of the functional coverage can be derived from content of the registers which are used to control and monitor the behavior of the device. The register interface may also serve the data path. There may be scope for using assertions on signal interfaces.

  • Specification to Test Plan

    The goal in creating a coverage model spreadsheet or testplan is to capture a subset of the design intent and behavior that is targeted for functional coverage.