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.
Ask this to yourself...
If you write the code of a 2:1 MUX, when can you say it is working properly?
Of course not b4 you have tested it, and you need a tb to test it.
The same is the case of a dw lib. For standalone fn verification you have to write a test-bench for it. Generally these dw IPs are used as part of a bigger design and they are always 'assumed' to be delivering the required functionality.
A testbench is nothing but a piece of code which provides the clocks,reset and stimulus to the DUT. It also samples the output from the DUT and checks whether they are right. If they are right, it reports a success else a failure. This is what a basic testbench does.
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.
