You are on page 1of 4

28/07/2016

ASICVerification:StaticTimingAnalysis

More NextBlog

ankitutkarsh1127@gmail.com Dashboard SignOut

ASIC Verification
Hello Everyone, This is My first blog ever. I have created this blog to discuss about various topics in the field of
ASIC. You'll find lot of useful information about verification. Keep visiting this site for more updates.

T U E S D AY, F E B R U A R Y 1 9 , 2 0 0 8

Static Timing Analysis


What is STA?
Static Timing Analysis (STA) is a technique for estimating the delay
of a digital circuit without simulation. Now a days, it is widely
adopted in industry for timing verification. This topic will overview the
basics of static timing analysis.
Search This Blog
How do you ensure after the ASIC is placed and routed, that every
register to register path in the design does not violate the setup and
hold time? This is where STA tools comes into the picture. Those tools
can fully analyze a multimillion gate ASIC in a short amount of time.
The STA comes into the picture twice. Once during synthesis and again
during place and route. Since Synthesis tools are third party tools, they
don't give the precise delays and the delays are based on wire load
models which are approximate only. Place and route tools are silicon
vendor tools and hence provide better information regarding these
delays.

Search

What STA can't do?


About Me
STA can only report the paths which are violating a particular
constraint. It can't make the TIMINGS MEET. STA tools can't analyze the
combinational feedback loops.
The inputs to any STA tools are going to be verilog netlist, Standard
Delay Format (SDF) and Standard Parasitic Extraction Format (SPEF). It
also uses the standard cell and macro library to find out the cell delay,
net delay & clock to Q output delay of a FF. You also need to have a
Design constraint file that will tell the tool about your ASIC. The big
picture of Delay modeling is shown in the following Figure.

Suresh C

Follow

29

View my complete profile

Categories
Digital (18)
http://chipverification.blogspot.in/2008/02/statictiminganalysis.html

1/4

28/07/2016

ASICVerification:StaticTimingAnalysis

Specman Tutorial (12)


Verification (10)
Verilog (8)
Learn C (6)
Timing (6)
Synthesis (5)
General (4)
SOC (4)
Specman (4)
State Machine (4)
Timing Violations:
When your STA tool analyzes your design, it is checking that each path
meets the setup and hold time for the design library that you specify.
Everyone of us very well know, when will setup time violation occurs.
Setup violations occurs when the data path is too slow compared to
the clock speed. The designer can fix the setup violations by reducing
the delay in the data path. Designer can reduce the clock speed to fix
the setup violation, but it is going to be a poor design technique.
Hold violations occurs when data is too fast when compared to the
clock speed. If hold violations are not fixed before the chip is made,
lot of problem occurs unlike setup violation where the clock speed can
be reduced. To fix hold violations, designer can add more delay to the
data path.

DFT (3)
RTL (3)
FPGA (2)
Gate level simulation (2)
Low power (2)
VHDL (2)
VLSI (2)
AMS (1)
CMOS (1)
Clock divider (1)
FIFO (1)
Reset (1)

Timing Constraints:
Archives
Timing constraints are how the designer tells the STA tool about the
timing behavior of the ASIC. The three minimum constraints are
defining the clock, input delay, and output delay. There are four
types of timing paths are available. They are :

2011 (2)
2008 (86)
Sep (5)
Aug (1)

Input to Register (Sync),


Register to Register (Sync),
Register to Output (Sync) and
Input to Output(Async). Each path has a start and endpoint

Jul (5)
Jun (6)
May (10)
Apr (15)

When the clocks are defined, all Register to Register paths are assumed
to be constrained in one clock cycle. A path originates from either an
Input port or a Register clock pin, while an end point is either an
Output port or a Register data pin. All start and end point must be
timing constrained.
False paths:

Mar (27)
Feb (17)
C Basics
C File Handling
C Strings
C Structures
C Pointers and Arrays

A false path is a path, which exists in the chip but it would never be
exercised in the operation of the chip. STA tools can report violations
on false paths because there is no knowledge of circuit function.

C Functions
OVM Seminar in San Diego
Survey: Specman vs Vera

http://chipverification.blogspot.in/2008/02/statictiminganalysis.html

2/4

28/07/2016

ASICVerification:StaticTimingAnalysis

MultiCycle Paths:
A multicycle path is when a signal takes more than one clock cycle to
propagate to the end point.
Calculation of path delays:
The actual path delay is the sum of net and cell delays. For a given
area, average of R and C are calculated for different fanouts. Net
delay is calculated by simply multiplying R with C. For example, The R
value for a gate that drives 3 gates (Fanout = 3) is say 0.036, the C
value for the same gate is for example 0.02, then the net delay is
going to be 0.036*0.02.
Two methods for calculating path delays are lumped and pinpin
models. The main difference b/w the two models is how the paths and
their delays are defined. Delays are classified either by connection or
rise/fall and min/max. For more info. about these delays, readers are
advised to refer verilogHDL by palnitkar.

Specman GUI
STA FAQ
Static Timing Analysis
Clock Skew
Timing properties of a FF
Engineering Change Order
(ECO)
Using System Verilog for
Functional Verification
Engineers Create Record
setting Highfrequency Cir...
The History of the ICs

BlogRoll
Adventures in ASIC digital design
ASIC Planet
Cool Verification

Report generation from STA tools:


Reporting the information stored in STA tool's database allows the user
to identify timing violations and make changes to the design.
PrimeTime is a famous STA tool that provides extensive commands to
report setup, hold, and design rules violations.

Digital Electronics
Digital Verification
Specman Verification
Think Verification

Posted by Suresh at 10:46:00 PM


Labels: Timing

Introduction to VLSI design by IIT


Professor

6 comments:
Phantom said...
You are really doing a wonderful job by putting in some great
topics of our field. Keep on doing it!
February 21, 2008 at 9:39 AM
sree said...
hi,
thank you sir,
it is very useful for the VLSI student like me,
thank you very much
have a good go
January 18, 2009 at 9:02 PM
Anonymous said...
Wow.. it was useful..
http://chipverification.blogspot.in/2008/02/statictiminganalysis.html

3/4

28/07/2016

ASICVerification:StaticTimingAnalysis

February 1, 2011 at 5:52 AM


Priya said...
Absolutely amazing tutorial...You have explained it in so simple
words that anyone can understand the basic funda! Thanks a
ton!
July 6, 2011 at 5:49 PM
Syam said...
its really awesome stuff given here dude... great work....
August 4, 2011 at 6:41 PM
Rengarajan said...
Thanks a lot. good start to STA...
February 8, 2012 at 1:27 PM
Post a Comment

Links to this post


Create a Link

Newer Post

Home

Older Post

Subscribe to: Post Comments (Atom)

http://chipverification.blogspot.in/2008/02/statictiminganalysis.html

4/4

You might also like