By Topic

Have I really met timing? - validating primetime timing reports with SPICE

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
Thiel, T. ; Semicond. Products Sector, Motorola GmbH, Munich, Germany

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.

Published in:

Design, Automation and Test in Europe Conference and Exhibition, 2004. Proceedings  (Volume:3 )

Date of Conference:

16-20 Feb. 2004