Home SystemVerilog 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 :

» To Randomize Or Not To Randomize

One of my former colleagues once revealed the fact that she had no less than 70 pairs of shoes. That’s right, seventy! She had been very good at her job and by no means had any plans to start her own shoe business so I asked myself why on earth...

» Method Manipulation In SV and e

If you're familiar with SystemVerilog and taking your first steps in e (or vice versa) you might find this useful. Here are some of the most common method manipulations that you''ll need to master and how you should go about implementing them in e...

» Review - Verification Leadership Seminar

How many of you have tried to cut on coffee? or even quit drinking coffee altogether? I guess a lot. Well, personally I’ve given up on trying but you know what? there’s actually something worse than having 8 cups of coffee per day - it’s the...

» Don't Be SYSsy

Anyone who’s ever worked with me knows that I have several weaknesses. One of them is extra sensitivity to things that reside under sys (global.sys) in Specman/e. If this is Chinese to you then you’re probably a SystemVerilog guy: "sys" is the...

» 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...

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.