Professional Documents
Culture Documents
report_clock_timing Commands
Doc Id: 031744 Product: IC Compiler
Average User Rating:
Save Article
Tag Article
Send comment
Question:
Source Latencies
For details about source latencies, see the following SolvNet
028398:
Do both report_clock_tree and report_clock_timing commands consider
source latencies?
The following reports show another subtle difference between the two
commands:
icc_shell> report_clock_tree -local_skew
...
============ Local Skew Report ================
Clock: clk
(I: ICG cell pin, N: non-stop pin)
(L: longest arrival, S: shortest arrival, E: arrival derived
from cts exceptions)
Clock arrival time is calculated from the source(s) of the
master clock.
Clock Pin
Latency
Skew
---------------------------------------------------------------------------------FF3/CP
0.74 (S)
FF4/CP
0.96 (L)
0.21
icc_shell> report_clock_timing -type skew
...
Clock: clk
Clock Pin
Latency
Skew
--------------------------------------------------------------------------FF1/CP
0.76
wrp-+
FF2/CP
0.74
0.02
wrp-+
--------------------------------------------------------------------------Clock: div_clk
No local skews.
The reports show a large discrepancy. The report_clock_timing
command sees the
clk and div_clk clocks as two distinct clocks, while the
report_clock_tree command
and clock tree synthesis consider the divided div_clk clock as part
of the clk clock.
To resolve the difference, use the following command:
icc_shell> report_clock_timing -type interclock_skew -from_clock clk
-to_clock div_clk
...
Clock Pin
Latency
Skew
--------------------------------------------------------------------------FF3/CP
0.74
wrp-+
FF4/CP
0.96
-0.21
wrp-+
---------------------------------------------------------------------------
Timing Derating
The report_clock_timing command considers timing derating when
calculating the
clock tree latency. Timing derating is applied by using the
set_timing_derate
command or by using advanced on-chip variation (AOCV). The
report_clock_tree
command does not perform derating, so you do not get an accurate
skew or latencies.
When you run the report_timing command, the latencies are the same
as the results
reported by the report_clock_timing command.
For example,
icc_shell> set_timing_derate -late 1.05
icc_shell> set_timing_derate -early 0.95
icc_shell> report_clock_tree -local_skew
...
Clock: clk
(I: ICG cell pin, N: non-stop pin)
(L: longest arrival, S: shortest arrival, E: arrival derived
from cts exceptions)
Summary
In short, the two commands differ in many ways. If you run into
another situation
that is not explained in this article, contact the Synopsys
Technical Support Center.
Save Article
Question:
Tag Article
Send comment
For example,
icc_shell> set_clock_latency -source 5 pclk
1
## report_clock_timing considers (source latency of 5.00 + network
latency of 0.23)
## 5.00 + 0.23 = 5.23 as latency
icc_shell > report_clock_timing -type latency -from pclk
Clock: PCI_CLK
--- Latency --Clock Pin
Trans
Source
Network
Total
--------------------------------------------------------------------------I_PCI_TOP/I_PCI_WRITE_FIFO/PCI_FIFO_RAM_1/CE2
0.27
5.00
0.23
5.23
wrp-+
--------------------------------------------------------------------------1
icc_shell> report_clock_timing -type skew
**************
**************************
Report : clock timing
-type skew
-nworst 1
-setup
Design : ORCA_TOP
Version: C-2009.06-ICC
Date
: Wed Jul 15 20:13:31 2009
****************************************
Clock: PCI_CLK
-from pclk
Clock Pin
Latency
Skew
--------------------------------------------------------------------------I_PCI_TOP/I_PCI_READ_FIFO/PCI_FIFO_CTL/U1/count_int_reg_3_/CP
5.23
wrp-+
I_PCI_TOP/I_PCI_READ_FIFO/PCI_FIFO_RAM_3/CE1
5.21
0.02
wrp-+
--------------------------------------------------------------------------1
##report_clock_tree considers only network latency as 0.23 and
reports skew
icc_shell> report_clock_tree -from pclk -summary
***************************************
Report : clock tree
Design : ORCA_TOP
Version: C-2009.06-ICC
Date
: Wed Jul 15 20:11:58 2009
********************************
============= Clock Tree Summary ==============
Clock
Sinks
CTBuffers
ClkCells Skew
LongestPath
TotalDRC
BufferArea
----------------------------------------------------------------------------------PCI_CLK
201
4
4
0.02
0.23
0
66.568
*********8