Skip to main content Accessibility help
×
Hostname: page-component-7479d7b7d-jwnkl Total loading time: 0 Render date: 2024-07-13T21:35:20.842Z Has data issue: false hasContentIssue false

6 - SystemVerilog and Vera in a verification flow

Published online by Cambridge University Press:  05 August 2012

Dhiraj K. Pradhan
Affiliation:
University of Bristol
Ian G. Harris
Affiliation:
University of California, Irvine
Get access

Summary

Introduction

The goal of this chapter is to illustrate the practical applicability of the simulation-based validation concepts in the book by applying them to a design example. We will use both System Verilog [1] and Vera [2] as hardware-verification languages (HVLs) in which we will implement the entire validation framework for the design example. Simulation is the most widely used technique for verification of design models. The design to be verified is described in a hardware-description language (HDL) and is referred to as the design under verification (DUV). This provides an executable model or models of the DUV. These models could be developed at different levels of abstraction.

A high-level design specification is then analyzed to produce stimulus or input test vectors. The input test vectors are applied to the models. The inputs are propagated through the model by a simulator and finally the outputs are generated. A monitor is used to check the output of the DUV against expected outputs for each input test vector. It is constructed based on an interpretation of the expected design behavior from the specification. If there is any observed deviation from the expected output, a design error is considered to have been found, and debugging tools are used to trace back and diagnose the source of the problem. The problem usually arises from either incorrectly modeled design or incorrectly modeled timing. Once the problem source is identified, it is fixed and the new model is simulated. In an ideal world, the model should be tested for all possible scenarios.

Type
Chapter
Information
Publisher: Cambridge University Press
Print publication year: 2009

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×