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.
oh, that some basic stuff:
1- write spec/verification plan
2- write RTL & TB
3- write tests (simulation)
4- this code could test ON FPGA or CPLD (two differents technologies, depend of your goal)
5- synthesis/DFT to your technology target
6- place/CTS/hold/Route
7- STA
8- along 5-6-7, LEC & ATPG
1 to 3 is mainly the frontend
5 to 8 is mainly the backend
depending of the fpga goals, from only checks in reel world and for firmware/software development or for sell contain in fpga (I don't know the trade off of this)
When you synthesize a code you are actually going to put it in hardware and it generates fitter settings,but simulation is only for conformation of code with respect to time instance.for example some statements such as (wait for 1 ns, after 20 ns) is not
synthesizable because in HW one cannot ask to wait for a particular time.But in simulation you check that your results arrive
after a wait of 1 ns..We do this to make sure that if a signal a changes based on signal b, signal b is stable enough to make
change in signal a.if signal b is changing at the same time as signal a output may not be stable. simulation just give you an idea of how the HW will function at a particular time stamp.
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.