2.1 Timing Paths (STA) Basic (Part 1)
2.1 Timing Paths (STA) Basic (Part 1)
VLSI Concepts
Translate page
An online information center for all who have Interest in Semiconductor Industry.
VLSI Basic STA & SI Extraction & DFM Low Power Physical Design Vlsi Interview Questions Job Posting Video Lectures VLSI Industry: Ins
Recommended Book
Search Index
Chapter 1: Digital Background
Chapter 2: Semiconductor backgro
Index
Chapter 3: CMOS Processing
Chapter1 Chapter2 Chapter3 Chapter4 Chapter5 Chapter6 Chapter7 Chapter8 Chapter 4: CMOS Basics
STA & SI
Introduction Static Timing Analysis Clock Advance STA Signal Integrity EDA Tools Timing Models Other Topics Chapter 5: CMOS Layout Design
Part5b -> Examples to calculate the “Maximum Clock Frequency” for different circuits. Bridging Gap Between ► 20
Acdamia and Industry ▼ 20
Part 6a -> How to solve Setup and Hold Violation (basic example)
►
Part 6b -> Continue of How to solve Setup and Hold Violation (Advance examples) Follow
►
Part 6c -> Continue of How to solve Setup and Hold Violation (more advance examples) 333 followers
►
Part 7a -> Methods for Increase/Decrease the Delay of Circuit (Effect of Wire Length On the Slew)
►
Part 7b -> Methods for Increase/Decrease the Delay of Circuit (Effect of Size of the Transistor On the Slew)
▼
Total Pageviews
Part 7c -> Methods for Increase/Decrease the Delay of Circuit (Effect of Threshold voltage On the Slew)
Part 8 -> 10 ways to fix Setup and Hold Violation. 5,788,043
As we have discussed in our last blog (about Basic of Timing analysis that there are 2 types of timing analysis.
Static Timing Analysis
Dynamic Timing Analysis.
Note: There is one more type of Timing analysis: "Manual Analysis". But now a days nothing is 100% Manual. Evey thing is more automated and Subscribe To VLSI EXPERT
less manual. So that we are not discussing right now.
Posts
In this Blog (and few next as a part of this) we will discuss about the Static Timing Analysis. We will discuss Dynamic Timing Analysis later
Comments
on.Static Timing analysis is divided into several parts as per the above mentioned list.
Static timing analysis is a method of validating the timing performance of a design by checking all possible paths for timing violations under worst- "Timing Paths" : Static
Timing Analysis (STA) ►
case conditions. It considers the worst possible delay through each logic element, but not the logical operation of the circuit. basic (Part 1)
► 20
In comparison to circuit simulation, static timing analysis is Basic of Timing ► 20
Analysis in Physical
Faster - It is faster because it does not need to simulate multiple test vectors. Design
More Thorough - It is more thorough because it checks the worst-case timing for all possible logic conditions, not just those sensitized EDN:
SH AR ES
by a particular set of test vectors. "Setup and Hold Time"
: Static Timing Analysis Fo
Once again Note this thing : Static timing analysis checks the design only for proper timing, not for correct logical functionality. (STA) basic (Part 3a) ve
two
"Examples Of Setup So
Static timing analysis seeks to answer the question, “Will the correct data be present at the data input of each synchronous device when the clock
and Hold time" : Static ve
edge arrives, under all possible conditions?” Timing Analysis (STA) Im
basic (Part 3c) ma
In static timing analysis, the word static alludes to the fact that this timing analysis is carried out in an input-independent manner. It locates the es
worst-case delay of the circuit over all possible input combinations. There are huge numbers of logic paths inside a chip of complex design. The "Setup and Hold Time
As
Violation" : Static
advantage of STA is that it performs timing analysis on all possible paths (whether they are real or potential false paths). Timing Analysis (STA) po
However, it is worth noting that STA is not suitable for all design styles. It has proven efficient only for fully synchronous designs. Since the basic (Part 3b) SA
mi
majority of chip design is synchronous, it has become a mainstay of chip design over the last few decades. ap
Delay - "Wire Load
Model" : Static Timing Re
The Way STA is performed on a given Circuit: Analysis (STA) basic fixe
To check a design for violations or say to perform STA there are 3 main steps: (Part 4c) be
sig
Design is broken down into sets of timing paths,
Delay - "Interconnect
Calculates the signal propagation delay along each path Delay Models" : Static
And checks for violations of timing constraints inside the design and at the input/output interface. Timing Analysis (STA)
basic (Part 4b)
The STA tool analyzes ALL paths from each and every startpoint to each and every endpoint and compares it against the constraint that (should) "Time Borrowing" :
Static Timing Analysis
exist for that path. All paths should be constrained, most paths are constrained by the definition of the period of the clock, and the timing
(STA) basic (Part 2)
characteristics of the primary inputs and outputs of the circuit.
10 Ways to fix SETUP
Before we start all this we should know few key concepts in STA method: timing path, arrive time, required time, slack and critical path. and HOLD violation:
Static Timing Analysis
Let's Talk about these one by one in detail. In this Blog we will mainly Focus over Different Types of Timing Paths.
(STA) Basic (Part-8)
Followers
Please see the following fig:
SH AR ES Followers (480) Next
Follow
Timing Path- 4 types of Data Path
PATH1- starts at an input port and ends at the data input of a sequential element. (Input port to Register)
PATH2- starts at the clock pin of a sequential element and ends at the data input of a sequential element. (Register to Register)
PATH3- starts at the clock pin of a sequential element and ends at an output port.(Register to Output port).
PATH4- starts at an input port and ends at an output port. (Input port to Output port)
Clock Path:
In the above fig its very clear that for clock path the starts from the input port/pin of the design which is specific for the Clock input and the end
point is the clock pin of a sequential element. In between the Start point and the end point there may be lots of Buffers/Inverters/clock divider.
Clock path may be passed trough a “gated element” to achieve additional advantages. In this case, characteristics and definitions of the clock
change accordingly. We call this type of clock path as “gated clock path”.
LD pin is not a part of any clock but it is using for gating the original CLK signal. Such type of paths are neither a part of Clock path nor of Data
Path because as per the Start Point and End Point definition of these paths, its different. So such type of paths are part of Clock gating path.
Asynchronous path:
A path from an input port to an asynchronous set or clear pin of a sequential element.
As you know that the functionality of set/reset pin is independent from the clock edge. Its level triggered pins and can start functioning at any time
of data. So in other way we can say that this path is not in synchronous with the rest of the circuit and that's the reason we are saying such type
SH AR ESof path an Asynchronous path.
There are few more types of path which we usually use during timing analysis reports. Those are subset of above mention paths with some
specific characteristics. Since we are discussing about the timing paths, so it will be good if we will discuss those here also.
Critical Path:
In short, I can say that the path which creates Longest delay is the critical path.
Critical paths are timing-sensitive functional paths. because of the timing of these paths is critical, no additional gates are allowed to
be added to the path, to prevent increasing the delay of the critical path.
Timing critical path are those path that do not meet your timing. What normally happens is that after synthesis the tool will give you a
number of path which have a negative slag. The first thing you would do is to make sure those path are not false or multicycle since it
that case you can just ignore them.
Taking a typical example (in a very simpler way), the STA tool will add the delay contributed from all the logic connecting the Q output of one flop
to the D input of the next (including the CLK->Q of the first flop), and then compare it against the defined clock period of the CLK pins (assuming
both flops are on the same clock, and taking into account the setup time of the second flop and the clock skew). This should be strictly less than
the clock period defined for that clock. If the delay is less than the clock period, then the "path meets timing". If it is greater, than the "path fails
timing". The "critical path" is the path out of all the possible paths that either exceeds its constraint by the largest amount, or, if all paths pass,
then the one that comes closest to failing.
False Path:
Physically exist in the design but those are logically/functionally incorrect path. Means no data is transferred from Start Point to End
Point. There may be several reasons of such path present in the design.
Some time we have to explicitly define/create few false path with in the design. E.g for setting a relationship between 2 Asynchronous
Clocks.
The goal in static timing analysis is to do timing analysis on all “true” timing paths, these paths are excluded from timing analysis.
Since false path are not exercised during normal circuit operation, they typically don't meet timing specification,considering false path
during timing closure can result into timing violations and the procedure to fix would introduce unnecessary complexities in the design.
There may be few paths in your design which are not critical for timing or masking other paths which are important for timing
optimization, or never occur with in normal situation. In such case , to increase the run time and improving the timing result , sometime
we have to declare such path as a False path , so that Timing analysis tool ignore these paths and so the proper analysis with respect
to other paths. Or During optimization don't concentrate over such paths. One example of this. e.g A path between two multiplexed
blocks that are never enabled at the same time. You can see the following picture for this.
False Path
Here you can see that False path 1 and False Path 2 can not occur at the same time but during optimization it can effect the timing of another
path. So in such scenario, we have to define one of the path as false path.
Same thing I can explain in another way (Note- Took snapshot from one of the forum). As we know that, not all paths that exist in a circuit are
"real" timing paths. For example, let us assume that one of the primary inputs to the chip is a configuration input; on the board it must be tied
either to VCC or to GND. Since this pin can never change, there are never any timing events on that signal. As a result, all STA paths that start at
this particular startpoint are false. The STA tool (and the synthesis tool) cannot know that this pin is going to be tied off, so it needs to be told that
these STA paths are false, which the designer can do by telling the tool using a "false_path" directive. When told that the paths are false, the STA
tool will not analyze it (and hence will not compare it to a constraint, so this path can not fail), nor will a synthesis tool do any optimizations on that
particular path to make it faster; synthesis tools try and improve paths until they "meet timing" - since the path is false, the synthesis tool has no
work to do on this path.
Thus, a path should be declared false if the designer KNOWS that the path in question is not a real timing path, even though it looks like one to
the STA tool. One must be very careful with declaring a path false. If you declare a path false, and there is ANY situation where it is actually a real
path, then you have created the potential for a circuit to fail, and for the most part, you will not catch the error until the chip is on a board, and
(not) working. Typically, false paths exists
MultiCycle Path:
SH AR ES A multicycle path is a timing path that is designed to take more than one clock cycle for the data to propagate from the startpoint to the
endpoint.
A multi-cycle path is a path that is allowed multiple clock cycles for propagation. Again, it is a path that starts at a timing startpoint and ends at a
timing endpoint. However, for a multi-cycle path, the normal constraint on this path is overridden to allow for the propagation to take multiple
clocks.
In the simplest example, the startpoint and endpoint are flops clocked by the same clock. The normal constraint is therefore applied by the
definition of the clock; the sum of all delays from the CLK arrival at the first flop to the arrival at the D of the second clock should take no more
than 1 clock period minus the setup time of the second flop and adjusted for clock skew.
By defining the path as a multicycle path you can tell the synthesis or STA tool that the path has N clock cycles to propagate; so the timing check
becomes "the propagation must be less than N x clock_period, minus the setup time and clock skew". N can be any number greater than 1.
A Single-cycle path is a timing path that is designed to take only one clock cycle for the data to propagate from the startpoint to the endpoint.
Both are inter-related so I am describing both in one place. When a flip flop to filp-flop path such as UFF1 to UFF3 is considered, one of the flip-
flop launches the data and other captures the data. So here UFF1 is referred to "launch Flip-flop" and UFF3 referred to "capture flip-flop".
These Launch and Capture terminology are always referred to a flip-flop to flip-flop path. Means for this particular path (UFF1->UFF3), UFF1 is
launch flip-flop and UFF3 is capture flip-flop. Now if there is any other path starting from UFF3 and ends to some other flip-flop (lets assume
UFF4), then for that path UFF3 become launch flip-flop and UFF4 be as capture flip-flop.
The Name "Launch path" referred to a part of clock path. Launch path is launch clock path which is responsible for launching the data at launch
flip flop. And Similarly Capture path is also a part of clock path. Capture path is capture clock path which is responsible for capturing the data at
capture flip flop.This is can be clearly understood by following fig.
Launch Clock Path (Launch Path) and Capture Clock Path (Capture path)
Here UFF0 is referred to launch flip-flop and UFF1 as capture flip-flop for "Data path" between UFF0 to UFF1.So Start point for this data path is
UFF0/CK and end point is UFF1/D.
One thing I want to add here (which I will describe later in my next blog- but its easy to understand here)-
Launch path and data path together constitute arrival time of data at the input of capture flip-flop.
Capture clock period and its path delay together constitute required time of data at the input of capture register.
Note: Its very clear that capture and launch paths are correspond to Data path. Means same clock path can be a launch path for one data path
SH AR ESand be a capture path for another datapath. Its will be clear by the following fig (source of Fig is From Synopsys).
Same clock path behave like Capture and Launch path for different Data path.
Here you can see that for Data path1 the clock path through BUF cell is a capture path but for Data path2 its a Launch Path.
In the above fig, The longest path between the 2 flip-flop is through the cells UBUF1,UNOR2 and UNAND3. The shortest path between the 2 flip-
flops is through the cell UNAND3.
I have tried my best to capture all the important points related to the Timing Paths. Please Let me know If anything is missing here.
Reactions: Excellent (20) Good (2) Interesting (4) Need More (0)
82 comments:
samiappa sakthikumaran March 10, 2011 at 9:48 PM
Hi sir, if for a certain timing contraint u give for ex: let me say that my clock period is 5ns and if slack is met using synopsys primetime, so can i say my
frequency of operation of my whole ckt is 200MHz ??? kindly reply. Thanks
Reply
Replies
Reply
Hi,
Fabulous work u r doing. Reaaly the topics covered in this blog are helping me a lot.
Reply
Hi @Samiappa -- you are right.. if slack is meeting.. then you can say .. but still there is a "can".. :) means its not 100% true. There are other factors
also. Please see my other blogs for details...
Hi,
I have some doubts in basics of CTS. How can i communicate with you to discuss about my queries? i mailed you yesterday ( mail ID i got from this
blog - [email protected] ) but the mail delivery is failed. If you don't mind may i have your right mail ID.
I will be more help-full if you can reply to my queries..Since i have more queries i'm asking you to provide any other option which i can communicate
with you or do let me know if i shall post my queries here.
There is a typo in my mail id ( which you have mentioned here)-- Correct one is
[email protected]
Reply
I have sent a mail with list of queries to the above given mail ID.
Regards,
Indu.
Reply
Reply
hello sir,
this is Harish, i just want to say few words abt it. ur blogs are so understandable way to earn knowledge about timing analysis and i recall totally what i
know....
and i got some topics from it easily to remember..
so u did a great job..
Reply
Replies
Reply
Reply
Thanks for sharing your info. I really appreciate your efforts and I will be waiting for your further write ups thanks once again.
Vee Eee Technologies
Reply
hai sir
this blog was very usefull for my work and easy to understand
great job............
Reply
hai sir
this blog was very usefull for my work and easy to understand
great job............
Reply
regards
chandrakant
Reply
regards
chandrakant
Reply
Reply
Reply
Reply
Hello Sir,
Reply
Replies
Examples Of Setup and Hold time" : Static Timing Analysis (STA) basic (Part 3c)
Reply
You should write a book for Standford and IITians. Existing articles and books on this topic shows author themselves do not know what it is. But you
explained it perfectly. So you are expert.
Reply
Thanks,
Shivaji.
Reply
Reply
Reply
Replies
regarding the Floorplan/Placement/Routing - you have to wait little bit. But Sure i will update those info also.
Reply
This is excellent. Please also details about test modes in STA ( scan cap dc, scan cap ac , scan shift, jtag, rambist ).
Reply
Reply
Replies
Can you please tell the difference between longest path and critical path with example. I am confused with these paths.
Thanks,
Deepthi
You should not be confused. critical path are that path - which has high impact on the design timing. It can be short or may be long path.
Point is - if there is any issue in the critical path then you have to fix that one first. you can't even compromise with that path.
Longest path .. means more number of gates and more delay in that path.
Reply
Reply
Reply
Hi
Capture clock period and its path delay together constitute required time of data at the input of capture register.
i didn't get this point clearly ..is the capture clock period and clock period same or its the delay of the capture clock path
Reply
Replies
Reply
Replies
I will try...
Reply
SH AR ES
Umadevi Ravindrachari November 7, 2013 at 6:59 PM
hello sir i need basis of static timing verification ....and concept of static timing analysis ....i need overview for about this concepts please upload as
soon as possible.......
Reply
Replies
Reply
A great work on STA is given as a nutshell.Thanks a lot.It would be appreciable if you could add details on Statistical Static Timing Analysis
(SSTA)also.
Reply
Replies
Reply
Hello Sir,
Thank you very much for ur efforts in explaining about STA.
I have a doubt in MCP example explanation were, you have stated
"However, if you have a signal in the 60MHz domain that indicates the phase of the 30MHz clock, you can design a circuit that allows for the full 33ns
for the clock crossing, then the path from flop30 -> to flop60 is a MCP (again with N=2)."
why is path between flop30 to flop60 MCP as the launching flop30 operates in slower clock it gives enough time to get sync with flop60 as the next
data from flop30 will be launched after two clock cycles at flop60. ( I am taking 30Mhz clock as main clock, as assumed by your statement).
So may be data from flop60 to flop 30 may take 2 cycles as flop60 as to keep its data stable for complete 2 cycles of its clock (60Mhz clk) to sync with
flop30.
Thanks
vijay
Reply
why setup time is large compared to hold time????can any one give me answer???
Reply
Replies
Reply
Replies
Reply
What would happen if the clock period used were shorter than the maximum signal propagation time through the circuit?
Reply
Awesome stuff
Reply
Replies
Reply
sir do you have information about to solve problems on combinational circuits delays??
i want more no 0f problems and solutions to calculate max frequency in both combinational and sequential circuits
plz help me sir
Reply
Follow by Email
Fixing Setup and Fixing Setup and Maximum Clock "Delay - Timing path Delay -
Hold Violation : St... Hold Violation : St... Frequency : Static... Delay" : Static Tim... "Interconnect Dela...
www.vlsi-expert.com www.vlsi-expert.com www.vlsi-expert.com www.vlsi-expert.com www.vlsi-expert.com
SH AR ES
"Setup and Hold Why VLSI Industry Basic of Timing Design constraint : 5 Steps to Build
Time Violation" : S... Reluctant to Hire F... Analysis in Physic... Maximum Fanout Career in VLSI
www.vlsi-expert.com www.vlsi-expert.com www.vlsi-expert.com www.vlsi-expert.com www.vlsi-expert.com
AddThis