Have I Really Met Timing Validating PrimeTime Timing Reports with Spice

drjiachen

Abstract
At sign-off everybody is wondering about how good the
accuracy of the static timing analysis timing reports
generated with PrimeTime really is. Errors can be
introduced by STA setup, interconnect modeling, library
characterization etc. The claims that path timing
calculated by PrimeTime usually is within a few percent
of Spice don’t help to ease your uncertainty.
When the Signal Integrity features were introduced to
PrimeTime there was also a feature added that was
hardly announced: PrimeTime can write out timing paths
for simulation with Spice that can be used to validate the
timing numbers calculated by PrimeTime. By comparing
the numbers calculated by PrimeTime to a simulation
with Spice for selected paths the designers can verify the
timing and build up confidence or identify errors.
This paper will describe a validation flow for PrimeTime
timing reports that is based on extraction of the Spice
paths, starting the Spice simulation, parsing the
simulation results, and creating a report comparing
PrimeTime and Spice timing. All these steps are done
inside the TCL environment of PrimeTime. It will describe
this flow, what is needed for the Spice simulation, how it
can be set up, what can go wrong, and what kind of
problems in the STA can be identified.

Have I really met timing - validating primetime timing reports with SPICE.pdf (263.78 KB, 下载次数: 23 )

2011-5-21 02:43 上传

点击文件名下载附件

wanglixu2005

下来拜读一下，谢谢分享！

jeffej

Have I Really Met Timing Validating PrimeTime Timing Reports with Spice