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

  • Your First Unit Test!

    See how easy it is to get started with SVUnit. Generate a unit test template, write unit tests and run them all in less than 20 minutes!

  • Unit Testing UVM Components

    The ability to test UVM components is a key feature of SVUnit. We’ll generate a UVM specific unit test template, add some TLM connectivity and write a unit test to verify a simple UVM model.

  • An Introduction to Unit Testing with SVUnit

    SVUnit is an open-source test framework for ASIC and FPGA developers writing Verilog/SystemVerilog code. SVUnit is the only SystemVerilog test framework suited for both design and verification engineers.

  • SVUnit Case Studies & Summary

    SVUnit is being used by design and verification engineers to improve bug rates and write high quality code. We’ll look at case studies that support the use of SVUnit and summarize the case for unit testing.

  • Verification with Multi-core Parallel Simulations: Have You Found Your Sweet Spot Yet?

    This poster paper illustrates design types and applications that are suitable and not suitable for multi-core simulations.

  • Verification with Multi-core Parallel Simulations: Have You Found Your Sweet Spot Yet?

    This paper is aimed at verification engineers looking to improve the productivity of their verification flow and to understand where multi-core simulations can provide maximum benefit. Successful multi-core parallel simulations depend on a variety of related design factors, which can be difficult to understand and sort out. With suitable design applications, it is possible to significantly save verification cycles.

  • Forbidden Sequence Property

    The Forbidden Sequence Property Pattern is used to specify portions of a design model’s verification execution that forbids a specified sequence of designated states or events.

  • Resource Sharing

    The Resource Sharing Pattern is used to share resources between objects without requiring detailed knowledge of the resource. Related resources share common access attributes thereby creating simple associations.

  • BFM Notification

    The BFM Notification Pattern is an Analysis Pattern to facilitate the design of transactors for dual domain partitioned testbenches that provide effective and efficient notifications of protocol transaction occurrences, and any other interesting protocol and design events and conditions, for testbench control and analysis.

  • Environment Layering

    The Environment Layering Pattern is used to provide consistent configuration and structure for vertical reuse of environments.

  • Component Configuration

    The Component Configuration Pattern is used to create a coherent configuration structure for the component hierarchy from top to bottom. It promotes self-containment and data-hiding techniques in the configuration and creation of component hierarchy.

  • Dual Domain Hierarchy Pattern

    The Dual Domain Hierarchy Pattern is an Environment Pattern to facilitate the design of testbenches that can be used for simulation as well as emulation, and across verification engines (or platforms) in general.

  • Technical Paper: Power Aware Verification in Mixed-Signal Simulation

  • Verification Patterns - Taking Reuse to the Next Level

    What is a pattern? In the process of designing something (e.g., a building, software program, or an airplane) the designer often makes numerous decisions about how to solve specific problems. If the designer can identify common factors contributing to the derived solution and abstracts the solution in such a way that it can be applied to other similar recurring problems, then the resulting generalized problem-solution pair is known as a pattern.

  • Precedence Chain Property

    The Precedence Chain Property Pattern is used to specify portions of a design model’s execution for relationships between chains (i.e., sequence of states or events1), where an occurrence of a cause chain must be have been preceded by an occurrence of an effect chain. We say that an occurrence of the effect chain is enabled by an occurrence of the cause chain.

  • Response Chain Property

    The Response Chain Property Pattern is used to specify portions of a design model’s execution for relationships between chains (i.e., sequence of states or events), where an occurrence of the cause chain must be followed by an occurrence of the effect chain.

  • Response Property

    The Response Property Pattern is used to specify portions of a design model’s execution for cause-effect relationships between a pair of states or events. An occurrence of the first, the cause, must be followed by an occurrence of the second, the effect . Also known as Follows and Leads -to.

  • Precedence Property

    The Precedence Property Pattern is used to specify portions of a design model’s execution for relationships between a pair of states or events,1 where the occurrence of the first is a necessary pre-condition for an occurrence of the second. We say that an occurrence of the second is enabled by an occurrence of the first.

  • Universality Property

    The Universality Property Pattern is used to specify portions of a design model’s verification execution that contains states or events that have a desired property. Also known as Henceforth   and   Always .

  • Bounded Existence Property

    The Bounded Existence Property Pattern is used to specify portions of a model’s verification execution that contains at most a specified number of instances of designated state transitions or events.

  • Existence Property

    The Existence Property Pattern is used to specify portions of a design model’s verification execution that contains an instance of a certain state or event1. Also known as Eventually or Future .

  • Absence Property

    The Absence Property Pattern is used to specify portions of a design model’s verification execution where a specific state or event1 should never occur. Also known Never .

  • Layering Sequence

    The layering sequence pattern is applicable to any situation where sequences are available that use one sequence_item but must transformed to another sequence_item to be executed on a target sequencer.

  • Utility

    Encapsulate small, useful functionality in a portable, easy-to-use object.

  • Façade

    A façade pattern provides a simple interface to a complex system, making it easier for the client or external world to use.