Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
As Cadence has acquired Verisity and ther is a strong rumor that "e language" is being pushed as IEEE standard for verification , the prospets of e based verification seems to high.
if you have an E expert in your team, you can choose E, otherwise, using others. E is too difficult to learn, especially there is no experienced engineer mentoring you.
There are always multiple approaches to verify any design. This actually depends of what kind of design do u have and what level of verification is expected to be done.
1. Incase you have small design with and lot of control logic and less data path, I would suggest you to use some tools like Cadence IFV and PSL for assertions. Yes.. I am suggesting ABV (Assertion Based Verification) here...
2. It is also possible to use Specman based environment... which is also robust and solid. This you can use irrespective of whether ur design is control intensive of data path intensive.
3. In case you are just doing a sanity check.. of some basic functionality... then it is okay to go ahead building a verilog testbench...
There are many more things that can be done... u just have to look at what u need to do..
If I can choose ,then Systemverilog,of course!
It is the latest trendy,every vendor can support it and it is free.don't waste so many time in choose language.just throw your engery in finding your bug.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.