( ESNUG 282 Item 7 ) ------------------------------------------------ [2/26/98]
Subject: (ESNUG 280 #7 281 #1) Need Help Doing Synopsys-HSPICE Correlation
> First of all, thanks for all the great information presented in the ESNUG
> postings. We are doing some Synopsys to HSPICE correlation. I am
> interested if anyone has an idea of how to automatically generate the
> input vector that correlates to the report_timing static analysis. In my
> particular case I am dealing with an asynchronous logic block, so there
> are no flip flops to disturb the path. Any ideas anyone?
>
> - Dave Schaefer
> Logical Silicon Solutions
From: Tom Ho <tom@iota.com>
John,
We found something interesting in the Synopsys timing report recently
that I had to use a better Timing Analyzer to cross check the timing
reports from Synopsys. We put 9999 in some of the impossible paths
in the Synopsys library file. Those 9999s showed up on the timing report.
In order to correlate between HSPICE and the other Timing Analyzer,
we used a Transistor level Timing Analyzer we have (may be it is like
PathMill from Synopsys). It can report the critical path easily and extract
a HSPICE netlist of the critical path with all the nodes initialized
automatically. You can just take the SPICE deck to run HSPICE. We have
accuracy of less than 3%. This was how we calibrate the accuracy of our
Synopsys library files, and the our Timing Analyzer.
I guess people can use Anagram, TimeMill, PathMill, ...etc to perform
the correlation. It is just that the timing reports from Synopsys are
quite rough. Good luck.
- Tom Ho
IOTA Technology Inc
|
|
