Home Articles Main Get Hooked

Search

Get Hooked PDF Print E-mail
User Rating: / 1
PoorBest 
Thursday, 24 December 2009 15:45

Changing an existing eVC for new project requirements is a grueling task. It’s really painful for any eVC developer to witness his creation being torn apart by an end user, but a little prudence from the developer can result into longevity of eVC. Want to learn how to do it? We’ll get there in a minute.

 

But first, I’d like you guys to meet M.P. Rashid - Think Verification’s first guest author. He is a verification engineer (how else) at Tata Elxsi in Banglore. He’s really enthusiastic about verification with Specman and a regular reader of Think Verification (way to go!). Today he’s going to talk about using hook methods (hooks) efficiently, which is a concept we should all get familiar with.

Before we get started - just a quick reminder that if you would like to share your thoughts about functional verification, Think Verification warmly welcomes guest authors and bloggers.

Ok, fasten your seatbelts folks - you’re about to Get Hooked:

Download the arcitle [pdf]
Download code example [e file]

 
More articles :

» Specman Compiled Mode

This is a really short tutorial that demonstrates the entire process of compiling and running a simulation with NC-Verilog & Specman (using compiled specman).

» VMM Hackers Guide - Default Behavior For Your BFM

Here's a short tutorial on how to implement a default behavior for your BFM using VMM. Some protocols require constant activity on their interface even when you don't have any data to transmit. This means you must have a mechanism that drives idle...

» Smart Constraints In SystemVerilog

Constraints are our best friends when it comes to random generation. They allow us to limit the range of possible scenarios/values as much as we like, from the level of "everything is allowed" down to the level of such heavy constraints that really...

» Verification Documents - Love Them, Hate Them, But You Can't Ignore Them

Verification Plan (or Test Plan) and Coverage Plan are two documents that specify the features to be tested in the verification process. The first document usually lists the DUT features that need to be covered and the latter - the coverage points...

» Let The New Game Begin

Things are changing. The EDA industry is changing, and the verification world is changing (check out Janick Bergeron's inspiring at SNUG San Jose for a glimpse of the future of verification). One of the major challenges we’re already facing today...

Add comment


Security code
Refresh

Copyright © 2019 Think Verification - Tips & Insights on ASIC Verification. All Rights Reserved.
Joomla! is Free Software released under the GNU/GPL License.