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

2075 Results

  • Code Coverage

    This session is an introduction to various code coverage metrics and how to apply them.

  • Test Planning

    This session shows how you can create a test plan that systematically captures all the functionality in your design so you can test it.

  • Applied Assertions

    This session discusses how to use assertions in a design, and then demonstrates how to insatiate an OVL checker into a VHDL design.

  • Transactions

    This session shows you how to create a transaction level test bench using modules instead of object.

  • Self-Checking Testbenches

    This session demonstrates how to combine predictors and comparators to form a self-checking testbench.

  • Automatic Stimulus

    This session introduces constrained-random stimulus for automatic stimulus generation.

  • Functional Coverage

    This session shows you how to implement functional coverage using SystemVerilog covergroups.

  • Using the UVM Register Layer

    Slides from DAC 2012 where John Anysley from Doulos shares the Architecture of the Register Layer, The Register Model and Running Register Sequences.

  • Siemens EDA has Accellera's Latest Standard Covered

    If you can't measure something, you can't improve it. For years, verification engineers have used "coverage" as a way to measure completeness of the verification effort. Of course, there are many types of coverage, from different types of code coverage to functional coverage, as well as many tools, both dynamic and static, that provide coverage information.

  • Is Intelligent Testbench Automation For You?

    Intelligent Testbench Automation (iTBA) is being successfully adopted by more verification teams every day. There have been multiple technical papers demonstrating successful verification applications and panel sessions comparing the merits to both Constrained Random Testing (CRT) and Directed Testing (DT) methods. Technical conferences including DAC, DVCon, and others have joined those interested in better understanding this new technology.

  • Automated Generation of Functional Coverage Metrics for Input Stimulus

    Questa inFact allows for graphical definition of the coverage goals and can, with the 10.1 release, automatically generate SystemVerilog covergroups from this definition, including the exclusions needed to accurately represent the achievable coverage. This article describes how this capability can simplify the definition of more comprehensive stimulus coverage metrics.

  • Targeting Internal-State Scenarios in an Uncertain World

    The challenges inherent in verifying today's complex designs are widely understood. Just identifying and exercising all the operating modes of one of today's complex designs can be challenging. Creating tests that will exercise all these input cases is, challenging and labor-intensive. Using directed-test methodology, is challenging to create sufficiently-comprehensive tests to ensure design quality, due to the amount of engineering effort needed to design, implement, and manage the test suite.

  • Virtualization Delivers Total Verification of SoC Hardware, Software, and Interfaces

    With the majority of designs today containing one or more embedded processors, the verification landscape is transforming as more companies grapple with the limitations of traditional verification tools. Comprehensive verification of multi-core SoCs cannot be accomplished without including the software that will run on the hardware. Emulation has the speed and capacity to do this before the investment is made in prototypes or silicon.

  • On the Fly Reset

    A common verification requirement is to reset a design part of the way through a simulation to check that it will come out of reset correctly and that any non-volatile settings survive the process. Almost all testbenches are designed to go through some form of reset and initialization process at their beginning, but applying reset at a mid-point in the simulation can be problematic.

  • Relieving the Parameterized Coverage Headache

    Modern FPGA and ASIC verification environments use coverage metrics to help determine how thorough the verification effort has been. Practices for creating, collecting, merging and analyzing this coverage data is documented for designs operating in a single configuration. However, complications arise when parameters are introduced into the design, especially when creating customizable IP. This article discusses the coverage-related pitfalls and solutions when dealing with parameterized designs.

  • Four Best Practices for Prototyping MATLAB and Simulink Algorithms on FPGAs

    Chip design and verification engineers often write as many as ten lines of test-bench code for every line of RTL code that is implemented in silicon. They can spend 50% or more of the design cycle on verification tasks. Despite this level of effort, nearly 60% of chips contain functional flaws and require re-spinning. Because HDL simulation is not sufficient to catch system-level errors, chip designers now employ FPGAs to accelerate algorithm creation and prototyping.

  • Better Living Through Better Class-Based SystemVerilog Debug

    SystemVerilog 1 UVM 2 class-based testbenches have become as complex as the hardware under test, and are evolving into large object-oriented software designs. The usual RTL debugging techniques must be updated to match this new complexity. Debugging tools are addressing these complexities, but this article will describe techniques and approaches that can be used to help debug these complex environments without advanced debug tools.

  • Introduction to Metrics

    This session provides an introduction and motivation for introducing metrics-driven processes into your flow.

  • The Driving Forces for Change

    This session examines the issues that are motivating change and the need for metrics-driven processes.

  • What Can Metrics Tell Us?

    This session expand our discussion on what metrics can tell us by providing examples for various common processes within today’s SoC verification flow.

  • What's Needed to Address the Problem?

    This session discusses four important aspects of a successful metrics-driven process.

  • What's Needed to Adopt Metrics?

    This session discusses important aspects of an implementation that should be considered when architecting a solution.

  • Evolving Trends in Functional Verification

    2012 Wilson Research Group Functional Verification Study Results

  • What to Expect After Adopting the Metrics

    This session provides a conclusion of what benefits to expect after you adopt metrics-driven processes.

  • Metrics in SoC Verification

    In this track, we take a broader view of metrics—beyond traditional coverage measurements—that identify a range of metrics across multiple aspects of today’s SoC functional verification process. We then discuss other important considerations when integrating metrics into a project flow, such as metric categorization, run-time control, data management, and reporting and analysis.