Logical Correlation Analysis on Victim and Aggressor Pairs With the Same Sense

Search SolvNet

Go

submit

Advanced

SYNOPSYS.COM |FEEDBACK |SITE MAP |HELP |SIGN OUT

Documentation
HOME

Support

Downloads

Training

Methodology

My Profile

SOLVNET ARTICLE

Logical Correlation Analysis on Victim and Aggressor Pairs

SAVED ARTICLES

With the Same Sense

TAGS

None

Doc Id:
1464951

Product:
PrimeTime-SI

Last Modified:
03/20/2014

Average User Rating:

Save Article

(1)Rate Article:

Tag Article

Print

Send comment

Email

Question:
For the following circuit, why does the report_delay_calculation -crosstalk command on N2 filter N1 by logical
correlation?
Figure 1: Circuit example

Annotated max rise delta transition: 0.00984211 pin transition: 0.277744

Annotated max fall delta transition: 0.0272156 pin transition: 0.320349
Attributes:
A - aggressor is Active
C - aggressor is a composite aggressor
E - aggressor is screened due to user Exclusion
I - aggressor has Infinite arrival with respect to the victim
L - aggressor is screened due to Logical correlation
N - aggressor does Not overlap for the worst case alignment
S - aggressor is screened for Small bumps
...
Victim is rising:
Victim
Coupling
Driver
Clocks
Net
Cap
Lib Cell
-------------------------------n1
0.034665
sdnrq4
clk
Aggressor
Net
--------n7138
n2

Coupling
Cap
--------0.002840
0.010805

Driver
Lib Cell
--------xr02d1
bufbd7

Clocks

Attributes

--------clk
clk

-----------S
L

Victim is falling:
Victim
Coupling
Net
Cap
----------------n1
0.034665

Driver
Lib Cell
--------sdnrq4

Clocks

Driver
Lib Cell
--------xr02d1
bufbd7

Clocks

Attributes

--------clk
clk

-----------S
L

Aggressor
Net
--------n7138
n2

Coupling
Cap
--------0.002840
0.010805

Switching Bump
(ratio of VDD)
----------------

--------clk
Switching Bump
(ratio of VDD)
----------------

Answer:
There are two scenarios of an aggressor being filtered by logical correlation. The first scenario is shown in the following
figure.
Figure 2: Logical Correlation of Aggressors

https://solvnet.synopsys.com/retrieve/1464951.html[8/26/2016 11:18:11 AM]

Add Tags

Logical Correlation Analysis on Victim and Aggressor Pairs With the Same Sense

The two aggressors are connected with an inverter. If you set the si_analysis_logical_correlation_mode variable
to false, PrimeTime does not consider the logical relationship between the two aggressors; it calculates crosstalk delay
as the waveforms shown in the bottom left of Figure 2. However, in reality, those waveforms cannot exist because of
the inverted nature of those two aggressors. To reduce such pessimism, set the
si_analysis_logical_correlation_mode variable to true (the default). The waveforms in this case are shown in the
bottom right of Figure 2. In this scenario, only the aggressor causing the largest crosstalk bump is active, while the
other is filtered. The following report example shows this scenario:
from report_delay_calculation -crosstalk -min
Victim is rising:
...
Aggressor
Coupling
Net
Cap
----------------aggr_1
0.000431
aggr_2
0.000571

Driver
Lib Cell
--------inv0d1
nd02d1

Clocks

Attributes

--------clk
clk

-----------A
L

Victim is falling:
...
Aggressor
Coupling
Net
Cap
----------------aggr_1
0.000431
aggr_2
0.000571

Driver
Lib Cell
--------inv0d1
nd02d1

Clocks

Attributes

--------clk
clk

-----------A
L

Switching Bump
(ratio of VDD)
---------------0.016373
-

Switching Bump
(ratio of VDD)
---------------0.016816
-

from report_delay_calculation -crosstalk -max

