Scribd
Upload
221 views3 pages

Report - Timing Switches

The document outlines various report timing switches used for analyzing path timing in a design, detailing options for delay types, path types, and reporting modes. It explains the differences between path-based analysis (PBA) modes and their impact on timing reports, particularly in relation to worst paths and slack values. Additionally, it provides insights into specific switches for reporting paths, significant digits, and other parameters related to timing analysis.

Uploaded by

mbalaji00000
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
221 views3 pages

Report - Timing Switches

The document outlines various report timing switches used for analyzing path timing in a design, detailing options for delay types, path types, and reporting modes. It explains the differences between path-based analysis (PBA) modes and their impact on timing reports, particularly in relation to worst paths and slack values. Additionally, it provides insights into specific switches for reporting paths, significant digits, and other parameters related to timing analysis.

Uploaded by

mbalaji00000
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

REPORT TIMING SWITCHES

Report_timing : By default, it checks and generates a report of max path timing.


1. “-delay_type”:
a. max: Specifies the path type. Considers max delay values of cells, nets to calculate the arrival and required
times.
b. min: Specifies the path type. Considers min delay values of cells, nets to calculate the arrival and required
times.
2. “-through”: Reports the path and slack, specifying an arrow indication mark “<-“ at the pin we mentioned in
the “switch -through”
3. “-path_type”:
a. full: Specifies detailed arrival path with delays of all design objects throughout the path
b. full_clock: Specifies detailed arrival path and detailed clock path
c. full_clock_expanded:
4. “-slack_lesser_than”: Reports only paths with slack lesser than specified limit.
5. “-pba_mode”:
a. none: Path Based Analysis is not applied. It analyses and reports in GBA mode which takes worst timing on
particular node, updates timing and reports. So, it takes less time.
b. path: Path Based Analysis is applied to paths. It takes more time as it no need to pick the worst path. It
calculates for that particular path and reports the timing.
c. exhaustive: Path Based Analysis is applied to paths

Difference between path and exhaustive:


6. “-nworst”: Reports the n worst paths i.e n violating paths in the design.
We could clearly observe the difference between -pba_mode switches (-path and -exhaustive) when we consider
the -nworst.
-pba_mode: Gives quick report of only the worst path. It checks for the worst path, when we perform changes
to fix that path, it applies to that path and updates timing in that path and reports the same path. And if slack is
positive we are good. It won’t check for remaining paths, and report the worst slack of the design then. Still
there might be chances of violating paths.
 To get those violating paths, we perform -pba_mode exhaustive.
-pba_mode exhaustive: Gives the report of worst path. When we perform changes to fix that path, it applies
to that path, updates timing and this time it reports the -nworst path i.e the other most violating path having
worst slack.

Understanding:
Whenever we perform update_timing, tool considers all nodes (all input nodes and output nodes), and then it
will stamp it as worst timing which is coming to that node. This is what happens in update_timing.
When we are giving a switch “-pba_mode none” i.e GBA, which is taking the worst timing on that particular
node which is already stemmed in update_timing, so it’s taking the least time because it just has to pick that
value and give us the report. So, GBA takes less time. But is more pessimistic.

- Sonika M
REPORT TIMING SWITCHES

PBA on other side, is taking more time because it doesn’t have to pick that particular worst value which is
already arrival time mapped in the design. It actually has to calculate the particular path and then only it has to
give the report.

Suppose let’s consider a rough idea as below –

Suppose we did report_timing -pba_mode path,

 We got report from F1 to F’, the path considered was the logic between F1 & F’ represented with “Black Line”
We got some -ve slack. Let’s say -30ps
We made some changes like Vt swapping etc.
Then update_timing.
Now when we report_timing -pba_mode path.
Now we get slack -20ps(let’s say).
So, we generally think our WNS is -20ps now.

But tool didn’t consider the remaining paths, let’s say here the logic between F1 & F’ marked with “Red Line”
is having a slack of -27ps which is the worst slack now which could be reported only when we give the switch
“-nworst”.

But, if we give the switch “-exhaustive”, the tool will by default check all the paths between the corresponding
start and endpoints and give the worst slack.

“-exhaustive” considers till “nworst”. It considers all paths and update timing of all paths.

- Sonika M
REPORT TIMING SWITCHES

Experiment:
When I reported timing giving the switch “-nworst 3 -max_paths 5”,
it reported total 5 paths.
For all 5 paths, the startpoint is same.
1st 3 paths reported different endpoints, 4th path’s endpoint is same as 1st paths’s.
5th paths’s endpoint is same as 2nd path.
When I reported “-max_paths 1 -nworst 5”, it reported only 1 path.

My Observation:
-nworst count refers to “no.of different startendpoints”
-max_paths count refers to “no.of worst paths for each startendpoints”

7. “-start_end_pair”: Reports paths for each pair of startpoint and endpoint based on connectivity.
8. “-significant_digits": Reports that many significant digits in slack value
9. “-nosplit”: Provides detailed combinational path delays in arrival path
10. “-nets”: Reports nets as well
11. “-physical”: Reports the physical coordinates as well
12. “-transition_time”: Reports the transition at each pin
13. “-capacitance”: Reports capacitance at each load pin
14. “-derate”: Reports the derate values at each pin
15. “-crosstalk_delta”: Reports the SI enabled delay values at each pin

- Sonika M

You might also like