Search Results

Filters
Reset All

Filters

Topic

Show More

Show Less

Content Type

Show More

Show Less

Audience

Resource Type

Show More

Show Less

Tags

Show More

Show Less

2097 Results

  • Creating Tests the PSS Way in SystemVerilog

    Portable Stimulus is one of the latest hot topics in the verification space. Siemens EDA, and other vendors, have had tools in this space for some time, and Accellera just recently released the Portable Test and Stimulus Standard, a standard language that can be used to capture Portable Stimulus semantics.

  • Formal Bug Hunting with “River Fishing” Techniques

    Formal verification has been used successfully to verify today’s SoC designs. Traditional formal verification, which starts from time 0, is good for early design verification, but it is inefficient for hunting complex functional bugs. Based on our experience, complex bugs happen when there are multiple interactions of events happening under uncommon scenarios.

  • Auto-Generating Implementation-Level Sequences for PSS

    The Portable Test and Stimulus Standard (PSS) v1.0a aims to help the user describe the high-level test intent and create code for any downstream verification platform.

  • UVMF, Beyond the ALU Generator Tutorial Extending Actual Test Control of the DUT Inputs

    The basis of this article was derived from practical experience. The scenario was this: “Here is a DUT specification, we have no UVM environment for you to start with as a template, so go and find out how to generate one with Siem ens EDA ’s UVM Framework (UVMF) template generation methodology.”

  • SystemVerilog Constrained Random Handbook

  • Random Directed Low-Power Coverage Methodology - A Smart Approach to Power Aware Verification Closure

    With the advancement in the technology, low-power design and its verification is becoming more complex. Today’s chips have multiple power domains each having multiple operating power modes and dynamically changing voltage levels.

  • Debugging Functional Coverage Models: Get the Most of Out of Your Cover Crosses

    Applying hole analysis on each cover cross independently can lead to misleading results and is sometimes prohibitive due to the sheer number of crosses. Additionally, we introduce a metric, hole effect, that is proportional to the coverage gains that would result upon resolving the highlighted hole. We evaluate our approach on a real processor’s data processing unit to validate its applicability and usefulness for debugging complex functional coverage models.

  • Debugging Functional Coverage Models: Get the Most Out of Your Cover Crosses

    Functional coverage models have grown in complexity to account for the increasing demands of designs today. Traditional and even advanced analysis techniques have yet to evolve to provide the verification engineer with actionable insights on how to debug their functional coverage model. In this paper, we generalize advanced hole analysis techniques to be able to get the most out of cover groups containing multiple cover crosses.

  • UVM and C Tests - Perfect Together

  • Block level testbench (.tgz)

  • Verification Acceleration for ASIC and FPGA Designs

    Modeling large integrated circuits for the workloads required for verification takes more computing than can be accomplished on CPU farms with 1000s of CPUs for many years.

  • Don’t Do It Yourself: Questa VIP Accelerates UVM Testbench Development

    This session will discuss writing constraints to characterize stimulus and configuration, creating prediction models, and defining coverage models with rapid testbench development utilizing the Questa Verification IP configurator to create high quality verification environments.

  • No Testbench? No Problem! We Have a (Formal) App for That

    Formal verification uses mathematical and algorithmic methods to prove exhaustive results, requiring no testbench or stimulus.

  • A Tale of Two Technologies - ASIC & FPGA SoC Functional Verification Trends

    This session discusses the Wilson Research Group Survey on ASIC and FPGA verification trends.

  • Making Verification Fun Again

    The key characteristics of the UVMF: accelerate environment development, reusable, scalable, and emulatable.

  • UVM Monitor

  • Block level testbench

    Example of a block level UVM testbench

  • Five Steps to Quality CDC Verification

    With the number of clock domains increasing in today’s complex ASIC designs, the ability to thoroughly verify clock domain crossings (CDC) has become even more important. As in functional verification, to ensure CDC issues are thoroughly verified, a comprehensive test plan is essential. Based on our experience working with many customers, we developed a five-step planning process for CDC verification.

  • Formal Apps Take the Bias Out of Functional Verification

    An increasingly popular approach has been to employ a comprehensive, constrained-random, coverage driven testbench development flow, such as the Universal Verification Methodology (UVM). Indeed, when random stimulus generation is well executed it often finds bugs “that no one thought of.” However, this method’s success is limited to smaller DUTs as it is essentially impossible to do an exhaustive analysis of large, complex DUTs within a realistic project schedule.

  • Five Steps to Quality CDC Verification

    After having a CDC test plan, an effective CDC verification methodology should include structural, protocol, and metastability verification. This ensures that CDC signals are handled reliably at the design stage, avoiding costly respins after they are fabricated. We will outline how these are applied to block-level and top-level RTL modules.

  • Formal Apps Take the Bias Out of Functional Verification

    When we spend hours, days, or even weeks putting our hearts and minds into creating something, we have a tendency to emphasize its strengths and minimize its weaknesses. This why verification engineers have a blind spot for their own verification platforms. This blindspot, or bias, often leads to overlooking those areas where bugs may lurk, only to emerge at the worst possible time when errors are most costly and take longer to fix.

  • Technical Paper: UVM and C Tests - Perfect Together

  • Effective Elements List and Transitive Natures of UPF Commands

  • The Big Brain Theory: Visualizing SoC Design and Verification Data

  • Using Strong Types in SystemVerilog Design and Verification Environments

    One of the classic debates in computer science is whether a language should have a strongly-or weakly-typed data system. A strongly-typed language does not allow operations on data that are of incompatible types. Having strong types, as in VHDL, helps define intent and avoid errors, but is much more verbose.