Victim is rising:
...
Aggressor
Coupling
Net
Cap
----------------aggr_1
0.000431
aggr_2
0.000571

Driver
Lib Cell
--------inv0d1
nd02d1

Clocks

Attributes

--------clk
clk

-----------A
L

Victim is falling:
...
Aggressor
Coupling
Net
Cap
----------------aggr_2
0.000431
aggr_1
0.000571

Driver
Lib Cell
--------inv0d1
nd02d1

Clocks

Attributes

--------clk
clk

-----------A
L

Switching Bump
(ratio of VDD)
---------------0.016373
-

Switching Bump
(ratio of VDD)
---------------0.016816
-

In the minimum delay analysis, aggr_1 is not filtered, and aggr_2 is filtered in both cases when the victim is rising and
falling. However, in maximum delay analysis, aggr_2 is filtered when victim is rising, and aggr_1 is filtered when victim
is falling. The reason is due to the bump size, which can be justified by looking at the bump with logical correlation
mode off:
pt_shell> report_attribute [get_nets victim] -application
...
test
victim string
si_xtalk_bumps_max_fall { aggr_2
test
victim string
si_xtalk_bumps_max_rise { aggr_2
test
victim string
si_xtalk_bumps_min_fall { aggr_2
test
victim string
si_xtalk_bumps_min_rise { aggr_2
...

0.016968
0.015107
0.015793
0.016327

}
}
}
}

{
{
{
{

aggr_1
aggr_1
aggr_1
aggr_1

0.016846
0.016129
0.016816
0.016373

}
}
}
}

From the preceding report, we can see that for minimum analysis, the bump size of aggr_2 is always smaller than
aggr_1. Therefore, aggr_2 is filtered out, and aggr_1 is kept. In maximum analysis, the bump size of aggr_2 is larger

https://solvnet.synopsys.com/retrieve/1464951.html[8/26/2016 11:18:11 AM]

Logical Correlation Analysis on Victim and Aggressor Pairs With the Same Sense
when the victim is falling, and the bump size of aggr_1 is larger when victim is rising. As a result, aggr_2 is kept when
victim is falling, and aggr_1 is kept when victim is rising.
The second scenario is shown in Figure 1 where the victim is driving an aggressor with a buffer. When the
si_analysis_logical_correlation_mode variable is false, aggressor n2 is not filtered. When the
si_analysis_logical_correlation_mode variable is true, aggressor n2 is filtered as shown in the crosstalk report at
the beginning of this article. In crosstalk maximum analysis, the aggressor n2 is filtered out since victim n1 and
aggressor n2 are always the same sense. In crosstalk minimum analysis, aggressor n2 is filtered out because victim n1
and aggressor n2 alignment are not overlapping. So when logical correlation is on, PrimeTime SI considers both sense
and victim and aggressor alignment.

(1)Rate Article:

Average User Rating:

Save Article

Tag Article

Print

Send comment

Email

Your Recently Viewed Articles

Logical Correlation Analysis on Victim and Aggressor Pairs With the Same Sense
How Does the Exhaustive Path-Based Analysis Search Work?
Accurate Signoff Analysis with Path-Based Analysis in PrimeTime
Why Does report_crpr Differ From the CRPR Value in report_timing?
Why Is My CRPR Common Point Incorrect?
PrimeTime Advanced On-Chip Variation (OCV) Technology
How to Interpret PrimeTime's Derating Summary Report
Advanced On-Chip Variation (AOCV) in PrimeTime
PrimeTime Automated Physically-Aware ECO Flow With IC Compiler Application Note
PrimeTime ECO White Paper
Your Recent Searches

articles 2013

2016 Synopsys, Inc. All Rights Reserved.

https://solvnet.synopsys.com/retrieve/1464951.html[8/26/2016 11:18:11 AM]

CONTACT US

| TERMS OF USE | PRIVACY POLICY