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.
Hi tumma,
testing is related to applying test paterns to the chip and verifying its function, for this the chip is designed based on DFT, BIST etc. where as verification is done at hdl or schematic level using simulators applying test vectors through test benchs
Verification is to check whether a chip is designed to its functional specification. Once the functionality is verified, the design can be sent out to fabrication.
During fabrication, some chips will end up with defect (just like any manufacturing process). The goal of testing is to sort out good parts from defective ones.
verification is for assuring that the design implemented is equivalent to the one required in the specification.... what u did is what u wanted? u can ask urself the question of: r we building the design right
validation for instance is when u say: r we building the right design, or is the specification we wrote corresponding to the conceptual intent we wanted
regarding testing, it's when u have already fabricated and u need to find the defected chips to remove them
Hi every one
I understand the diff. in the matter of fabrication,
Can any one tell mi the diff. in the case of designing circuit. for example take opamp.
I have designed an opamp, now I am simulating (checking functionality) the opamp. I am getting some out put.
verification is done before implementation of design on actual hardware so to find out whether there r any flaws in our design. Testing is done after implementation of our design on hardware.Final testing is done to find out whether our fully verified design has been properly converted into fianal circuit
Thank u for your reply...
I need another clarification.
You have said that “Verification is done before implementation of design on actual hardware so to find out whether there r any flaws in our design”.
My question is…
For example consider two cases,
1) I am analyzing opamp circuit (simulating in schematic).
2) I am analyzing same opamp circuit (simulating in schematic) by introducing faults, and I am using DFT/BIST for analyzing the fault.
see the attachment for more detail
As u said... the first case is verification...
In 2nd case I am using DFT/BIST, I know it is a kind of testing but I am doing in circuit level.
For ASIC jargon,
Verification usually means to verify if the circuit/code drawn/written is your intention or not,
Test is usually related to manufacturing.
For conversation,
there are some ambiguity between these 2 words.
=======================================================
So, in the ASIC world,
what you do is still verification.
--> Verify the DFT/BIST function of the chip.
----> In fact, you are preparing for testing. (Instead of doing test itself.)
The purpose of the test is to verify that the design was manufactured correctly
The purpose of the verification is to ensure that a design meets its functional
intent. (---by Janick Bergeron in the book of "Writing Testbenchs")
What u mean functionality.... i don’t know in what way u r trying to say...
Basically testing is of 2 types functionality testing and parametric testing... and it can b further devided in to many types... these will b done after chip has been manufactured. in testing we use term called DUT(Device Under Test).
In the case of Verification the term will be CUT (Circuit under Test). In verification we will be dealing with circuits and all kind of verification like functional, parametric, DFT... Will be done... Once the chip has been Manufactured we will be using the term called Testing.
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.
