- multiple people ............
- multiple prescriptions ........
Friday, December 17, 2010
ease of prescription management
Thursday, November 11, 2010
Tuesday, November 9, 2010
RC extraction
basic rc extraction corners
Hi,
Extraction can happen in different modes and different process corners.
From the fab, we get the RC data for different corners (for example slow/fast/nominal etc).
when we talk about modes, extraction can happen for ASIC's during the design process at
1. Global mode (post global routing).
2. Final mode (post detailed routing).
In Global mode, once RC's are extracted, the delay model that is used is elmore.
Elmore is a distributed resistance and lumped capacitance model. It accounts for only one pole and hence fast but can introduce some inaccuracy.
In final mode, the delay model is AWE (asymptotic waveform evaluation). AWE is more accurate because it is a > 2 pole model.
Delay models are important because the delay calculator provides this delay information back to STA (static timing analysis) engine.
Extraction is so important because it effects STA (static timing analysis), which dictates if you met your setup and hold times at every single flop in your chip.
STA actually finds the longest(critical) path in your circuit which determines your circuit frequency and also if you met all your hold times in your circuit.
STA uses extraction data at fast corner while calculating hld and slow data while calculating setup to be pessimistic as possible so that your chip doesn't fail after it comes back from the fab.
Extraction can also be classified as Lumped and coupled. In lumped you basically try to reduce a large RC circuit into an equivalen smaller RC circuit just taking the dominant poles into account (without any coupling). This is important because you want to reduce large RC circuits to smaller one's so that you can save on computer memory and run times.
In coupled mode, you basically try to extract the coupling capacitances which contribute to analyzing your crosstalk delay/noise effects on your chip.
If we are extracting for gate level, we have an equivalent RC circuit representation for each gate, which represents the gate Input/Output capacitances along with holding resistances. We plug these models into the RC network. But this is only for delay computation purpose (especially for fast slew propagation). But this can be inaccurate. Hence we dont represent gates using RC's. Rather we represent them using NLDM's and .libs (liberty format).
Reduction only happens mostly for passive components (wires) and not active elements. This reduction we term as model order reduction (MOR).
We usually plug in .lib (liberty) models for gates. Liberty models have tables which show gate delay as a function of (input transition time/output loads).
what we use at global and final mode for extraction is usually called a 2.5D extractor. This makes use of rules which are generated using a 3D extractor.
A 3D extractor is most accurate as it uses maxwells equations (to be precise green's function) to calculate RC's of various geometries which your fabrication facility will most likely manufacture.
BR
-Niks
Thursday, October 28, 2010
Fwd: 68-95-99.7 rule - Wikipedia, the free encyclopedia
Helen, Jeffrey and Stephane
From: Jeffrey CUI <huijun.cui@gmail.com>
Date: Thu, Oct 28, 2010 at 4:48 PM
Subject: 68-95-99.7 rule - Wikipedia, the free encyclopedia
To: Jeffrey CUI <huijun.cui@gmail.com>
Tuesday, October 26, 2010
Clock reconvergence pessimism removal (CRPR) 2
The removal portion or the credit is the difference between max delay and min delay of the common portion.
There is a command called : report_crpr which could give the exact crp value. Calculate crpr is quite expensive, so report_timing won't give you the exact cpr value. The value given by the report_timing is the exact value +/- the range of "timing_crpr_threshold_ps". That is the reason that you could see different crp value between report_crpr and report_timing.
To deal with the above issue, synopsys create another variable "timing_crpr_enable_adaptive_engine" to handle, when this variable is set to true, only the path with violation will be recalculate cpr, so the cpr will be accurate.
Clock reconvergence pessimism removal (CRPR)
In the adaptive CRPR mode, PrimeTime SI calculates CRPR only for the critical path set
(the violating portion of the design), thereby reducing the complexity of CRPR analysis. The
critical path set is the set of all paths with a slack of less than zero, for both setup and hold
timing constraints. The adaptive mode operates only when crosstalk analysis is enabled and
the maximum iteration count is set to 2 or more.
Typically, more nets are reselected for analysis in the second iteration using adaptive CRPR
because no CRPR is done in the first iteration. The resulting analysis is more accurate (less
pessimistic) because more nets are reselected for analysis.
report_timing and report_crpr
CRPR, or clock reconvergence pessimism removal, accounts for the difference in min/max delay of the portion of the clock network that is common to both the launch and the capture paths. For a path, it finds the common pin where the clock paths diverge, computes the difference between the min/max arrival times (the "CRP" value), and applies this as a credit to the path slack.
pt_shell> report_app_var *crpr*
Variable Value Type Default Constraints
----------------------- --------- ------- ---------- -----------------------
timing_crpr_enable_adaptive_engine false bool false
timing_crpr_minimize_grouping false bool false
timing_crpr_remove_clock_to_data_crp false bool false
timing_crpr_remove_muxed_clock_crp true bool true
timing_crpr_threshold_ps 1000 real 20 val >= 1
CRPR should be set to true to get things closer to the .........
Talk with Oscar ( library guy )
2. It doesn't make sense to use set_nose_margin, set_noise_immunity_curve, it is a coarse setting and some teams use it to add extra margin.
3. We do have lef file available ( I love lef file, I could extract lots of information from it ).
PTL, I got all the information I need.
Question: which corner we use when we analyze noise ???
Monday, October 25, 2010
set_noise_margin
From: Jeffrey H Cui [mailto:jeffrey@marvell.com]
Sent: Monday, October 25, 2010 6:25 PM
To: Jeffrey Cui
Subject:
2. Synopsys Commands Command Reference
set_noise_margin
Copyright 2009 Synopsys, Inc. All rights reserved.
NAME
set_noise_margin
Sets noise margin for a library pin, port, or pin.
SYNTAX
int set_noise_margin
[-above]
[-below]
[-low]
[-high]
margin_value
object_list
float margin_value
list object_list
ARGUMENTS
-above Specifies the noise margin for above ground or power rail noise
analysis region.
-below Specifies the noise margin for below ground or power rail noise
analysis region.
-low Specifies the noise margin for ground rail noise.
-high Specifies the noise margin for power rail noise.
margin_value
Specifies a margin value. The value is the input height in
units of voltage. 1.0.
object_list
Specifies a list of lib-pins or ports.
DESCRIPTION
Each library cell input can tolerate a certain amount of noise without
causing a failure at the cell output. This characteristic is called
noise immunity. This command specifies noise immunity at library pins
to determine whether noise failures occur as well as the amount of
noise slack.
Noise immunity in the library can be specified as noise immunity
curves, polynomials, or tables or in terms of noise margins.
This command specifies a noise margin for a library pin, design port,
or pin. It can be used in the absence of library-specified noise immu-
nity characteristics, or to override the library-specified characteris-
tics by replacing them with noise margins. Noise immunity curves that
have been annotated using the set_noise_immunity_curve command will
override noise margins set by this command.
Noise margins consider only the bump heights at the cell inputs. Using
height-only noise margins is simpler, faster, and more conservative
than the other methods.
For high, narrow noise bumps, using height-only noise margins is pes-
simistic because it treats some bumps as noise failures that would oth-
erwise pass with the immunity curve model. However, for wide noise
bumps, using noise
margins gives the same results as using noise immunity curves.
Noise immunity characteristics can vary for different noise bump types,
so there can be four different noise margins associated with each
input: below low, above low, below high, and above high. All values are
specified as positive numbers for all four types of noise bumps.
In the absence of command-specified or library-specified noise immunity
data, PrimeTime SI calculates the maximum allowable noise bump heights
based on DC noise margins of the driver and receiver, as defined in the
.lib technology library by the input/output logic-level parameters.
report_noise_calculation will show whether noise margin information was
taken from the library or annotated by this command.
EXAMPLES
This example specifies a margin of 4 for above the ground rail noise
for pin A of library cell IV in the lsi_10k library:
pt_shell> set_noise_margin -above -low 4 lsi_10k/IV/A
SEE ALSO
set_noise_immunity_curve (2), report_noise_calculation (2),
remove_noise_margin (2).
B-2008.12-SP2 Copyright (c) 2009 Synopsys, Inc. All rights reserved.
set_noise_margin -above -low 4 m9hpd_std_slow/hpd_sao21bx2/A2
set_noise_immunity_curve
From: Jeffrey H Cui [mailto:jeffrey@marvell.com]
Sent: Monday, October 25, 2010 6:25 PM
To: Jeffrey Cui
Subject:
2. Synopsys Commands Command Reference
set_noise_immunity_curve
Copyright 2009 Synopsys, Inc. All rights reserved.
NAME
set_noise_immunity_curve
Sets noise immunity curve for a library pin or port.
SYNTAX
int set_noise_immunity_curve
[-above]
[-below]
[-low]
[-high]
[-height height_value]
[-width width_value]
[-area area_value]
object_list
float height_value
float width_value
float area_value
list object_list
ARGUMENTS
-above Specifies an immunity curve for above ground or power rail noise
analysis region.
-below Specifies an immunity curve for below ground or power rail noise
analysis region.
-low Specifies an immunity curve for ground rail noise.
-high Specifies an immunity curve for power rail noise.
-height height_value
Specifies the height of the input voltage bump at the threshold
of logic failure. The height is in the voltage units of the
library.
-width width_value
Specifies the width of the input voltage bump at the threshold
of logic failure. The width is in the time units of the
library.
-area area_value
Specifies an area value for the curve. This parameter specifies
the size of the hyperbolic curve. 1.0.
object_list
Specifies a list of lib-pins or ports.
DESCRIPTION
Each cell input can tolerate a certain amount of noise without causing
a failure at the cell output. This characteristic is called noise immu-
nity. This command specifies noise immunity at library pins to deter-
mine whether noise failures occur as well as the amount of noise slack.
Noise immunity in the library can be specified as noise immunity
curves, polynomials, or tables or in terms of noise margins that con-
sider only the bump heights at the cell inputs.
This command specifies a noise immunity curve for a library pin or
design port. It can be used in the absence of library-specified noise
immunity characteristics, or to override the library-specified charac-
teristics by replacing them with a noise immunity curve. This command
will also override noise margins that have been annotated using the
set_noise_margin command,
The curve is hyperbolic with three coefficients to fully specify the
hyperbola: height and width of the input voltage bump at the threshold
of logic failure, and an area value to specify the size of the curve.
The three coefficients should be chosen to match the hyperbolic curve
to the data points obtained by laboratory characterization.
Noise immunity characteristics can vary for different noise bump types,
so there can be four different noise immunity curves associated with
each input: below low, above low, below high, and above high. All coef-
ficients are specified as positive numbers for all four types of noise
bumps.
report_noise_calculation will show whether noise immunity information
was taken from the library or annotated by this command.
EXAMPLES
This example specifies a noise height of 2, width of 3, area of 4 for
above the ground rail noise for pin A of library cell IV in the lsi_10k
library:
pt_shell> set_noise_immunity_curve -above -height 2 -width 3 \
-area 4 lsi_10k/IV/A
SEE ALSO
set_noise_margin (2), report_noise_calculation (2), remove_noise_immu-
nity_curve (2).
B-2008.12-SP2 Copyright (c) 2009 Synopsys, Inc. All rights reserved.
si_noise_composite_aggr_mode
si_noise_composite_aggr_mode
Specifies the composite aggressor mode for noise analysis.
TYPE
String
DEFAULT
disabled
DESCRIPTION
This variable specifies which composite aggressor mode is used in
PrimeTime SI noise analysis. Allowed values are disabled (the
default), which turns off the composite aggressor feature. normal,
causes PrimeTime SI to calculate noise by utilizing the non-statistical
composite aggressor feature. Selecting statistical causes PrimeTime SI
to calculate noise by using the statistical composite aggressor flow.
In disabled composite aggressor mode, PrimeTime SI uses its original
flow with composite aggressor completely off to analyze the noise.
In normal composite aggressor mode, PrimeTime SI aggregates the effect
of multiple small aggressors into a single composite aggressor, thereby
reducing the computational complexity and improving the performance.
statistical composite aggressor mode reduces the pessimism for noise
analysis by reducing the effect of composite aggressor.
For the current value of this variable, type printvar si_noise_compos-
ite_aggr_mode.
si_xtalk_double_switching_mode
si_xtalk_double_switching_mode
Controls the double switching detection during the PrimeTime-SI
timing analysis.
TYPE
String
DEFAULT
"disabled"
DESCRIPTION
Double switching detection mode can have one of these three values,
"disabled", "clock_network" or "full_design". When this mode is "dis-
abled", the default mode, this double switching detection is not
enabled. When this variable is enabled (set to "clock_network" or
"full_design"), during update_timing PrimeTime-SI checks that whether
crosstalk bump on the switching victim could cause the output to switch
twice (and cause a pulse) instead of of desiered single signal propaga-
tion.
To detect the potential double switching in the clock network, which
could cause the double clocking (where the clock could switch twice on
a the sensitive edge) or false clocking (where the switching bump on
the non-sensitive edge could actually latch the state), set this value
to "clock_network".
To detect the potential double switching in the data path as well as
clock path set this variable to "full_design". Double switching on a
data path is less severe then double switching on the clock network.
The double switching detection needs CCSN library information on the
victim load cell.
After the update_timing user could access these information in two ways
1) by command report_si_double_switching or 2) by the net attributes
si_has_double_switching & si_double_switching_slack. Refer the man
page of report_si_double_switching for the command details. The victim
net attribute si_has_double_switching is true when ever there is a
potential double switching on any of the load pins. The victim net
attribute si_double_switching_slack has the bump slack, reducing the
switching bump by that much amount could remove the double switching.
If the victim net doesn't cause double switching si_double_switch-
ing_slack will be "POSITIVE". If the victim net load pins doesn't have
CCS-Noise model information, the attribute will be reported as "INIFIN-
ITY".
The victim nets having the double switching is automatically reselected
to higher iteration so that they could be reanalyzed with more accurate
analysis.
The double switching happens when, the switching bump & transition time
are large and fed into driver which strong enough amplify this. To
avoid double switching either of them can be reduced.
Mock response to Devang
I am trying to understand several more options. I have some questions to ask Felicia/Amit and waiting for their response. I think I could have some recommendation middle this week.
NOISE
Thursday, October 21, 2010
0ps input transient time issue
2. the input cap zero issue: I guess it is because the port is floating
3. Big output transient time, there is no output load.
-Jeff
Wednesday, October 20, 2010
primetime_si
pt_shell> set_operating_conditions -analysis_type bc_wc \ -min BEST -max WORST pt_shell> report_timing -delay_type min_max Then, for crosstalk max analysis under WORST operating conditions, you would use:
pt_shell> set si_enable_analysis true pt_shell> set_operating_conditions -analysis_type \ on_chip_variation WORST pt_shell> report_timing -delay_type max Then, for crosstalk min analysis under BEST operating conditions, you would use:
pt_shell> set_operating_conditions -analysis_type \ on_chip_variation BEST pt_shell> report_timing -delay_type min
Monday, October 18, 2010
10_18_2010 PDS Error issue - Create_cell
So the solution is easy, just add two lines before I create cells to make sure these cells are not there when I am trying to create cell. Basically, def could play the role of create_cell too.
Friday, October 15, 2010
ICC bound vs plan
ICC scenario
-cts_corner min | max | min_max | none
When set to min (max), the min (max) corner of the scenario will
be considered by the optimize_clock_tree command. When set to
min_max, both of the min and max corners of the scenario will be
considered by the optimize_clock_tree command. Default value of
this option is none.
Wednesday, October 13, 2010
40nm spacing rules ..........
________________________________________________
Filler insertion. the 40nm minimum spacing rule is 2 placement grid. which is 0.28.
The problem is when the space is say, 4 x 0.14, you have 3x filler cell in your list, 3x is chosen first, then only 1x space is left. You have a gap left. This part is relative easy to resolve by controlling the size of standard rows, make the size always even number of 0.14. But it will become impossible after you place the standard cell, you can't control the gap between standard cells, it could be 2,3,4,5,6.
Because of the above reason, Synopsys creates this option -no_x1, which is to resolve the issue I mentioned above. It could resolve like 4x gap, it will try 3x filler, then use two 2x filler to fill the gap.
Friday, October 8, 2010
ESD and DRO cells
DRO used up to metal3, composed by standard cell. So I will treat it as standard cell, I won't add any blockage, any route_guide to it, I will let ICC to take care of everything. The only thing I need to take care is to make sure the cell is on the right row and make sure the hookup won't be messed up.
metal1 is run all the way across the block, so no need to take care the
To play safe which is not super necessary. create_preroute_via from metal6 to metal3
ESD used up to metal2. Two set of pins, VDD/VSS and VDD_ESD/VSS_ESD, since there is only one set of VDD/VSS here, so the connect is simple. Here is the deal, pease ESD as standard cell, make sure it is on the right row. After all the conn
metal1 rail is only on the boundary, so some trouble over there.
create_preroute_via from metal6 to metal2 for VDD_ESD and VSS_ESD
Found out no need to take care the connection from upper metal to lower metal, the tool is smart enough to take care of it by itself. Walla, ICC.
I still want to take care WPE for around these blocks.
Small problem, there is no odd width filler cell in daxing's script, this may create gap for power rail. The problem is not that small, need to tell him to fix it.