

















Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
These are the Lecture Slides of Functional Verification which includes Reusable Verification Components, Verilog Implementation, Implementation, Autonomous Generation and Monitoring, Input and Output Paths, Verifying Configurable Designs, Reusable Test Harness, Testcase Specific Code, Abstraction etc. Key important points are: Verification Tools, Linting Tools, Simulators, Third Party Models, Waveform Viewers, Code Coverage, Verification Languages, Revision Control, Issue Tracking, Metrics
Typology: Slides
1 / 25
This page cannot be seen from the preview
Don't miss anything!
Verification Tools
Event based Cycle based
Verilog’s 128 possible states to VHDL’s 9 Analog’s current and voltage into digital’s logic value and strength.
Board Verification??? Chip needs to be verified in its target environment – board Do you develop or buy behaviorals for board parts? May seem expensive Ask yourself – If it was not worth designing on your own to begin with, why is writing your own model now justified? Model you develop is not as reliable as the one you buy One you buy is tested by many users, not just yourself Remember – Always more expensive to develop your
licensing it Docsity.com
Some consider this as part of the simulator Most common verification tools used Purpose is to visually inspect design/testbench/verification environment Things to consider: Don’t use viewer to determine if design passes or fails a test
Is there a function or combination of functions that have not been verified?
Specific to verification principles Deficiencies in RTL languages (Verilog and VHDL) Verilog was designed with a focus on describing low-level hardware structures No support for data structures (records, linked lists, etc) Not object oriented VHDL was designed for large design teams Encapsulates all information and communicates strictly through well-defined interfaces
implementation of a verification strategy
Verisity’s Specman Elite Synopsys’ Vera Chronology’s Rave System C
Pertains to a ‘view’ of the file system, known as a configuration
Can refresh to new configurations as needed I.E. You are working a bug and don’t want to corrupt your environment until it is fixed. Once fixed, you grab the ‘current’ configuration which brings you up to date.
What is an issue? How to track it?
This is the simplest tracking method
What is it exactly – word of mouth! You find an issue, you walk over the your co-worker and tell him/her.
Pros:
Individuals are empowered! Simple issues are solved almost immediately
Cons:
There is no history on the problem, history will repeat itself Same issue may be revisited numerous times (no history) Can lead to “finger pointing”