Hi Ahmad,
The ideal QA tool will check the integrity of every single file and
re****ts any single change between PDK versions. This ideal tool is
unfortunately a utopia that does not exist in a real world. We have
tried to make this with 2 or 3 of my colleagues in my former company
and we managed to get something very powerful but it does not prevent
from leaking and letting couple of bugs going through =85
The duties of such a tool is to run all the flows sup****ted by the
PDK, not only on inverters but real-case designs as well.
In other words, you have to make modules for :
Digital/Analog/AMS/RF FE simulation (DC/AC/Tran/Noise =85)
DRC
LVS
RC Extraction
Dummy filling
Layout fini****ng
=85
Instantiate all the sup****ted devices, with the most significant
parameter sets, insure that they instantiate well, netlist well, call
the pcells well, run the callbacks well, check the CDFs, the Model
files, pass the DRC, well exctracted by the LVs engine, well extracted
by the Parasitic extractor engine =85 and That=92s only a little bit !
Run the DRC flows, the LVS Flows, RCX, =85
Well, the list is very long and It=92s very hard to achieve.
I learnt over my experience that the best way in QA-ing a PDK is to
run it on real designs (recent tapeouts for example).
The QA tool we made was a huge Perl engine which runs bits of Skill,
Shell, Eldo (I was not using ocean/spectre at this time)
That=92s a pretty heavy stuff to tackle!
Good luck anyway!
Riad.
|
