From: owner-ibis-users@eda.org (ibis-users)
To: ibis-users-digest@eda.org
Subject: ibis-users V1 #175
Reply-To: 
Sender: owner-ibis-users@eda.org
Errors-To: owner-ibis-users@eda.org
Precedence: bulk


ibis-users            Friday, June 10 2011            Volume 01 : Number 175




----------------------------------------------------------------------

Date: Thu, 2 Jun 2011 06:48:01 -0700
From: "Muranyi, Arpad" <Arpad_Muranyi@mentor.com>
Subject: RE: [IBIS-Users] Requesting for some help / information regarding the use of IBIS in SI simulation.

This is a multi-part message in MIME format.

- ------_=_NextPart_001_01CC212B.B13B969F
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Just a minor correction regarding:

=20

=20

=B7         Package model description in IBIS=20

o    Allows finer grain description of detailed models

=A7  This can be multiple lumped RLC models or multiple Tlines or any combi=
nation.

=20

=20

The [Package Model] / [Define Package Model] keywords in

IBIS allow a single lumped RLC matrix, or a multi-segment

T-line modeling approach.

=20

Arpad

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

=20

=20

From: owner-ibis-users@eda.org [mailto:owner-ibis-users@eda.org] On Behalf =
Of Doug Burns
Sent: Thursday, June 02, 2011 6:54 AM
To: bradb@sigrity.com; 'Scott McMorrow'
Cc: 'Ray Anderson'; 'ibis-users'
Subject: RE: [IBIS-Users] Requesting for some help / information regarding =
the use of IBIS in SI simulation.

=20

Brad,

=20

 I don't think we really disagree, but let us simplify the statements

 Given the model you have, what would you agree with:

=B7         Single RLC Model ala Simple IBIS

o    This does not model the resonances

o    This provides a large discontinuity to a high speed edge

=B7         Simple Tline model using RLC Characteristics

o    This does not model resonance

o    Better match to actual (ie less ringing than Lumped model)

=A7  Better does not mean accurate or correct, just closer to the desired t=
han a lumped model

=B7         Package model description in IBIS=20

o    Allows finer grain description of detailed models

=A7  This can be multiple lumped RLC models or multiple Tlines or any combi=
nation.

=A7  In the limit, a Tline segment can be modeled as multiple RLC pieces to=
 represent a distributed nature

o    Will model resonances you speak about at least at first order

=20

I assume that you will agree with all of the above.

=20

Therefore, what I am saying is that interconnect, by its very physical natu=
re represents a distributed RLC structure. Modeling any segment that is lon=
g compared to the edge rate of the signal is better modeled as a Tline than=
 a lumped model such that the distributed nature of the segment can be capt=
ured.=20

=20

For the example you cite, a simple RLC does not model the behavior and ther=
e is no rational to believe just making the model into a tline model would =
fix that issues. However, for a multi-segment model using lumped values for=
 each segment, my experience is that using tline models for all segments th=
at have length greater than the 1/3 to 1/2 the rise time (Almost always the=
 case with high speed signals), that a tline description is better than the=
 RLC description. This is true even in the multi-segmented implementation=
=20

=20

 Doug

=20

=20

- -----Original Message-----
From: Brad Brim [mailto:bradb@sigrity.com]=20
Sent: Thursday, June 02, 2011 5:55 AM
To: 'Doug Burns'; 'Scott McMorrow'
Cc: 'Ray Anderson'; 'ibis-users'
Subject: RE: [IBIS-Users] Requesting for some help / information regarding =
the use of IBIS in SI simulation.

=20

hi guys,

=20

Guess we'll agree to disagree.

=20

I have experience with any number of simple packages that violate your

"better" supposition for a uniformly distributed TL model. Why would this

occur, because I completely agree with you that it is counter intuitive.

=20

=46rom a package I recently characterized in some detail for system SI/PI

analysis; let's say the net behaves as static RLC to 2Ghz, then at about

4GHz there is some form of resonance in the signals or the planes. There's a

suckout in the response and then at higher frequencies it behaves more like

the TL you guys propose. If you assume the TL, then you completely miss this

behavior, and I do mean "completely". For this DDR bus you probably don't

care about the spectrum above 8GHz where it is again more TL like. But you

certainly DO care about the spectrum between 2Ghz and 6Ghz where it looks

nothing like a TL. If I choose properly a TEE or PI circuit to model the

behavior in this mid frequency range (since either works to 2Ghz) then you

get a much better transient system-level simulation than using your proposed

TL model. This is true even though the TEE/PI response at higher frequencies

is much worse than the uniform TL model. There is energy in the mid spectrum

but not in the high spectrum for this application. If I use a multi-stage

RLC model then select the element values to fit the broadband response then

I can get match at both mid and high frequencies to well 10Ghz and make all

of us happier (but maybe not to 40GHz).

=20

This is NOT a corner case. I see it in many of the package I characterize.

If I was trying to do a best fit to 40Ghz for this same package because my

signals had energy spread out that broadband, then it would probably be

better to use the uniform TL model. However, not all applications call for

it and the system is much better characterized with a model more correct

where the signals actually have energy.

=20

cheers,

 -Brad=20

=20

> -----Original Message-----

> From: Doug Burns [mailto:dburns@sisoft.com]=20

> Sent: Wednesday, June 01, 2011 6:55 AM

> To: 'Scott McMorrow'; bradb@sigrity.com

> Cc: 'Ray Anderson'; 'ibis-users'

> Subject: RE: [IBIS-Users] Requesting for some help /=20

> information regarding the use of IBIS in SI simulation.

>=20

> All,

>=20

>  I have to agree with Scott on this. For the type of packages=20

> as outlined by Scott, if one were to take the detailed model=20

> from a simulator and decompose it to a RLC format, the best=20

> correlation between the detailed model and the simplified=20

> model will occur when the simplified RLC is treated as a=20

> distributed structure such as a transmission line. Like=20

> Scott, we have proven this multiple time on a wide variety of=20

> package styles (leadframe through 24+ layer packages). There=20

> is no disagreement that a detailed model will be better,=20

> especially for high frequencies, but we must work within the=20

> limits of what IBIS can support. The mode detailed that=20

> package description is in IBIS, the better estimation we can=20

> make, but using lumped data for high speed signals is just=20

> causing an issue where one really will not exist. EDA tools=20

> need to make the best estimation of the available data to=20

> predict performance.

>=20

> Doug

>=20

> Douglas Burns

> Signal Integrity Software, Inc

> 6 Clock Tower Place

> Maynard, MA 01754

> 978-461-0449 x14

>=20

>=20=20

> -----Original Message-----

> From: owner-ibis-users@eda.org=20

> [mailto:owner-ibis-users@eda.org] On Behalf Of Scott McMorrow

> Sent: Wednesday, June 01, 2011 9:33 AM

> To: bradb@sigrity.com

> Cc: 'Ray Anderson'; 'ibis-users'

> Subject: Re: [IBIS-Users] Requesting for some help /=20

> information regarding the use of IBIS in SI simulation.

>=20

> Brad

>=20

> It is certainly your prerogative to disagree with me.  In the=20

> context of the original question, we are not talking about=20

> randomly distributed RLC, but rather package connections from=20

> board to silicon, which is the case in most IBIS models.=20=20

> Given that, we know the general topology.=20=20

> Whether the package uses lead frame, 2 layer FC packaging,=20

> 2/4 layer organic wire bond packaging, or multilayer buildup=20

> packaging, a single path from die to ball looks remarkably=20

> similar to cascaded transmission lines.  Even bond wires look=20

> like transmission lines.

>=20

> If I'm given a single RLC for an IBIS model of a=20

> conventionally packaged silicon device , then I can guarantee=20

> you that the simulation will be more faithful to measurements=20

> when the transmission line equivalent is used, rather than=20

> lumped elements.  Been there, done the measurements many,=20

> many times.  When multiple sections are specified in the IBIS=20

> .pkg format, then there is no ambiguity, a non-zero RLC=20

> section length defines a distributed element, and a zero=20

> length section defines a lumped element.  The simulator=20

> should model it as such.

>=20

> Having done correlation of package modeling to measurements=20

> from DC to 40 GHz on a 12-layer build-up with near zero=20

> error, I'm well aware of the issues involved with using the=20

> wrong modeling method, and poor material modeling.  I agree=20

> with you that a single RLC is an extremely poor approximation=20

> of any complex package interconnect, or any interconnect for=20

> that matter.  However, given that a user is presented with an=20

> RLC that was extracted with a quasi-static solver, as is the=20

> case with most IBIS models, I maintain that the result will=20

> be closer to reality when transformed into the distributed=20

> transmission line equivalent.  I've seen way too many cases=20

> where simulators used a lumped RLC directly, grossly over=20

> predicting  ringing at the die and in the channel, and=20

> confirmed by physical measurements.

>=20

> When we get into full-wave and hybrid full-wave AC modeling=20

> of packages there are a host of other issues that we can=20

> discuss, such as accurate dielectric modeling, accurate=20

> surface roughness modeling, as-designed vs. as-built package=20

> geometries, +/- 15% impedance variation due to manufacturing=20

> process  and electromagnetic non-locality.  But that is for=20

> another time.

>=20

>=20

> best regards,

>=20

> Scott

>=20

>=20

> Scott McMorrow

> Teraspeed Consulting Group LLC

> 121 North River Drive

> Narragansett, RI 02882

> (401) 284-1827 Business

> (401) 284-1840 Fax

>=20

> http://www.teraspeed.com

>=20

> TeraspeedR is the registered service mark of Teraspeed=20

> Consulting Group LLC

>=20

>=20

> On 6/1/2011 1:53 AM, Brad Brim wrote:

> > hello Scott,

> >

> > I don't agree with you. Such simulators (or model extractors which=20

> > write

> out

> > such "postprocessed" model data) are no more assured accurate than

> simply

> > applying or writing out the base RLC data.

> >

> > Most package extractors, especially ones you may refer to as=20

> > applicable "from the beginning", are based on static RLC=20

> simulation in=20

> > which a

> single L

> > and C are extracted at exactly DC from two distinct simulations;=20

> > magnetostatic and electrostatic respectively. One has NO CLUE how to

> form

> > the equivalent circuit given only the static lumped L and C=20

> computed=20

> > independently. Of course, as asked and discussed by Ray, if=20

> the user=20

> > has insight from the physical structure then a more broadband model=20

> > MIGHT be generated, but there is no guarantee!

> > One person assuming a PI circuit (with the C split equally=20

> in half -=20

> > or

> even

> > unequally - and the L in the middle) and another person=20

> assuming a TEE=20

> > circuit (with the L split and the shunt C in the middle) are no more

> correct

> > than the other. One has NO IDEA of the high frequency=20

> behavior of the=20

> > circuit (either just above the quasistatic limit where the likely

> spectral

> > content is relevant or higher where it is less likely relevant)=20

> > without

> some

> > form of AC high-frequency simulation or measurement. The=20

> behavior at=20

> > "infinite" frequency in meaningless and to argue that a uniformly=20

> > distributed multi-stage ladder network is valid has no more

> justification

> > than another person arguing it should me a lowpass network with all=20

> > the inductance on the die side because of wirebond inductance. This=20

> > argument

> has

> > blindly been accepted and argued for many years. It has been=20

> > unjustified

> and

> > wrong, as you would say, "from the beginning".

> >

> > Want a valid model at higher frequencies, then extract AC=20

> information

> from

> > which to generate it. One's guess or intuitive argument without AC=20

> > information to back it up is only a guess, as Andy stated. The=20

> > classical uniformly distributed ladder network is a=20

> deceptively simple=20

> > and

> intuitively

> > pleasing assumption that is easy to understand and unfortunately

> accepted by

> > way too many people in the industry. This supposed more=20

> accurate guess

> has

> > failed in too many cases and can even be worse than a=20

> simple totally=20

> > unbalanced low pass filter assumption over the frequency=20

> spectrum of=20

> > relevance.

> >

> > Many commercially available RLC extractors continue to make this

> assumption

> > today. Users are placed at significant risk because they falsely=20

> > believe

> the

> > model is in some sense "broadband" or "wideband". It is a=20

> guess with=20

> > no guarantee to be any better than any other assumed more=20

> distributed=20

> > equivalent circuit for which there is no theoretical or physical=20

> > justification.

> >

> > If one starts with AC data, assumes an equivalent circuit and *then*

> selects

> > element values in such to fit the data then there is reason to argue

> this is

> > a more valid model at higher frequencies. One cannot do=20

> this from only

> DC

> > terminal-based data. Not that it's difficult, it is impossible.

> >

> > best regards,

> >   -Brad

> >

> >

> >> -----Original Message-----

> >> From: owner-ibis-users@eda.org

> >> [mailto:owner-ibis-users@eda.org] On Behalf Of Scott McMorrow

> >> Sent: Tuesday, May 31, 2011 5:04 PM

> >> To: Ray Anderson

> >> Cc: ibis-users; Ray Anderson

> >> Subject: Re: [IBIS-Users] Requesting for some help / information=20

> >> regarding the use of IBIS in SI simulation.

> >>

> >> Since the beginning of IBIS, the most accurate simulators=20

> would turn=20

> >> the RLC package parasitics into a transmission line=20

> equivalent.  In=20

> >> lieu of any additional information it is the most=20

> reasonable thing to=20

> >> do, since packages can be approximated as transmission lines.

> >>

> >>

> >> Scott McMorrow

> >> Teraspeed Consulting Group LLC

> >> 121 North River Drive

> >> Narragansett, RI 02882

> >> (401) 284-1827 Business

> >> (401) 284-1840 Fax

> >>

> >> http://www.teraspeed.com

> >>

> >> TeraspeedR is the registered service mark of Teraspeed Consulting=20

> >> Group LLC

> >>

> >>

> >> On 5/31/2011 7:59 PM, Ray Anderson wrote:

> >>> If you are using extracted RLC data to manually set up=20

> the package=20

> >>> model you can certainly make intelligent decisions on the

> >> topology of

> >>> the model and the distribution of the RLC parasitics.

> >> However if you

> >>> are depending on a simulator to read the data from a IBIS

> >> .pkg format

> >>> file (or the [PIN] data) and set up a model for you then

> >> your results

> >>> may differ from simulator to simulator.

> >>>

> >>> -Ray

> >>> Xilinx Inc.

> >>>

> >>>

> >>> -----Original Message-----

> >>> From: owner-ibis-users@eda.org=20

> [mailto:owner-ibis-users@eda.org] On=20

> >>> Behalf Of Andrew Ingraham

> >>> Sent: Tuesday, May 31, 2011 4:48 PM

> >>> To: ibis-users

> >>> Subject: Re: [IBIS-Users] Requesting for some help / information=20

> >>> regarding the use of IBIS in SI simulation.

> >>>

> >>> Yes.

> >>>

> >>> I am usually tempted to start with an evenly distributed

> >> RLC model ...

> >>> unless I have reason to think that the distribution is

> >> otherwise.  For

> >>> example, wirebonds might have most of the inductance and

> >> resistance,

> >>> whereas the leadframe may have more capacitance, which

> >> might influence

> >>> one to imbalance those factors unequally between die end

> >> and pin end.

> >>> But without hard data to back it up, that is just guessing.

> >>>

> >>> Andy

> >>>

> >> --

> >> This message has been scanned for viruses and dangerous content by=20

> >> MailScanner, and is believed to be clean.

> >>

> >>=20

> --------------------------------------------------------------------

> >> |For help or to subscribe/unsubscribe, e-mail=20

> majordomo@eda-stds.org=20

> >> |with the appropriate command message(s) in the body:

> >> |

> >> |  help

> >> |  subscribe   ibis<optional e-mail address, if different>

> >> |  subscribe   ibis-users<optional e-mail address, if different>

> >> |  unsubscribe ibis<optional e-mail address, if different>=20=20

> >> | unsubscribe ibis-users<optional e-mail address, if different>

> >> |

> >> |or e-mail a request to ibis-request@eda-stds.org.

> >> |

> >> |IBIS reflector archives exist under:

> >> |

> >> |  http://www.eda-stds.org/pub/ibis/email_archive/ Recent=20

> >> | http://www.eda-stds.org/pub/ibis/users_archive/ Recent

> >> |  http://www.eda-stds.org/pub/ibis/email/         E-mail=20

> since 1993

> >>

>=20

> --

> This message has been scanned for viruses and dangerous=20

> content by MailScanner, and is believed to be clean.

>=20

> --------------------------------------------------------------------

> |For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org=20

> |with the appropriate command message(s) in the body:

> |

> |  help

> |  subscribe   ibis       <optional e-mail address, if different>

> |  subscribe   ibis-users <optional e-mail address, if different>

> |  unsubscribe ibis       <optional e-mail address, if different>

> |  unsubscribe ibis-users <optional e-mail address, if different>

> |

> |or e-mail a request to ibis-request@eda-stds.org.

> |

> |IBIS reflector archives exist under:

> |

> |  http://www.eda-stds.org/pub/ibis/email_archive/ Recent=20=20

> | http://www.eda-stds.org/pub/ibis/users_archive/ Recent

> |  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993

>=20

=20


- --=20
This message has been scanned for viruses and=20
dangerous content by MailScanner <http://www.mailscanner.info/> , and is=20
believed to be clean.=20


- --=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


- ------_=_NextPart_001_01CC212B.B13B969F
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Micr=
osoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Consolas","serif";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 77.95pt 1.0in 77.95pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:292954127;
	mso-list-type:hybrid;
	mso-list-template-ids:1258719960 1615499318 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:832260047;
	mso-list-type:hybrid;
	mso-list-template-ids:974274102 1615499318 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
- --></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:black'>Just a minor correct=
ion regarding:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Cou=
rier New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 lfo4'><![if=
 !supportLists]><span style=3D'font-family:Symbol'><span style=3D'mso-list:=
Ignore'>=B7<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>Package model =
description in IBIS <o:p></o:p></p><p class=3DMsoPlainText style=3D'margin-=
left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo4'><![if !supportLists]=
><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times New Roma=
n"'>&nbsp;&nbsp;&nbsp; </span></span><![endif]>Allows finer grain descripti=
on of detailed models<o:p></o:p></p><p class=3DMsoPlainText style=3D'margin=
- -left:1.5in;text-indent:-.25in;mso-list:l0 level3 lfo4'><![if !supportLists=
]><span style=3D'font-family:Wingdings'><span style=3D'mso-list:Ignore'>=A7=
<span style=3D'font:7.0pt "Times New Roman"'>&nbsp; </span></span></span><!=
[endif]>This can be multiple lumped RLC models or multiple Tlines or any co=
mbination.<o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0=
pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";c=
olor:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:10.0pt;font-family:"Courier New";color:black'>The [Package Model=
] / [Define Package Model] keywords in<o:p></o:p></span></p><p class=3DMsoN=
ormal><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black=
'>IBIS allow a single lumped RLC matrix, or a multi-segment<o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Cou=
rier New";color:black'>T-line modeling approach.<o:p></o:p></span></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";c=
olor:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:10.0pt;font-family:"Courier New";color:black'>Arpad<o:p></o:p></=
span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"=
Courier New";color:black'>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span st=
yle=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;<=
/o:p></span></p><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0=
pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-s=
ize:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> owner-ibis-users@e=
da.org [mailto:owner-ibis-users@eda.org] <b>On Behalf Of </b>Doug Burns<br>=
<b>Sent:</b> Thursday, June 02, 2011 6:54 AM<br><b>To:</b> bradb@sigrity.co=
m; 'Scott McMorrow'<br><b>Cc:</b> 'Ray Anderson'; 'ibis-users'<br><b>Subjec=
t:</b> RE: [IBIS-Users] Requesting for some help / information regarding th=
e use of IBIS in SI simulation.<o:p></o:p></span></p></div></div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Brad,<o:p></o:p><=
/p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>&nb=
sp;I don't think we really disagree, but let us simplify the statements<o:p=
></o:p></p><p class=3DMsoPlainText>&nbsp;Given the model you have, what wou=
ld you agree with:<o:p></o:p></p><p class=3DMsoPlainText style=3D'margin-le=
ft:.5in;text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><s=
pan style=3D'font-family:Symbol'><span style=3D'mso-list:Ignore'>=B7<span s=
tyle=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; </span></span></span><![endif]>Single RLC Model ala Simple IBIS=
<o:p></o:p></p><p class=3DMsoPlainText style=3D'margin-left:1.0in;text-inde=
nt:-.25in;mso-list:l1 level2 lfo2'><![if !supportLists]><span style=3D'mso-=
list:Ignore'>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbs=
p; </span></span><![endif]>This does not model the resonances<o:p></o:p></p=
><p class=3DMsoPlainText style=3D'margin-left:1.0in;text-indent:-.25in;mso-=
list:l1 level2 lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>o=
<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></sp=
an><![endif]>This provides a large discontinuity to a high speed edge<o:p><=
/o:p></p><p class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25=
in;mso-list:l1 level1 lfo2'><![if !supportLists]><span style=3D'font-family=
:Symbol'><span style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Time=
s New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></spa=
n></span><![endif]>Simple Tline model using RLC Characteristics<o:p></o:p><=
/p><p class=3DMsoPlainText style=3D'margin-left:1.0in;text-indent:-.25in;ms=
o-list:l1 level2 lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'=
>o<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></=
span><![endif]>This does not model resonance<o:p></o:p></p><p class=3DMsoPl=
ainText style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 lf=
o2'><![if !supportLists]><span style=3D'mso-list:Ignore'>o<span style=3D'fo=
nt:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span><![endif]>Bett=
er match to actual (ie less ringing than Lumped model)<o:p></o:p></p><p cla=
ss=3DMsoPlainText style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1=
 level3 lfo2'><![if !supportLists]><span style=3D'font-family:Wingdings'><s=
pan style=3D'mso-list:Ignore'>=A7<span style=3D'font:7.0pt "Times New Roman=
"'>&nbsp; </span></span></span><![endif]>Better does not mean accurate or c=
orrect, just closer to the desired than a lumped model<o:p></o:p></p><p cla=
ss=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 =
level1 lfo4'><![if !supportLists]><span style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New Roman"'>&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![end=
if]>Package model description in IBIS <o:p></o:p></p><p class=3DMsoPlainTex=
t style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo4'><!=
[if !supportLists]><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0=
pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span><![endif]>Allows fin=
er grain description of detailed models<o:p></o:p></p><p class=3DMsoPlainTe=
xt style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l0 level3 lfo4'><=
![if !supportLists]><span style=3D'font-family:Wingdings'><span style=3D'ms=
o-list:Ignore'>=A7<span style=3D'font:7.0pt "Times New Roman"'>&nbsp; </spa=
n></span></span><![endif]>This can be multiple lumped RLC models or multipl=
e Tlines or any combination.<o:p></o:p></p><p class=3DMsoPlainText style=3D=
'margin-left:1.5in;text-indent:-.25in;mso-list:l0 level3 lfo4'><![if !suppo=
rtLists]><span style=3D'font-family:Wingdings'><span style=3D'mso-list:Igno=
re'>=A7<span style=3D'font:7.0pt "Times New Roman"'>&nbsp; </span></span></=
span><![endif]>In the limit, a Tline segment can be modeled as multiple RLC=
 pieces to represent a distributed nature<o:p></o:p></p><p class=3DMsoPlain=
Text style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo4'=
><![if !supportLists]><span style=3D'mso-list:Ignore'>o<span style=3D'font:=
7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span><![endif]>Will mo=
del resonances you speak about at least at first order<o:p></o:p></p><p cla=
ss=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>I assume tha=
t you will agree with all of the above.<o:p></o:p></p><p class=3DMsoPlainTe=
xt><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Therefore, what I am saying=
 is that interconnect, by its very physical nature represents a distributed=
 RLC structure. Modeling any segment that is long compared to the edge rate=
 of the signal is better modeled as a Tline than a lumped model such that t=
he distributed nature of the segment can be captured. <o:p></o:p></p><p cla=
ss=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>For the exam=
ple you cite, a simple RLC does not model the behavior and there is no rati=
onal to believe just making the model into a tline model would fix that iss=
ues. However, for a multi-segment model using lumped values for each segmen=
t, my experience is that using tline models for all segments that have leng=
th greater than the 1/3 to 1/2 the rise time (Almost always the case with h=
igh speed signals), that a tline description is better than the RLC descrip=
tion. This is true even in the multi-segmented implementation <o:p></o:p></=
p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>&nbs=
p;Doug<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=
=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>-----Original =
Message-----<br>From: Brad Brim [mailto:bradb@sigrity.com] <br>Sent: Thursd=
ay, June 02, 2011 5:55 AM<br>To: 'Doug Burns'; 'Scott McMorrow'<br>Cc: 'Ray=
 Anderson'; 'ibis-users'<br>Subject: RE: [IBIS-Users] Requesting for some h=
elp / information regarding the use of IBIS in SI simulation.<o:p></o:p></p=
><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>hi gu=
ys,<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DM=
soPlainText>Guess we'll agree to disagree.<o:p></o:p></p><p class=3DMsoPlai=
nText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>I have experience with a=
ny number of simple packages that violate your<o:p></o:p></p><p class=3DMso=
PlainText>&quot;better&quot; supposition for a uniformly distributed TL mod=
el. Why would this<o:p></o:p></p><p class=3DMsoPlainText>occur, because I c=
ompletely agree with you that it is counter intuitive.<o:p></o:p></p><p cla=
ss=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>From a packa=
ge I recently characterized in some detail for system SI/PI<o:p></o:p></p><=
p class=3DMsoPlainText>analysis; let's say the net behaves as static RLC to=
 2Ghz, then at about<o:p></o:p></p><p class=3DMsoPlainText>4GHz there is so=
me form of resonance in the signals or the planes. There's a<o:p></o:p></p>=
<p class=3DMsoPlainText>suckout in the response and then at higher frequenc=
ies it behaves more like<o:p></o:p></p><p class=3DMsoPlainText>the TL you g=
uys propose. If you assume the TL, then you completely miss this<o:p></o:p>=
</p><p class=3DMsoPlainText>behavior, and I do mean &quot;completely&quot;.=
 For this DDR bus you probably don't<o:p></o:p></p><p class=3DMsoPlainText>=
care about the spectrum above 8GHz where it is again more TL like. But you<=
o:p></o:p></p><p class=3DMsoPlainText>certainly DO care about the spectrum =
between 2Ghz and 6Ghz where it looks<o:p></o:p></p><p class=3DMsoPlainText>=
nothing like a TL. If I choose properly a TEE or PI circuit to model the<o:=
p></o:p></p><p class=3DMsoPlainText>behavior in this mid frequency range (s=
ince either works to 2Ghz) then you<o:p></o:p></p><p class=3DMsoPlainText>g=
et a much better transient system-level simulation than using your proposed=
<o:p></o:p></p><p class=3DMsoPlainText>TL model. This is true even though t=
he TEE/PI response at higher frequencies<o:p></o:p></p><p class=3DMsoPlainT=
ext>is much worse than the uniform TL model. There is energy in the mid spe=
ctrum<o:p></o:p></p><p class=3DMsoPlainText>but not in the high spectrum fo=
r this application. If I use a multi-stage<o:p></o:p></p><p class=3DMsoPlai=
nText>RLC model then select the element values to fit the broadband respons=
e then<o:p></o:p></p><p class=3DMsoPlainText>I can get match at both mid an=
d high frequencies to well 10Ghz and make all<o:p></o:p></p><p class=3DMsoP=
lainText>of us happier (but maybe not to 40GHz).<o:p></o:p></p><p class=3DM=
soPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>This is NOT a corn=
er case. I see it in many of the package I characterize.<o:p></o:p></p><p c=
lass=3DMsoPlainText>If I was trying to do a best fit to 40Ghz for this same=
 package because my<o:p></o:p></p><p class=3DMsoPlainText>signals had energ=
y spread out that broadband, then it would probably be<o:p></o:p></p><p cla=
ss=3DMsoPlainText>better to use the uniform TL model. However, not all appl=
ications call for<o:p></o:p></p><p class=3DMsoPlainText>it and the system i=
s much better characterized with a model more correct<o:p></o:p></p><p clas=
s=3DMsoPlainText>where the signals actually have energy.<o:p></o:p></p><p c=
lass=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>cheers,<o:=
p></o:p></p><p class=3DMsoPlainText>&nbsp;-Brad <o:p></o:p></p><p class=3DM=
soPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>&gt; -----Original=
 Message-----<o:p></o:p></p><p class=3DMsoPlainText>&gt; From: Doug Burns [=
mailto:dburns@sisoft.com] <o:p></o:p></p><p class=3DMsoPlainText>&gt; Sent:=
 Wednesday, June 01, 2011 6:55 AM<o:p></o:p></p><p class=3DMsoPlainText>&gt=
; To: 'Scott McMorrow'; bradb@sigrity.com<o:p></o:p></p><p class=3DMsoPlain=
Text>&gt; Cc: 'Ray Anderson'; 'ibis-users'<o:p></o:p></p><p class=3DMsoPlai=
nText>&gt; Subject: RE: [IBIS-Users] Requesting for some help / <o:p></o:p>=
</p><p class=3DMsoPlainText>&gt; information regarding the use of IBIS in S=
I simulation.<o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; All,<o:p></o:p></p><p class=3DMsoPlainText>&gt; <=
o:p></o:p></p><p class=3DMsoPlainText>&gt;&nbsp; I have to agree with Scott=
 on this. For the type of packages <o:p></o:p></p><p class=3DMsoPlainText>&=
gt; as outlined by Scott, if one were to take the detailed model <o:p></o:p=
></p><p class=3DMsoPlainText>&gt; from a simulator and decompose it to a RL=
C format, the best <o:p></o:p></p><p class=3DMsoPlainText>&gt; correlation =
between the detailed model and the simplified <o:p></o:p></p><p class=3DMso=
PlainText>&gt; model will occur when the simplified RLC is treated as a <o:=
p></o:p></p><p class=3DMsoPlainText>&gt; distributed structure such as a tr=
ansmission line. Like <o:p></o:p></p><p class=3DMsoPlainText>&gt; Scott, we=
 have proven this multiple time on a wide variety of <o:p></o:p></p><p clas=
s=3DMsoPlainText>&gt; package styles (leadframe through 24+ layer packages)=
. There <o:p></o:p></p><p class=3DMsoPlainText>&gt; is no disagreement that=
 a detailed model will be better, <o:p></o:p></p><p class=3DMsoPlainText>&g=
t; especially for high frequencies, but we must work within the <o:p></o:p>=
</p><p class=3DMsoPlainText>&gt; limits of what IBIS can support. The mode =
detailed that <o:p></o:p></p><p class=3DMsoPlainText>&gt; package descripti=
on is in IBIS, the better estimation we can <o:p></o:p></p><p class=3DMsoPl=
ainText>&gt; make, but using lumped data for high speed signals is just <o:=
p></o:p></p><p class=3DMsoPlainText>&gt; causing an issue where one really =
will not exist. EDA tools <o:p></o:p></p><p class=3DMsoPlainText>&gt; need =
to make the best estimation of the available data to <o:p></o:p></p><p clas=
s=3DMsoPlainText>&gt; predict performance.<o:p></o:p></p><p class=3DMsoPlai=
nText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; Doug<o:p></o:p></p><=
p class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; Dou=
glas Burns<o:p></o:p></p><p class=3DMsoPlainText>&gt; Signal Integrity Soft=
ware, Inc<o:p></o:p></p><p class=3DMsoPlainText>&gt; 6 Clock Tower Place<o:=
p></o:p></p><p class=3DMsoPlainText>&gt; Maynard, MA 01754<o:p></o:p></p><p=
 class=3DMsoPlainText>&gt; 978-461-0449 x14<o:p></o:p></p><p class=3DMsoPla=
inText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt;&nbsp; <o:p></o:p></=
p><p class=3DMsoPlainText>&gt; -----Original Message-----<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; From: owner-ibis-users@eda.org <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; [mailto:owner-ibis-users@eda.org] On Behalf Of Sc=
ott McMorrow<o:p></o:p></p><p class=3DMsoPlainText>&gt; Sent: Wednesday, Ju=
ne 01, 2011 9:33 AM<o:p></o:p></p><p class=3DMsoPlainText>&gt; To: bradb@si=
grity.com<o:p></o:p></p><p class=3DMsoPlainText>&gt; Cc: 'Ray Anderson'; 'i=
bis-users'<o:p></o:p></p><p class=3DMsoPlainText>&gt; Subject: Re: [IBIS-Us=
ers] Requesting for some help / <o:p></o:p></p><p class=3DMsoPlainText>&gt;=
 information regarding the use of IBIS in SI simulation.<o:p></o:p></p><p c=
lass=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; Brad<o=
:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlai=
nText>&gt; It is certainly your prerogative to disagree with me.&nbsp; In t=
he <o:p></o:p></p><p class=3DMsoPlainText>&gt; context of the original ques=
tion, we are not talking about <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
randomly distributed RLC, but rather package connections from <o:p></o:p></=
p><p class=3DMsoPlainText>&gt; board to silicon, which is the case in most =
IBIS models.&nbsp; <o:p></o:p></p><p class=3DMsoPlainText>&gt; Given that, =
we know the general topology.&nbsp; <o:p></o:p></p><p class=3DMsoPlainText>=
&gt; Whether the package uses lead frame, 2 layer FC packaging, <o:p></o:p>=
</p><p class=3DMsoPlainText>&gt; 2/4 layer organic wire bond packaging, or =
multilayer buildup <o:p></o:p></p><p class=3DMsoPlainText>&gt; packaging, a=
 single path from die to ball looks remarkably <o:p></o:p></p><p class=3DMs=
oPlainText>&gt; similar to cascaded transmission lines.&nbsp; Even bond wir=
es look <o:p></o:p></p><p class=3DMsoPlainText>&gt; like transmission lines=
.<o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoP=
lainText>&gt; If I'm given a single RLC for an IBIS model of a <o:p></o:p><=
/p><p class=3DMsoPlainText>&gt; conventionally packaged silicon device , th=
en I can guarantee <o:p></o:p></p><p class=3DMsoPlainText>&gt; you that the=
 simulation will be more faithful to measurements <o:p></o:p></p><p class=
=3DMsoPlainText>&gt; when the transmission line equivalent is used, rather =
than <o:p></o:p></p><p class=3DMsoPlainText>&gt; lumped elements.&nbsp; Bee=
n there, done the measurements many, <o:p></o:p></p><p class=3DMsoPlainText=
>&gt; many times.&nbsp; When multiple sections are specified in the IBIS <o=
:p></o:p></p><p class=3DMsoPlainText>&gt; .pkg format, then there is no amb=
iguity, a non-zero RLC <o:p></o:p></p><p class=3DMsoPlainText>&gt; section =
length defines a distributed element, and a zero <o:p></o:p></p><p class=3D=
MsoPlainText>&gt; length section defines a lumped element.&nbsp; The simula=
tor <o:p></o:p></p><p class=3DMsoPlainText>&gt; should model it as such.<o:=
p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlain=
Text>&gt; Having done correlation of package modeling to measurements <o:p>=
</o:p></p><p class=3DMsoPlainText>&gt; from DC to 40 GHz on a 12-layer buil=
d-up with near zero <o:p></o:p></p><p class=3DMsoPlainText>&gt; error, I'm =
well aware of the issues involved with using the <o:p></o:p></p><p class=3D=
MsoPlainText>&gt; wrong modeling method, and poor material modeling.&nbsp; =
I agree <o:p></o:p></p><p class=3DMsoPlainText>&gt; with you that a single =
RLC is an extremely poor approximation <o:p></o:p></p><p class=3DMsoPlainTe=
xt>&gt; of any complex package interconnect, or any interconnect for <o:p><=
/o:p></p><p class=3DMsoPlainText>&gt; that matter.&nbsp; However, given tha=
t a user is presented with an <o:p></o:p></p><p class=3DMsoPlainText>&gt; R=
LC that was extracted with a quasi-static solver, as is the <o:p></o:p></p>=
<p class=3DMsoPlainText>&gt; case with most IBIS models, I maintain that th=
e result will <o:p></o:p></p><p class=3DMsoPlainText>&gt; be closer to real=
ity when transformed into the distributed <o:p></o:p></p><p class=3DMsoPlai=
nText>&gt; transmission line equivalent.&nbsp; I've seen way too many cases=
 <o:p></o:p></p><p class=3DMsoPlainText>&gt; where simulators used a lumped=
 RLC directly, grossly over <o:p></o:p></p><p class=3DMsoPlainText>&gt; pre=
dicting&nbsp; ringing at the die and in the channel, and <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; confirmed by physical measurements.<o:p></o:p></p=
><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; W=
hen we get into full-wave and hybrid full-wave AC modeling <o:p></o:p></p><=
p class=3DMsoPlainText>&gt; of packages there are a host of other issues th=
at we can <o:p></o:p></p><p class=3DMsoPlainText>&gt; discuss, such as accu=
rate dielectric modeling, accurate <o:p></o:p></p><p class=3DMsoPlainText>&=
gt; surface roughness modeling, as-designed vs. as-built package <o:p></o:p=
></p><p class=3DMsoPlainText>&gt; geometries, +/- 15% impedance variation d=
ue to manufacturing <o:p></o:p></p><p class=3DMsoPlainText>&gt; process&nbs=
p; and electromagnetic non-locality.&nbsp; But that is for <o:p></o:p></p><=
p class=3DMsoPlainText>&gt; another time.<o:p></o:p></p><p class=3DMsoPlain=
Text>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p cla=
ss=3DMsoPlainText>&gt; best regards,<o:p></o:p></p><p class=3DMsoPlainText>=
&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; Scott<o:p></o:p></p><p cla=
ss=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o=
:p></p><p class=3DMsoPlainText>&gt; Scott McMorrow<o:p></o:p></p><p class=
=3DMsoPlainText>&gt; Teraspeed Consulting Group LLC<o:p></o:p></p><p class=
=3DMsoPlainText>&gt; 121 North River Drive<o:p></o:p></p><p class=3DMsoPlai=
nText>&gt; Narragansett, RI 02882<o:p></o:p></p><p class=3DMsoPlainText>&gt=
; (401) 284-1827 Business<o:p></o:p></p><p class=3DMsoPlainText>&gt; (401) =
284-1840 Fax<o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p c=
lass=3DMsoPlainText>&gt; http://www.teraspeed.com<o:p></o:p></p><p class=3D=
MsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; TeraspeedR is=
 the registered service mark of Teraspeed <o:p></o:p></p><p class=3DMsoPlai=
nText>&gt; Consulting Group LLC<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPl=
ainText>&gt; On 6/1/2011 1:53 AM, Brad Brim wrote:<o:p></o:p></p><p class=
=3DMsoPlainText>&gt; &gt; hello Scott,<o:p></o:p></p><p class=3DMsoPlainTex=
t>&gt; &gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; I don't agree w=
ith you. Such simulators (or model extractors which <o:p></o:p></p><p class=
=3DMsoPlainText>&gt; &gt; write<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
out<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; such &quot;postprocesse=
d&quot; model data) are no more assured accurate than<o:p></o:p></p><p clas=
s=3DMsoPlainText>&gt; simply<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt=
; applying or writing out the base RLC data.<o:p></o:p></p><p class=3DMsoPl=
ainText>&gt; &gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; Most pack=
age extractors, especially ones you may refer to as <o:p></o:p></p><p class=
=3DMsoPlainText>&gt; &gt; applicable &quot;from the beginning&quot;, are ba=
sed on static RLC <o:p></o:p></p><p class=3DMsoPlainText>&gt; simulation in=
 <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; which a<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; single L<o:p></o:p></p><p class=3DMsoPlainText>&g=
t; &gt; and C are extracted at exactly DC from two distinct simulations; <o=
:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; magnetostatic and electrosta=
tic respectively. One has NO CLUE how to<o:p></o:p></p><p class=3DMsoPlainT=
ext>&gt; form<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; the equivalen=
t circuit given only the static lumped L and C <o:p></o:p></p><p class=3DMs=
oPlainText>&gt; computed <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; i=
ndependently. Of course, as asked and discussed by Ray, if <o:p></o:p></p><=
p class=3DMsoPlainText>&gt; the user <o:p></o:p></p><p class=3DMsoPlainText=
>&gt; &gt; has insight from the physical structure then a more broadband mo=
del <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; MIGHT be generated, bu=
t there is no guarantee!<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; On=
e person assuming a PI circuit (with the C split equally <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; in half - <o:p></o:p></p><p class=3DMsoPlainText>=
&gt; &gt; or<o:p></o:p></p><p class=3DMsoPlainText>&gt; even<o:p></o:p></p>=
<p class=3DMsoPlainText>&gt; &gt; unequally - and the L in the middle) and =
another person <o:p></o:p></p><p class=3DMsoPlainText>&gt; assuming a TEE <=
o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; circuit (with the L split a=
nd the shunt C in the middle) are no more<o:p></o:p></p><p class=3DMsoPlain=
Text>&gt; correct<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; than the =
other. One has NO IDEA of the high frequency <o:p></o:p></p><p class=3DMsoP=
lainText>&gt; behavior of the <o:p></o:p></p><p class=3DMsoPlainText>&gt; &=
gt; circuit (either just above the quasistatic limit where the likely<o:p><=
/o:p></p><p class=3DMsoPlainText>&gt; spectral<o:p></o:p></p><p class=3DMso=
PlainText>&gt; &gt; content is relevant or higher where it is less likely r=
elevant) <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; without<o:p></o:p=
></p><p class=3DMsoPlainText>&gt; some<o:p></o:p></p><p class=3DMsoPlainTex=
t>&gt; &gt; form of AC high-frequency simulation or measurement. The <o:p><=
/o:p></p><p class=3DMsoPlainText>&gt; behavior at <o:p></o:p></p><p class=
=3DMsoPlainText>&gt; &gt; &quot;infinite&quot; frequency in meaningless and=
 to argue that a uniformly <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;=
 distributed multi-stage ladder network is valid has no more<o:p></o:p></p>=
<p class=3DMsoPlainText>&gt; justification<o:p></o:p></p><p class=3DMsoPlai=
nText>&gt; &gt; than another person arguing it should me a lowpass network =
with all <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; the inductance on=
 the die side because of wirebond inductance. This <o:p></o:p></p><p class=
=3DMsoPlainText>&gt; &gt; argument<o:p></o:p></p><p class=3DMsoPlainText>&g=
t; has<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; blindly been accepte=
d and argued for many years. It has been <o:p></o:p></p><p class=3DMsoPlain=
Text>&gt; &gt; unjustified<o:p></o:p></p><p class=3DMsoPlainText>&gt; and<o=
:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; wrong, as you would say, &qu=
ot;from the beginning&quot;.<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt=
;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; Want a valid model at hig=
her frequencies, then extract AC <o:p></o:p></p><p class=3DMsoPlainText>&gt=
; information<o:p></o:p></p><p class=3DMsoPlainText>&gt; from<o:p></o:p></p=
><p class=3DMsoPlainText>&gt; &gt; which to generate it. One's guess or int=
uitive argument without AC <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;=
 information to back it up is only a guess, as Andy stated. The <o:p></o:p>=
</p><p class=3DMsoPlainText>&gt; &gt; classical uniformly distributed ladde=
r network is a <o:p></o:p></p><p class=3DMsoPlainText>&gt; deceptively simp=
le <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; and<o:p></o:p></p><p cl=
ass=3DMsoPlainText>&gt; intuitively<o:p></o:p></p><p class=3DMsoPlainText>&=
gt; &gt; pleasing assumption that is easy to understand and unfortunately<o=
:p></o:p></p><p class=3DMsoPlainText>&gt; accepted by<o:p></o:p></p><p clas=
s=3DMsoPlainText>&gt; &gt; way too many people in the industry. This suppos=
ed more <o:p></o:p></p><p class=3DMsoPlainText>&gt; accurate guess<o:p></o:=
p></p><p class=3DMsoPlainText>&gt; has<o:p></o:p></p><p class=3DMsoPlainTex=
t>&gt; &gt; failed in too many cases and can even be worse than a <o:p></o:=
p></p><p class=3DMsoPlainText>&gt; simple totally <o:p></o:p></p><p class=
=3DMsoPlainText>&gt; &gt; unbalanced low pass filter assumption over the fr=
equency <o:p></o:p></p><p class=3DMsoPlainText>&gt; spectrum of <o:p></o:p>=
</p><p class=3DMsoPlainText>&gt; &gt; relevance.<o:p></o:p></p><p class=3DM=
soPlainText>&gt; &gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; Many =
commercially available RLC extractors continue to make this<o:p></o:p></p><=
p class=3DMsoPlainText>&gt; assumption<o:p></o:p></p><p class=3DMsoPlainTex=
t>&gt; &gt; today. Users are placed at significant risk because they falsel=
y <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; believe<o:p></o:p></p><p=
 class=3DMsoPlainText>&gt; the<o:p></o:p></p><p class=3DMsoPlainText>&gt; &=
gt; model is in some sense &quot;broadband&quot; or &quot;wideband&quot;. I=
t is a <o:p></o:p></p><p class=3DMsoPlainText>&gt; guess with <o:p></o:p></=
p><p class=3DMsoPlainText>&gt; &gt; no guarantee to be any better than any =
other assumed more <o:p></o:p></p><p class=3DMsoPlainText>&gt; distributed =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; equivalent circuit for whi=
ch there is no theoretical or physical <o:p></o:p></p><p class=3DMsoPlainTe=
xt>&gt; &gt; justification.<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;=
<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; If one starts with AC data=
, assumes an equivalent circuit and *then*<o:p></o:p></p><p class=3DMsoPlai=
nText>&gt; selects<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; element =
values in such to fit the data then there is reason to argue<o:p></o:p></p>=
<p class=3DMsoPlainText>&gt; this is<o:p></o:p></p><p class=3DMsoPlainText>=
&gt; &gt; a more valid model at higher frequencies. One cannot do <o:p></o:=
p></p><p class=3DMsoPlainText>&gt; this from only<o:p></o:p></p><p class=3D=
MsoPlainText>&gt; DC<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; termin=
al-based data. Not that it's difficult, it is impossible.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &=
gt; best regards,<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&nbsp;&nbs=
p; -Brad<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;<o:p></o:p></p><p c=
lass=3DMsoPlainText>&gt; &gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &g=
t;&gt; -----Original Message-----<o:p></o:p></p><p class=3DMsoPlainText>&gt=
; &gt;&gt; From: owner-ibis-users@eda.org<o:p></o:p></p><p class=3DMsoPlain=
Text>&gt; &gt;&gt; [mailto:owner-ibis-users@eda.org] On Behalf Of Scott McM=
orrow<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; Sent: Tuesday, Ma=
y 31, 2011 5:04 PM<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; To: =
Ray Anderson<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; Cc: ibis-u=
sers; Ray Anderson<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; Subj=
ect: Re: [IBIS-Users] Requesting for some help / information <o:p></o:p></p=
><p class=3DMsoPlainText>&gt; &gt;&gt; regarding the use of IBIS in SI simu=
lation.<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><=
p class=3DMsoPlainText>&gt; &gt;&gt; Since the beginning of IBIS, the most =
accurate simulators <o:p></o:p></p><p class=3DMsoPlainText>&gt; would turn =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; the RLC package parasi=
tics into a transmission line <o:p></o:p></p><p class=3DMsoPlainText>&gt; e=
quivalent.&nbsp; In <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; li=
eu of any additional information it is the most <o:p></o:p></p><p class=3DM=
soPlainText>&gt; reasonable thing to <o:p></o:p></p><p class=3DMsoPlainText=
>&gt; &gt;&gt; do, since packages can be approximated as transmission lines=
.<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p clas=
s=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &=
gt;&gt; Scott McMorrow<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; =
Teraspeed Consulting Group LLC<o:p></o:p></p><p class=3DMsoPlainText>&gt; &=
gt;&gt; 121 North River Drive<o:p></o:p></p><p class=3DMsoPlainText>&gt; &g=
t;&gt; Narragansett, RI 02882<o:p></o:p></p><p class=3DMsoPlainText>&gt; &g=
t;&gt; (401) 284-1827 Business<o:p></o:p></p><p class=3DMsoPlainText>&gt; &=
gt;&gt; (401) 284-1840 Fax<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&=
gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; http://www.teraspee=
d.com<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt; TeraspeedR is the registered service mar=
k of Teraspeed Consulting <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&=
gt; Group LLC<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p=
></p><p class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p class=3DMsoPlai=
nText>&gt; &gt;&gt; On 5/31/2011 7:59 PM, Ray Anderson wrote:<o:p></o:p></p=
><p class=3DMsoPlainText>&gt; &gt;&gt;&gt; If you are using extracted RLC d=
ata to manually set up <o:p></o:p></p><p class=3DMsoPlainText>&gt; the pack=
age <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;&gt; model you can =
certainly make intelligent decisions on the<o:p></o:p></p><p class=3DMsoPla=
inText>&gt; &gt;&gt; topology of<o:p></o:p></p><p class=3DMsoPlainText>&gt;=
 &gt;&gt;&gt; the model and the distribution of the RLC parasitics.<o:p></o=
:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; However if you<o:p></o:p></p><=
p class=3DMsoPlainText>&gt; &gt;&gt;&gt; are depending on a simulator to re=
ad the data from a IBIS<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;=
 .pkg format<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;&gt; file (=
or the [PIN] data) and set up a model for you then<o:p></o:p></p><p class=
=3DMsoPlainText>&gt; &gt;&gt; your results<o:p></o:p></p><p class=3DMsoPlai=
nText>&gt; &gt;&gt;&gt; may differ from simulator to simulator.<o:p></o:p><=
/p><p class=3DMsoPlainText>&gt; &gt;&gt;&gt;<o:p></o:p></p><p class=3DMsoPl=
ainText>&gt; &gt;&gt;&gt; -Ray<o:p></o:p></p><p class=3DMsoPlainText>&gt; &=
gt;&gt;&gt; Xilinx Inc.<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;=
&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;&gt;<o:p></o:p></p>=
<p class=3DMsoPlainText>&gt; &gt;&gt;&gt; -----Original Message-----<o:p></=
o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;&gt; From: owner-ibis-users@ed=
a.org <o:p></o:p></p><p class=3DMsoPlainText>&gt; [mailto:owner-ibis-users@=
eda.org] On <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;&gt; Behalf=
 Of Andrew Ingraham<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;&gt;=
 Sent: Tuesday, May 31, 2011 4:48 PM<o:p></o:p></p><p class=3DMsoPlainText>=
&gt; &gt;&gt;&gt; To: ibis-users<o:p></o:p></p><p class=3DMsoPlainText>&gt;=
 &gt;&gt;&gt; Subject: Re: [IBIS-Users] Requesting for some help / informat=
ion <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;&gt; regarding the =
use of IBIS in SI simulation.<o:p></o:p></p><p class=3DMsoPlainText>&gt; &g=
t;&gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;&gt; Yes.<o:p=
></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;&gt;<o:p></o:p></p><p class=
=3DMsoPlainText>&gt; &gt;&gt;&gt; I am usually tempted to start with an eve=
nly distributed<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; RLC mod=
el ...<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;&gt; unless I hav=
e reason to think that the distribution is<o:p></o:p></p><p class=3DMsoPlai=
nText>&gt; &gt;&gt; otherwise.&nbsp; For<o:p></o:p></p><p class=3DMsoPlainT=
ext>&gt; &gt;&gt;&gt; example, wirebonds might have most of the inductance =
and<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; resistance,<o:p></o=
:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;&gt; whereas the leadframe may =
have more capacitance, which<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt=
;&gt; might influence<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;&g=
t; one to imbalance those factors unequally between die end<o:p></o:p></p><=
p class=3DMsoPlainText>&gt; &gt;&gt; and pin end.<o:p></o:p></p><p class=3D=
MsoPlainText>&gt; &gt;&gt;&gt; But without hard data to back it up, that is=
 just guessing.<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;&gt;<o:p=
></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;&gt; Andy<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt;&gt;<o:p></o:p></p><p class=3DMsoPlainTex=
t>&gt; &gt;&gt; --<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; This=
 message has been scanned for viruses and dangerous content by <o:p></o:p><=
/p><p class=3DMsoPlainText>&gt; &gt;&gt; MailScanner, and is believed to be=
 clean.<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><=
p class=3DMsoPlainText>&gt; &gt;&gt; <o:p></o:p></p><p class=3DMsoPlainText=
>&gt; --------------------------------------------------------------------<=
o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; |For help or to subscri=
be/unsubscribe, e-mail <o:p></o:p></p><p class=3DMsoPlainText>&gt; majordom=
o@eda-stds.org <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; |with t=
he appropriate command message(s) in the body:<o:p></o:p></p><p class=3DMso=
PlainText>&gt; &gt;&gt; |<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&g=
t; |&nbsp; help<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; |&nbsp;=
 subscribe&nbsp;&nbsp; ibis&lt;optional e-mail address, if different&gt;<o:=
p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; |&nbsp; subscribe&nbsp;&n=
bsp; ibis-users&lt;optional e-mail address, if different&gt;<o:p></o:p></p>=
<p class=3DMsoPlainText>&gt; &gt;&gt; |&nbsp; unsubscribe ibis&lt;optional =
e-mail address, if different&gt;&nbsp; <o:p></o:p></p><p class=3DMsoPlainTe=
xt>&gt; &gt;&gt; | unsubscribe ibis-users&lt;optional e-mail address, if di=
fferent&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; |<o:p></o:p=
></p><p class=3DMsoPlainText>&gt; &gt;&gt; |or e-mail a request to ibis-req=
uest@eda-stds.org.<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; |<o:=
p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; |IBIS reflector archives =
exist under:<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; |<o:p></o:=
p></p><p class=3DMsoPlainText>&gt; &gt;&gt; |&nbsp; http://www.eda-stds.org=
/pub/ibis/email_archive/ Recent <o:p></o:p></p><p class=3DMsoPlainText>&gt;=
 &gt;&gt; | http://www.eda-stds.org/pub/ibis/users_archive/ Recent<o:p></o:=
p></p><p class=3DMsoPlainText>&gt; &gt;&gt; |&nbsp; http://www.eda-stds.org=
/pub/ibis/email/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; E-mail <o:=
p></o:p></p><p class=3DMsoPlainText>&gt; since 1993<o:p></o:p></p><p class=
=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; <o=
:p></o:p></p><p class=3DMsoPlainText>&gt; --<o:p></o:p></p><p class=3DMsoPl=
ainText>&gt; This message has been scanned for viruses and dangerous <o:p><=
/o:p></p><p class=3DMsoPlainText>&gt; content by MailScanner, and is believ=
ed to be clean.<o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><=
p class=3DMsoPlainText>&gt; -----------------------------------------------=
- ---------------------<o:p></o:p></p><p class=3DMsoPlainText>&gt; |For help =
or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org <o:p></o:p></p><=
p class=3DMsoPlainText>&gt; |with the appropriate command message(s) in the=
 body:<o:p></o:p></p><p class=3DMsoPlainText>&gt; |<o:p></o:p></p><p class=
=3DMsoPlainText>&gt; |&nbsp; help<o:p></o:p></p><p class=3DMsoPlainText>&gt=
; |&nbsp; subscribe&nbsp;&nbsp; ibis&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &l=
t;optional e-mail address, if different&gt;<o:p></o:p></p><p class=3DMsoPla=
inText>&gt; |&nbsp; subscribe&nbsp;&nbsp; ibis-users &lt;optional e-mail ad=
dress, if different&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; |&nbsp; =
unsubscribe ibis&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;optional e-mail ad=
dress, if different&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; |&nbsp; =
unsubscribe ibis-users &lt;optional e-mail address, if different&gt;<o:p></=
o:p></p><p class=3DMsoPlainText>&gt; |<o:p></o:p></p><p class=3DMsoPlainTex=
t>&gt; |or e-mail a request to ibis-request@eda-stds.org.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; |<o:p></o:p></p><p class=3DMsoPlainText>&gt; |IBI=
S reflector archives exist under:<o:p></o:p></p><p class=3DMsoPlainText>&gt=
; |<o:p></o:p></p><p class=3DMsoPlainText>&gt; |&nbsp; http://www.eda-stds.=
org/pub/ibis/email_archive/ Recent&nbsp; <o:p></o:p></p><p class=3DMsoPlain=
Text>&gt; | http://www.eda-stds.org/pub/ibis/users_archive/ Recent<o:p></o:=
p></p><p class=3DMsoPlainText>&gt; |&nbsp; http://www.eda-stds.org/pub/ibis=
/email/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; E-mail since 1993<o=
:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlai=
nText><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><br>-- <br>This message has=
 been scanned for viruses and <br>dangerous content by <a href=3D"http://ww=
w.mailscanner.info/"><b>MailScanner</b></a>, and is <br>believed to be clea=
n. <o:p></o:p></p></div><br />--=20
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href=3D"http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>

- ------_=_NextPart_001_01CC212B.B13B969F--
- --------------------------------------------------------------------
|For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
|with the appropriate command message(s) in the body:
|
|  help
|  subscribe   ibis       <optional e-mail address, if different>
|  subscribe   ibis-users <optional e-mail address, if different>
|  unsubscribe ibis       <optional e-mail address, if different>
|  unsubscribe ibis-users <optional e-mail address, if different>
|
|or e-mail a request to ibis-request@eda-stds.org.
|
|IBIS reflector archives exist under:
|
|  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/users_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993

------------------------------

Date: Wed, 8 Jun 2011 13:36:11 +0300
From: "Maher, Amin" <Amin_Maher@mentor.com>
Subject: [IBIS-Users] mutual inductance in EBD files

- ------_=_NextPart_001_01CC25C7.E4659C69
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello experts,

=20

Is there a way to describe mutual inductance (coupling) between EBD
paths.

=20

Regards,

Amin Maher=20


- --=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


- ------_=_NextPart_001_01CC25C7.E4659C69
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta http-equi=
v=3DContent-Type content=3D"text/html; charset=3Dus-ascii"><meta name=3DGen=
erator content=3D"Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
- --></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hello experts,<o=
:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal=
>Is there a way to describe mutual inductance (coupling) between EBD paths.=
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNorm=
al>Regards,<o:p></o:p></p><p class=3DMsoNormal>Amin Maher <o:p></o:p></p></=
div><br />--=20
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href=3D"http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>

- ------_=_NextPart_001_01CC25C7.E4659C69--
- --------------------------------------------------------------------
|For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
|with the appropriate command message(s) in the body:
|
|  help
|  subscribe   ibis       <optional e-mail address, if different>
|  subscribe   ibis-users <optional e-mail address, if different>
|  unsubscribe ibis       <optional e-mail address, if different>
|  unsubscribe ibis-users <optional e-mail address, if different>
|
|or e-mail a request to ibis-request@eda-stds.org.
|
|IBIS reflector archives exist under:
|
|  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/users_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993

------------------------------

Date: Thu, 2 Jun 2011 07:55:05 -0400 (EDT)
From: "Walter Katz" <wkatz@sisoft.com>
Subject: RE: [IBIS-Users] Requesting for some help / information regarding the use of IBIS in SI simulation.

All,

IBIS is now discussing enhancements to the IBIS Package Models to support
complex, broadband and coupled package models. There will be presentations
made at the IBIS Summit next week at DAC on two proposals, both using a
soon to be approved IBIS Interconnect Spice Subckt (IBIS-ISS) language.
IBIS-ISS is a subset of HSPICE that the EDA Vendors in IBS have agreed to.
This new package model interface should address all of the issues that
have been raised in this e-mail thread. All interested parties should
carefully review what is being proposed to insure that these issues are
correctly addressed.

Walter

- -----Original Message-----
From: owner-ibis-users@eda.org [mailto:owner-ibis-users@eda.org] On Behalf
Of Brad Brim
Sent: Thursday, June 02, 2011 5:55 AM
To: 'Doug Burns'; 'Scott McMorrow'
Cc: 'Ray Anderson'; 'ibis-users'
Subject: RE: [IBIS-Users] Requesting for some help / information regarding
the use of IBIS in SI simulation.

hi guys,

Guess we'll agree to disagree.

I have experience with any number of simple packages that violate your
"better" supposition for a uniformly distributed TL model. Why would this
occur, because I completely agree with you that it is counter intuitive.

From a package I recently characterized in some detail for system SI/PI
analysis; let's say the net behaves as static RLC to 2Ghz, then at about
4GHz there is some form of resonance in the signals or the planes. There's
a suckout in the response and then at higher frequencies it behaves more
like the TL you guys propose. If you assume the TL, then you completely
miss this behavior, and I do mean "completely". For this DDR bus you
probably don't care about the spectrum above 8GHz where it is again more
TL like. But you certainly DO care about the spectrum between 2Ghz and
6Ghz where it looks nothing like a TL. If I choose properly a TEE or PI
circuit to model the behavior in this mid frequency range (since either
works to 2Ghz) then you get a much better transient system-level
simulation than using your proposed TL model. This is true even though the
TEE/PI response at higher frequencies is much worse than the uniform TL
model. There is energy in the mid spectrum but not in the high spectrum
for this application. If I use a multi-stage RLC model then select the
element values to fit the broadband response then I can get match at both
mid and high frequencies to well 10Ghz and make all of us happier (but
maybe not to 40GHz).

This is NOT a corner case. I see it in many of the package I characterize.
If I was trying to do a best fit to 40Ghz for this same package because my
signals had energy spread out that broadband, then it would probably be
better to use the uniform TL model. However, not all applications call for
it and the system is much better characterized with a model more correct
where the signals actually have energy.

cheers,
 -Brad 

> -----Original Message-----
> From: Doug Burns [mailto:dburns@sisoft.com]
> Sent: Wednesday, June 01, 2011 6:55 AM
> To: 'Scott McMorrow'; bradb@sigrity.com
> Cc: 'Ray Anderson'; 'ibis-users'
> Subject: RE: [IBIS-Users] Requesting for some help / information 
> regarding the use of IBIS in SI simulation.
> 
> All,
> 
>  I have to agree with Scott on this. For the type of packages as 
> outlined by Scott, if one were to take the detailed model from a 
> simulator and decompose it to a RLC format, the best correlation 
> between the detailed model and the simplified model will occur when 
> the simplified RLC is treated as a distributed structure such as a 
> transmission line. Like Scott, we have proven this multiple time on a 
> wide variety of package styles (leadframe through 24+ layer packages). 
> There is no disagreement that a detailed model will be better, 
> especially for high frequencies, but we must work within the limits of 
> what IBIS can support. The mode detailed that package description is 
> in IBIS, the better estimation we can make, but using lumped data for 
> high speed signals is just causing an issue where one really will not 
> exist. EDA tools need to make the best estimation of the available 
> data to predict performance.
> 
> Doug
> 
> Douglas Burns
> Signal Integrity Software, Inc
> 6 Clock Tower Place
> Maynard, MA 01754
> 978-461-0449 x14
> 
>  
> -----Original Message-----
> From: owner-ibis-users@eda.org
> [mailto:owner-ibis-users@eda.org] On Behalf Of Scott McMorrow
> Sent: Wednesday, June 01, 2011 9:33 AM
> To: bradb@sigrity.com
> Cc: 'Ray Anderson'; 'ibis-users'
> Subject: Re: [IBIS-Users] Requesting for some help / information 
> regarding the use of IBIS in SI simulation.
> 
> Brad
> 
> It is certainly your prerogative to disagree with me.  In the context 
> of the original question, we are not talking about randomly 
> distributed RLC, but rather package connections from board to silicon, 
> which is the case in most IBIS models.
> Given that, we know the general topology.  
> Whether the package uses lead frame, 2 layer FC packaging,
> 2/4 layer organic wire bond packaging, or multilayer buildup 
> packaging, a single path from die to ball looks remarkably similar to 
> cascaded transmission lines.  Even bond wires look like transmission 
> lines.
> 
> If I'm given a single RLC for an IBIS model of a conventionally 
> packaged silicon device , then I can guarantee you that the simulation 
> will be more faithful to measurements when the transmission line 
> equivalent is used, rather than lumped elements.  Been there, done the 
> measurements many, many times.  When multiple sections are specified 
> in the IBIS .pkg format, then there is no ambiguity, a non-zero RLC 
> section length defines a distributed element, and a zero length 
> section defines a lumped element.  The simulator should model it as 
> such.
> 
> Having done correlation of package modeling to measurements from DC to 
> 40 GHz on a 12-layer build-up with near zero error, I'm well aware of 
> the issues involved with using the wrong modeling method, and poor 
> material modeling.  I agree with you that a single RLC is an extremely 
> poor approximation of any complex package interconnect, or any 
> interconnect for that matter.  However, given that a user is presented 
> with an RLC that was extracted with a quasi-static solver, as is the 
> case with most IBIS models, I maintain that the result will be closer 
> to reality when transformed into the distributed transmission line 
> equivalent.  I've seen way too many cases where simulators used a 
> lumped RLC directly, grossly over predicting  ringing at the die and 
> in the channel, and confirmed by physical measurements.
> 
> When we get into full-wave and hybrid full-wave AC modeling of 
> packages there are a host of other issues that we can discuss, such as 
> accurate dielectric modeling, accurate surface roughness modeling, 
> as-designed vs. as-built package geometries, +/- 15% impedance 
> variation due to manufacturing process  and electromagnetic 
> non-locality.  But that is for another time.
> 
> 
> best regards,
> 
> Scott
> 
> 
> Scott McMorrow
> Teraspeed Consulting Group LLC
> 121 North River Drive
> Narragansett, RI 02882
> (401) 284-1827 Business
> (401) 284-1840 Fax
> 
> http://www.teraspeed.com
> 
> TeraspeedR is the registered service mark of Teraspeed 
> Consulting Group LLC
> 
> 
> On 6/1/2011 1:53 AM, Brad Brim wrote:
> > hello Scott,
> >
> > I don't agree with you. Such simulators (or model extractors which 
> > write
> out
> > such "postprocessed" model data) are no more assured accurate than
> simply
> > applying or writing out the base RLC data.
> >
> > Most package extractors, especially ones you may refer to as 
> > applicable "from the beginning", are based on static RLC 
> simulation in 
> > which a
> single L
> > and C are extracted at exactly DC from two distinct simulations; 
> > magnetostatic and electrostatic respectively. One has NO CLUE how to
> form
> > the equivalent circuit given only the static lumped L and C 
> computed 
> > independently. Of course, as asked and discussed by Ray, if 
> the user 
> > has insight from the physical structure then a more broadband model 
> > MIGHT be generated, but there is no guarantee!
> > One person assuming a PI circuit (with the C split equally 
> in half - 
> > or
> even
> > unequally - and the L in the middle) and another person 
> assuming a TEE 
> > circuit (with the L split and the shunt C in the middle) are no more
> correct
> > than the other. One has NO IDEA of the high frequency 
> behavior of the 
> > circuit (either just above the quasistatic limit where the likely
> spectral
> > content is relevant or higher where it is less likely relevant) 
> > without
> some
> > form of AC high-frequency simulation or measurement. The 
> behavior at 
> > "infinite" frequency in meaningless and to argue that a uniformly 
> > distributed multi-stage ladder network is valid has no more
> justification
> > than another person arguing it should me a lowpass network with all 
> > the inductance on the die side because of wirebond inductance. This 
> > argument
> has
> > blindly been accepted and argued for many years. It has been 
> > unjustified
> and
> > wrong, as you would say, "from the beginning".
> >
> > Want a valid model at higher frequencies, then extract AC 
> information
> from
> > which to generate it. One's guess or intuitive argument without AC 
> > information to back it up is only a guess, as Andy stated. The 
> > classical uniformly distributed ladder network is a 
> deceptively simple 
> > and
> intuitively
> > pleasing assumption that is easy to understand and unfortunately
> accepted by
> > way too many people in the industry. This supposed more 
> accurate guess
> has
> > failed in too many cases and can even be worse than a 
> simple totally 
> > unbalanced low pass filter assumption over the frequency 
> spectrum of 
> > relevance.
> >
> > Many commercially available RLC extractors continue to make this
> assumption
> > today. Users are placed at significant risk because they falsely 
> > believe
> the
> > model is in some sense "broadband" or "wideband". It is a 
> guess with 
> > no guarantee to be any better than any other assumed more 
> distributed 
> > equivalent circuit for which there is no theoretical or physical 
> > justification.
> >
> > If one starts with AC data, assumes an equivalent circuit and *then*
> selects
> > element values in such to fit the data then there is reason to argue
> this is
> > a more valid model at higher frequencies. One cannot do 
> this from only
> DC
> > terminal-based data. Not that it's difficult, it is impossible.
> >
> > best regards,
> >   -Brad
> >
> >
> >> -----Original Message-----
> >> From: owner-ibis-users@eda.org
> >> [mailto:owner-ibis-users@eda.org] On Behalf Of Scott McMorrow
> >> Sent: Tuesday, May 31, 2011 5:04 PM
> >> To: Ray Anderson
> >> Cc: ibis-users; Ray Anderson
> >> Subject: Re: [IBIS-Users] Requesting for some help / information 
> >> regarding the use of IBIS in SI simulation.
> >>
> >> Since the beginning of IBIS, the most accurate simulators 
> would turn 
> >> the RLC package parasitics into a transmission line 
> equivalent.  In 
> >> lieu of any additional information it is the most 
> reasonable thing to 
> >> do, since packages can be approximated as transmission lines.
> >>
> >>
> >> Scott McMorrow
> >> Teraspeed Consulting Group LLC
> >> 121 North River Drive
> >> Narragansett, RI 02882
> >> (401) 284-1827 Business
> >> (401) 284-1840 Fax
> >>
> >> http://www.teraspeed.com
> >>
> >> TeraspeedR is the registered service mark of Teraspeed Consulting 
> >> Group LLC
> >>
> >>
> >> On 5/31/2011 7:59 PM, Ray Anderson wrote:
> >>> If you are using extracted RLC data to manually set up 
> the package 
> >>> model you can certainly make intelligent decisions on the
> >> topology of
> >>> the model and the distribution of the RLC parasitics.
> >> However if you
> >>> are depending on a simulator to read the data from a IBIS
> >> .pkg format
> >>> file (or the [PIN] data) and set up a model for you then
> >> your results
> >>> may differ from simulator to simulator.
> >>>
> >>> -Ray
> >>> Xilinx Inc.
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: owner-ibis-users@eda.org 
> [mailto:owner-ibis-users@eda.org] On 
> >>> Behalf Of Andrew Ingraham
> >>> Sent: Tuesday, May 31, 2011 4:48 PM
> >>> To: ibis-users
> >>> Subject: Re: [IBIS-Users] Requesting for some help / information 
> >>> regarding the use of IBIS in SI simulation.
> >>>
> >>> Yes.
> >>>
> >>> I am usually tempted to start with an evenly distributed
> >> RLC model ...
> >>> unless I have reason to think that the distribution is
> >> otherwise.  For
> >>> example, wirebonds might have most of the inductance and
> >> resistance,
> >>> whereas the leadframe may have more capacitance, which
> >> might influence
> >>> one to imbalance those factors unequally between die end
> >> and pin end.
> >>> But without hard data to back it up, that is just guessing.
> >>>
> >>> Andy
> >>>
> >> --
> >> This message has been scanned for viruses and dangerous content by 
> >> MailScanner, and is believed to be clean.
> >>
> >> 
> --------------------------------------------------------------------
> >> |For help or to subscribe/unsubscribe, e-mail 
> majordomo@eda-stds.org 
> >> |with the appropriate command message(s) in the body:
> >> |
> >> |  help
> >> |  subscribe   ibis<optional e-mail address, if different>
> >> |  subscribe   ibis-users<optional e-mail address, if different>
> >> |  unsubscribe ibis<optional e-mail address, if different>  
> >> | unsubscribe ibis-users<optional e-mail address, if different>
> >> |
> >> |or e-mail a request to ibis-request@eda-stds.org.
> >> |
> >> |IBIS reflector archives exist under:
> >> |
> >> |  http://www.eda-stds.org/pub/ibis/email_archive/ Recent 
> >> | http://www.eda-stds.org/pub/ibis/users_archive/ Recent
> >> |  http://www.eda-stds.org/pub/ibis/email/         E-mail 
> since 1993
> >>
> 
> --
> This message has been scanned for viruses and dangerous 
> content by MailScanner, and is believed to be clean.
> 
> --------------------------------------------------------------------
> |For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org 
> |with the appropriate command message(s) in the body:
> |
> |  help
> |  subscribe   ibis       <optional e-mail address, if different>
> |  subscribe   ibis-users <optional e-mail address, if different>
> |  unsubscribe ibis       <optional e-mail address, if different>
> |  unsubscribe ibis-users <optional e-mail address, if different>
> |
> |or e-mail a request to ibis-request@eda-stds.org.
> |
> |IBIS reflector archives exist under:
> |
> |  http://www.eda-stds.org/pub/ibis/email_archive/ Recent  
> | http://www.eda-stds.org/pub/ibis/users_archive/ Recent
> |  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993
> 


- -- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

- --------------------------------------------------------------------
|For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
|with the appropriate command message(s) in the body:
|
|  help
|  subscribe   ibis       <optional e-mail address, if different>
|  subscribe   ibis-users <optional e-mail address, if different>
|  unsubscribe ibis       <optional e-mail address, if different>
|  unsubscribe ibis-users <optional e-mail address, if different>
|
|or e-mail a request to ibis-request@eda-stds.org.
|
|IBIS reflector archives exist under:
|
|  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/users_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993

- -- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

- --------------------------------------------------------------------
|For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
|with the appropriate command message(s) in the body:
|
|  help
|  subscribe   ibis       <optional e-mail address, if different>
|  subscribe   ibis-users <optional e-mail address, if different>
|  unsubscribe ibis       <optional e-mail address, if different>
|  unsubscribe ibis-users <optional e-mail address, if different>
|
|or e-mail a request to ibis-request@eda-stds.org.
|
|IBIS reflector archives exist under:
|
|  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/users_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993

------------------------------

Date: Thu, 9 Jun 2011 10:03:55 -0700
From: "Muranyi, Arpad" <Arpad_Muranyi@mentor.com>
Subject: RE: [IBIS-Users] mutual inductance in EBD files

This is a multi-part message in MIME format.

- ------_=_NextPart_001_01CC26C7.377DA9CE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Amin,

=20

Looks like the answer is NO.  Even though the EBD syntax is

almost identical to the package syntax for the multi-segment

uncoupled T-line style trace descriptions, the lumped RLC

coupled matrix syntax of package models is not available

for EBD models.

=20

Thanks,

=20

Arpad

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

=20

=20

From: owner-ibis-users@eda.org [mailto:owner-ibis-users@eda.org] On
Behalf Of Maher, Amin
Sent: Wednesday, June 08, 2011 5:36 AM
To: ibis-users@eda.org
Subject: [IBIS-Users] mutual inductance in EBD files

=20

Hello experts,

=20

Is there a way to describe mutual inductance (coupling) between EBD
paths.

=20

Regards,

Amin Maher=20


- --=20
This message has been scanned for viruses and=20
dangerous content by MailScanner <http://www.mailscanner.info/> , and is

believed to be clean.=20


- --=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


- ------_=_NextPart_001_01CC26C7.377DA9CE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta http-equi=
v=3DContent-Type content=3D"text/html; charset=3Dus-ascii"><meta name=3DGen=
erator content=3D"Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
- --></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:black'>Amin,<o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Co=
urier New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>Looks =
like the answer is NO.&nbsp; Even though the EBD syntax is<o:p></o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Cour=
ier New";color:black'>almost identical to the package syntax for the multi-=
segment<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:=
10.0pt;font-family:"Courier New";color:black'>uncoupled T-line style trace =
descriptions, the lumped RLC<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>coupled =
matrix syntax of package models is not available<o:p></o:p></span></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";c=
olor:black'>for EBD models.<o:p></o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbs=
p;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fon=
t-family:"Courier New";color:black'>Thanks,<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";colo=
r:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'fo=
nt-size:10.0pt;font-family:"Courier New";color:black'>Arpad<o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Cou=
rier New";color:black'>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Co=
urier New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&=
nbsp;</o:p></span></p><div><div style=3D'border:none;border-top:solid #B5C4=
DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'=
font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span s=
tyle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> owner-ibis-use=
rs@eda.org [mailto:owner-ibis-users@eda.org] <b>On Behalf Of </b>Maher, Ami=
n<br><b>Sent:</b> Wednesday, June 08, 2011 5:36 AM<br><b>To:</b> ibis-users=
@eda.org<br><b>Subject:</b> [IBIS-Users] mutual inductance in EBD files<o:p=
></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Hello experts,<o:p></o:p></p><p class=3DMsoNormal><o:p>&n=
bsp;</o:p></p><p class=3DMsoNormal>Is there a way to describe mutual induct=
ance (coupling) between EBD paths.<o:p></o:p></p><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p><p class=3DMsoNormal>Regards,<o:p></o:p></p><p class=3DMsoN=
ormal>Amin Maher <o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-si=
ze:12.0pt;font-family:"Times New Roman","serif"'><br>-- <br>This message ha=
s been scanned for viruses and <br>dangerous content by <a href=3D"http://w=
ww.mailscanner.info/"><b>MailScanner</b></a>, and is <br>believed to be cle=
an. <o:p></o:p></span></p></div><br />--=20
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href=3D"http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>

- ------_=_NextPart_001_01CC26C7.377DA9CE--
- --------------------------------------------------------------------
|For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
|with the appropriate command message(s) in the body:
|
|  help
|  subscribe   ibis       <optional e-mail address, if different>
|  subscribe   ibis-users <optional e-mail address, if different>
|  unsubscribe ibis       <optional e-mail address, if different>
|  unsubscribe ibis-users <optional e-mail address, if different>
|
|or e-mail a request to ibis-request@eda-stds.org.
|
|IBIS reflector archives exist under:
|
|  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/users_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993

------------------------------

Date: Thu, 2 Jun 2011 02:55:03 -0700
From: "Brad Brim" <bradb@sigrity.com>
Subject: RE: [IBIS-Users] Requesting for some help / information regarding the use of IBIS in SI simulation.

hi guys,

Guess we'll agree to disagree.

I have experience with any number of simple packages that violate your
"better" supposition for a uniformly distributed TL model. Why would this
occur, because I completely agree with you that it is counter intuitive.

From a package I recently characterized in some detail for system SI/PI
analysis; let's say the net behaves as static RLC to 2Ghz, then at about
4GHz there is some form of resonance in the signals or the planes. There's a
suckout in the response and then at higher frequencies it behaves more like
the TL you guys propose. If you assume the TL, then you completely miss this
behavior, and I do mean "completely". For this DDR bus you probably don't
care about the spectrum above 8GHz where it is again more TL like. But you
certainly DO care about the spectrum between 2Ghz and 6Ghz where it looks
nothing like a TL. If I choose properly a TEE or PI circuit to model the
behavior in this mid frequency range (since either works to 2Ghz) then you
get a much better transient system-level simulation than using your proposed
TL model. This is true even though the TEE/PI response at higher frequencies
is much worse than the uniform TL model. There is energy in the mid spectrum
but not in the high spectrum for this application. If I use a multi-stage
RLC model then select the element values to fit the broadband response then
I can get match at both mid and high frequencies to well 10Ghz and make all
of us happier (but maybe not to 40GHz).

This is NOT a corner case. I see it in many of the package I characterize.
If I was trying to do a best fit to 40Ghz for this same package because my
signals had energy spread out that broadband, then it would probably be
better to use the uniform TL model. However, not all applications call for
it and the system is much better characterized with a model more correct
where the signals actually have energy.

cheers,
 -Brad 

> -----Original Message-----
> From: Doug Burns [mailto:dburns@sisoft.com] 
> Sent: Wednesday, June 01, 2011 6:55 AM
> To: 'Scott McMorrow'; bradb@sigrity.com
> Cc: 'Ray Anderson'; 'ibis-users'
> Subject: RE: [IBIS-Users] Requesting for some help / 
> information regarding the use of IBIS in SI simulation.
> 
> All,
> 
>  I have to agree with Scott on this. For the type of packages 
> as outlined by Scott, if one were to take the detailed model 
> from a simulator and decompose it to a RLC format, the best 
> correlation between the detailed model and the simplified 
> model will occur when the simplified RLC is treated as a 
> distributed structure such as a transmission line. Like 
> Scott, we have proven this multiple time on a wide variety of 
> package styles (leadframe through 24+ layer packages). There 
> is no disagreement that a detailed model will be better, 
> especially for high frequencies, but we must work within the 
> limits of what IBIS can support. The mode detailed that 
> package description is in IBIS, the better estimation we can 
> make, but using lumped data for high speed signals is just 
> causing an issue where one really will not exist. EDA tools 
> need to make the best estimation of the available data to 
> predict performance.
> 
> Doug
> 
> Douglas Burns
> Signal Integrity Software, Inc
> 6 Clock Tower Place
> Maynard, MA 01754
> 978-461-0449 x14
> 
>  
> -----Original Message-----
> From: owner-ibis-users@eda.org 
> [mailto:owner-ibis-users@eda.org] On Behalf Of Scott McMorrow
> Sent: Wednesday, June 01, 2011 9:33 AM
> To: bradb@sigrity.com
> Cc: 'Ray Anderson'; 'ibis-users'
> Subject: Re: [IBIS-Users] Requesting for some help / 
> information regarding the use of IBIS in SI simulation.
> 
> Brad
> 
> It is certainly your prerogative to disagree with me.  In the 
> context of the original question, we are not talking about 
> randomly distributed RLC, but rather package connections from 
> board to silicon, which is the case in most IBIS models.  
> Given that, we know the general topology.  
> Whether the package uses lead frame, 2 layer FC packaging, 
> 2/4 layer organic wire bond packaging, or multilayer buildup 
> packaging, a single path from die to ball looks remarkably 
> similar to cascaded transmission lines.  Even bond wires look 
> like transmission lines.
> 
> If I'm given a single RLC for an IBIS model of a 
> conventionally packaged silicon device , then I can guarantee 
> you that the simulation will be more faithful to measurements 
> when the transmission line equivalent is used, rather than 
> lumped elements.  Been there, done the measurements many, 
> many times.  When multiple sections are specified in the IBIS 
> .pkg format, then there is no ambiguity, a non-zero RLC 
> section length defines a distributed element, and a zero 
> length section defines a lumped element.  The simulator 
> should model it as such.
> 
> Having done correlation of package modeling to measurements 
> from DC to 40 GHz on a 12-layer build-up with near zero 
> error, I'm well aware of the issues involved with using the 
> wrong modeling method, and poor material modeling.  I agree 
> with you that a single RLC is an extremely poor approximation 
> of any complex package interconnect, or any interconnect for 
> that matter.  However, given that a user is presented with an 
> RLC that was extracted with a quasi-static solver, as is the 
> case with most IBIS models, I maintain that the result will 
> be closer to reality when transformed into the distributed 
> transmission line equivalent.  I've seen way too many cases 
> where simulators used a lumped RLC directly, grossly over 
> predicting  ringing at the die and in the channel, and 
> confirmed by physical measurements.
> 
> When we get into full-wave and hybrid full-wave AC modeling 
> of packages there are a host of other issues that we can 
> discuss, such as accurate dielectric modeling, accurate 
> surface roughness modeling, as-designed vs. as-built package 
> geometries, +/- 15% impedance variation due to manufacturing 
> process  and electromagnetic non-locality.  But that is for 
> another time.
> 
> 
> best regards,
> 
> Scott
> 
> 
> Scott McMorrow
> Teraspeed Consulting Group LLC
> 121 North River Drive
> Narragansett, RI 02882
> (401) 284-1827 Business
> (401) 284-1840 Fax
> 
> http://www.teraspeed.com
> 
> TeraspeedR is the registered service mark of Teraspeed 
> Consulting Group LLC
> 
> 
> On 6/1/2011 1:53 AM, Brad Brim wrote:
> > hello Scott,
> >
> > I don't agree with you. Such simulators (or model extractors which 
> > write
> out
> > such "postprocessed" model data) are no more assured accurate than
> simply
> > applying or writing out the base RLC data.
> >
> > Most package extractors, especially ones you may refer to as 
> > applicable "from the beginning", are based on static RLC 
> simulation in 
> > which a
> single L
> > and C are extracted at exactly DC from two distinct simulations; 
> > magnetostatic and electrostatic respectively. One has NO CLUE how to
> form
> > the equivalent circuit given only the static lumped L and C 
> computed 
> > independently. Of course, as asked and discussed by Ray, if 
> the user 
> > has insight from the physical structure then a more broadband model 
> > MIGHT be generated, but there is no guarantee!
> > One person assuming a PI circuit (with the C split equally 
> in half - 
> > or
> even
> > unequally - and the L in the middle) and another person 
> assuming a TEE 
> > circuit (with the L split and the shunt C in the middle) are no more
> correct
> > than the other. One has NO IDEA of the high frequency 
> behavior of the 
> > circuit (either just above the quasistatic limit where the likely
> spectral
> > content is relevant or higher where it is less likely relevant) 
> > without
> some
> > form of AC high-frequency simulation or measurement. The 
> behavior at 
> > "infinite" frequency in meaningless and to argue that a uniformly 
> > distributed multi-stage ladder network is valid has no more
> justification
> > than another person arguing it should me a lowpass network with all 
> > the inductance on the die side because of wirebond inductance. This 
> > argument
> has
> > blindly been accepted and argued for many years. It has been 
> > unjustified
> and
> > wrong, as you would say, "from the beginning".
> >
> > Want a valid model at higher frequencies, then extract AC 
> information
> from
> > which to generate it. One's guess or intuitive argument without AC 
> > information to back it up is only a guess, as Andy stated. The 
> > classical uniformly distributed ladder network is a 
> deceptively simple 
> > and
> intuitively
> > pleasing assumption that is easy to understand and unfortunately
> accepted by
> > way too many people in the industry. This supposed more 
> accurate guess
> has
> > failed in too many cases and can even be worse than a 
> simple totally 
> > unbalanced low pass filter assumption over the frequency 
> spectrum of 
> > relevance.
> >
> > Many commercially available RLC extractors continue to make this
> assumption
> > today. Users are placed at significant risk because they falsely 
> > believe
> the
> > model is in some sense "broadband" or "wideband". It is a 
> guess with 
> > no guarantee to be any better than any other assumed more 
> distributed 
> > equivalent circuit for which there is no theoretical or physical 
> > justification.
> >
> > If one starts with AC data, assumes an equivalent circuit and *then*
> selects
> > element values in such to fit the data then there is reason to argue
> this is
> > a more valid model at higher frequencies. One cannot do 
> this from only
> DC
> > terminal-based data. Not that it's difficult, it is impossible.
> >
> > best regards,
> >   -Brad
> >
> >
> >> -----Original Message-----
> >> From: owner-ibis-users@eda.org
> >> [mailto:owner-ibis-users@eda.org] On Behalf Of Scott McMorrow
> >> Sent: Tuesday, May 31, 2011 5:04 PM
> >> To: Ray Anderson
> >> Cc: ibis-users; Ray Anderson
> >> Subject: Re: [IBIS-Users] Requesting for some help / information 
> >> regarding the use of IBIS in SI simulation.
> >>
> >> Since the beginning of IBIS, the most accurate simulators 
> would turn 
> >> the RLC package parasitics into a transmission line 
> equivalent.  In 
> >> lieu of any additional information it is the most 
> reasonable thing to 
> >> do, since packages can be approximated as transmission lines.
> >>
> >>
> >> Scott McMorrow
> >> Teraspeed Consulting Group LLC
> >> 121 North River Drive
> >> Narragansett, RI 02882
> >> (401) 284-1827 Business
> >> (401) 284-1840 Fax
> >>
> >> http://www.teraspeed.com
> >>
> >> TeraspeedR is the registered service mark of Teraspeed Consulting 
> >> Group LLC
> >>
> >>
> >> On 5/31/2011 7:59 PM, Ray Anderson wrote:
> >>> If you are using extracted RLC data to manually set up 
> the package 
> >>> model you can certainly make intelligent decisions on the
> >> topology of
> >>> the model and the distribution of the RLC parasitics.
> >> However if you
> >>> are depending on a simulator to read the data from a IBIS
> >> .pkg format
> >>> file (or the [PIN] data) and set up a model for you then
> >> your results
> >>> may differ from simulator to simulator.
> >>>
> >>> -Ray
> >>> Xilinx Inc.
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: owner-ibis-users@eda.org 
> [mailto:owner-ibis-users@eda.org] On 
> >>> Behalf Of Andrew Ingraham
> >>> Sent: Tuesday, May 31, 2011 4:48 PM
> >>> To: ibis-users
> >>> Subject: Re: [IBIS-Users] Requesting for some help / information 
> >>> regarding the use of IBIS in SI simulation.
> >>>
> >>> Yes.
> >>>
> >>> I am usually tempted to start with an evenly distributed
> >> RLC model ...
> >>> unless I have reason to think that the distribution is
> >> otherwise.  For
> >>> example, wirebonds might have most of the inductance and
> >> resistance,
> >>> whereas the leadframe may have more capacitance, which
> >> might influence
> >>> one to imbalance those factors unequally between die end
> >> and pin end.
> >>> But without hard data to back it up, that is just guessing.
> >>>
> >>> Andy
> >>>
> >> --
> >> This message has been scanned for viruses and dangerous content by 
> >> MailScanner, and is believed to be clean.
> >>
> >> 
> --------------------------------------------------------------------
> >> |For help or to subscribe/unsubscribe, e-mail 
> majordomo@eda-stds.org 
> >> |with the appropriate command message(s) in the body:
> >> |
> >> |  help
> >> |  subscribe   ibis<optional e-mail address, if different>
> >> |  subscribe   ibis-users<optional e-mail address, if different>
> >> |  unsubscribe ibis<optional e-mail address, if different>  
> >> | unsubscribe ibis-users<optional e-mail address, if different>
> >> |
> >> |or e-mail a request to ibis-request@eda-stds.org.
> >> |
> >> |IBIS reflector archives exist under:
> >> |
> >> |  http://www.eda-stds.org/pub/ibis/email_archive/ Recent 
> >> | http://www.eda-stds.org/pub/ibis/users_archive/ Recent
> >> |  http://www.eda-stds.org/pub/ibis/email/         E-mail 
> since 1993
> >>
> 
> --
> This message has been scanned for viruses and dangerous 
> content by MailScanner, and is believed to be clean.
> 
> --------------------------------------------------------------------
> |For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org 
> |with the appropriate command message(s) in the body:
> |
> |  help
> |  subscribe   ibis       <optional e-mail address, if different>
> |  subscribe   ibis-users <optional e-mail address, if different>
> |  unsubscribe ibis       <optional e-mail address, if different>
> |  unsubscribe ibis-users <optional e-mail address, if different>
> |
> |or e-mail a request to ibis-request@eda-stds.org.
> |
> |IBIS reflector archives exist under:
> |
> |  http://www.eda-stds.org/pub/ibis/email_archive/ Recent  
> | http://www.eda-stds.org/pub/ibis/users_archive/ Recent
> |  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993
> 


- -- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

- --------------------------------------------------------------------
|For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
|with the appropriate command message(s) in the body:
|
|  help
|  subscribe   ibis       <optional e-mail address, if different>
|  subscribe   ibis-users <optional e-mail address, if different>
|  unsubscribe ibis       <optional e-mail address, if different>
|  unsubscribe ibis-users <optional e-mail address, if different>
|
|or e-mail a request to ibis-request@eda-stds.org.
|
|IBIS reflector archives exist under:
|
|  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/users_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993

------------------------------

Date: Wed, 1 Jun 2011 09:55:03 -0400 (EDT)
From: "Doug Burns" <dburns@sisoft.com>
Subject: RE: [IBIS-Users] Requesting for some help / information regarding the use of IBIS in SI simulation.

All,

 I have to agree with Scott on this. For the type of packages as outlined
by Scott, if one were to take the detailed model from a simulator and
decompose it to a RLC format, the best correlation between the detailed
model and the simplified model will occur when the simplified RLC is
treated as a distributed structure such as a transmission line. Like
Scott, we have proven this multiple time on a wide variety of package
styles (leadframe through 24+ layer packages). There is no disagreement
that a detailed model will be better, especially for high frequencies, but
we must work within the limits of what IBIS can support. The mode detailed
that package description is in IBIS, the better estimation we can make,
but using lumped data for high speed signals is just causing an issue
where one really will not exist. EDA tools need to make the best
estimation of the available data to predict performance.

Doug

Douglas Burns
Signal Integrity Software, Inc
6 Clock Tower Place
Maynard, MA 01754
978-461-0449 x14

 
- -----Original Message-----
From: owner-ibis-users@eda.org [mailto:owner-ibis-users@eda.org] On Behalf
Of Scott McMorrow
Sent: Wednesday, June 01, 2011 9:33 AM
To: bradb@sigrity.com
Cc: 'Ray Anderson'; 'ibis-users'
Subject: Re: [IBIS-Users] Requesting for some help / information regarding
the use of IBIS in SI simulation.

Brad

It is certainly your prerogative to disagree with me.  In the context of 
the original question, we are not talking about randomly distributed 
RLC, but rather package connections from board to silicon, which is the 
case in most IBIS models.  Given that, we know the general topology.  
Whether the package uses lead frame, 2 layer FC packaging, 2/4 layer 
organic wire bond packaging, or multilayer buildup packaging, a single 
path from die to ball looks remarkably similar to cascaded transmission 
lines.  Even bond wires look like transmission lines.

If I'm given a single RLC for an IBIS model of a conventionally packaged 
silicon device , then I can guarantee you that the simulation will be 
more faithful to measurements when the transmission line equivalent is 
used, rather than lumped elements.  Been there, done the measurements 
many, many times.  When multiple sections are specified in the IBIS .pkg 
format, then there is no ambiguity, a non-zero RLC section length 
defines a distributed element, and a zero length section defines a 
lumped element.  The simulator should model it as such.

Having done correlation of package modeling to measurements from DC to 
40 GHz on a 12-layer build-up with near zero error, I'm well aware of 
the issues involved with using the wrong modeling method, and poor 
material modeling.  I agree with you that a single RLC is an extremely 
poor approximation of any complex package interconnect, or any 
interconnect for that matter.  However, given that a user is presented 
with an RLC that was extracted with a quasi-static solver, as is the 
case with most IBIS models, I maintain that the result will be closer to 
reality when transformed into the distributed transmission line 
equivalent.  I've seen way too many cases where simulators used a lumped 
RLC directly, grossly over predicting  ringing at the die and in the 
channel, and confirmed by physical measurements.

When we get into full-wave and hybrid full-wave AC modeling of packages 
there are a host of other issues that we can discuss, such as accurate 
dielectric modeling, accurate surface roughness modeling, as-designed 
vs. as-built package geometries, +/- 15% impedance variation due to 
manufacturing process  and electromagnetic non-locality.  But that is 
for another time.


best regards,

Scott


Scott McMorrow
Teraspeed Consulting Group LLC
121 North River Drive
Narragansett, RI 02882
(401) 284-1827 Business
(401) 284-1840 Fax

http://www.teraspeed.com

TeraspeedR is the registered service mark of
Teraspeed Consulting Group LLC


On 6/1/2011 1:53 AM, Brad Brim wrote:
> hello Scott,
>
> I don't agree with you. Such simulators (or model extractors which write
out
> such "postprocessed" model data) are no more assured accurate than
simply
> applying or writing out the base RLC data.
>
> Most package extractors, especially ones you may refer to as applicable
> "from the beginning", are based on static RLC simulation in which a
single L
> and C are extracted at exactly DC from two distinct simulations;
> magnetostatic and electrostatic respectively. One has NO CLUE how to
form
> the equivalent circuit given only the static lumped L and C computed
> independently. Of course, as asked and discussed by Ray, if the user has
> insight from the physical structure then a more broadband model MIGHT be
> generated, but there is no guarantee!
> One person assuming a PI circuit (with the C split equally in half - or
even
> unequally - and the L in the middle) and another person assuming a TEE
> circuit (with the L split and the shunt C in the middle) are no more
correct
> than the other. One has NO IDEA of the high frequency behavior of the
> circuit (either just above the quasistatic limit where the likely
spectral
> content is relevant or higher where it is less likely relevant) without
some
> form of AC high-frequency simulation or measurement. The behavior at
> "infinite" frequency in meaningless and to argue that a uniformly
> distributed multi-stage ladder network is valid has no more
justification
> than another person arguing it should me a lowpass network with all the
> inductance on the die side because of wirebond inductance. This argument
has
> blindly been accepted and argued for many years. It has been unjustified
and
> wrong, as you would say, "from the beginning".
>
> Want a valid model at higher frequencies, then extract AC information
from
> which to generate it. One's guess or intuitive argument without AC
> information to back it up is only a guess, as Andy stated. The classical
> uniformly distributed ladder network is a deceptively simple and
intuitively
> pleasing assumption that is easy to understand and unfortunately
accepted by
> way too many people in the industry. This supposed more accurate guess
has
> failed in too many cases and can even be worse than a simple totally
> unbalanced low pass filter assumption over the frequency spectrum of
> relevance.
>
> Many commercially available RLC extractors continue to make this
assumption
> today. Users are placed at significant risk because they falsely believe
the
> model is in some sense "broadband" or "wideband". It is a guess with no
> guarantee to be any better than any other assumed more distributed
> equivalent circuit for which there is no theoretical or physical
> justification.
>
> If one starts with AC data, assumes an equivalent circuit and *then*
selects
> element values in such to fit the data then there is reason to argue
this is
> a more valid model at higher frequencies. One cannot do this from only
DC
> terminal-based data. Not that it's difficult, it is impossible.
>
> best regards,
>   -Brad
>
>
>> -----Original Message-----
>> From: owner-ibis-users@eda.org
>> [mailto:owner-ibis-users@eda.org] On Behalf Of Scott McMorrow
>> Sent: Tuesday, May 31, 2011 5:04 PM
>> To: Ray Anderson
>> Cc: ibis-users; Ray Anderson
>> Subject: Re: [IBIS-Users] Requesting for some help /
>> information regarding the use of IBIS in SI simulation.
>>
>> Since the beginning of IBIS, the most accurate simulators
>> would turn the RLC package parasitics into a transmission
>> line equivalent.  In lieu of any additional information it is
>> the most reasonable thing to do, since packages can be
>> approximated as transmission lines.
>>
>>
>> Scott McMorrow
>> Teraspeed Consulting Group LLC
>> 121 North River Drive
>> Narragansett, RI 02882
>> (401) 284-1827 Business
>> (401) 284-1840 Fax
>>
>> http://www.teraspeed.com
>>
>> TeraspeedR is the registered service mark of Teraspeed
>> Consulting Group LLC
>>
>>
>> On 5/31/2011 7:59 PM, Ray Anderson wrote:
>>> If you are using extracted RLC data to manually set up the package
>>> model you can certainly make intelligent decisions on the
>> topology of
>>> the model and the distribution of the RLC parasitics.
>> However if you
>>> are depending on a simulator to read the data from a IBIS
>> .pkg format
>>> file (or the [PIN] data) and set up a model for you then
>> your results
>>> may differ from simulator to simulator.
>>>
>>> -Ray
>>> Xilinx Inc.
>>>
>>>
>>> -----Original Message-----
>>> From: owner-ibis-users@eda.org [mailto:owner-ibis-users@eda.org] On
>>> Behalf Of Andrew Ingraham
>>> Sent: Tuesday, May 31, 2011 4:48 PM
>>> To: ibis-users
>>> Subject: Re: [IBIS-Users] Requesting for some help / information
>>> regarding the use of IBIS in SI simulation.
>>>
>>> Yes.
>>>
>>> I am usually tempted to start with an evenly distributed
>> RLC model ...
>>> unless I have reason to think that the distribution is
>> otherwise.  For
>>> example, wirebonds might have most of the inductance and
>> resistance,
>>> whereas the leadframe may have more capacitance, which
>> might influence
>>> one to imbalance those factors unequally between die end
>> and pin end.
>>> But without hard data to back it up, that is just guessing.
>>>
>>> Andy
>>>
>> --
>> This message has been scanned for viruses and dangerous
>> content by MailScanner, and is believed to be clean.
>>
>> --------------------------------------------------------------------
>> |For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
>> |with the appropriate command message(s) in the body:
>> |
>> |  help
>> |  subscribe   ibis<optional e-mail address, if different>
>> |  subscribe   ibis-users<optional e-mail address, if different>
>> |  unsubscribe ibis<optional e-mail address, if different>
>> |  unsubscribe ibis-users<optional e-mail address, if different>
>> |
>> |or e-mail a request to ibis-request@eda-stds.org.
>> |
>> |IBIS reflector archives exist under:
>> |
>> |  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
>> | http://www.eda-stds.org/pub/ibis/users_archive/ Recent
>> |  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993
>>

- -- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

- --------------------------------------------------------------------
|For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
|with the appropriate command message(s) in the body:
|
|  help
|  subscribe   ibis       <optional e-mail address, if different>
|  subscribe   ibis-users <optional e-mail address, if different>
|  unsubscribe ibis       <optional e-mail address, if different>
|  unsubscribe ibis-users <optional e-mail address, if different>
|
|or e-mail a request to ibis-request@eda-stds.org.
|
|IBIS reflector archives exist under:
|
|  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/users_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993

- -- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

- --------------------------------------------------------------------
|For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
|with the appropriate command message(s) in the body:
|
|  help
|  subscribe   ibis       <optional e-mail address, if different>
|  subscribe   ibis-users <optional e-mail address, if different>
|  unsubscribe ibis       <optional e-mail address, if different>
|  unsubscribe ibis-users <optional e-mail address, if different>
|
|or e-mail a request to ibis-request@eda-stds.org.
|
|IBIS reflector archives exist under:
|
|  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/users_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993

------------------------------

Date: Tue, 31 May 2011 23:42:33 -0700
From: "Brad Brim" <bradb@sigrity.com>
Subject: RE: [IBIS-Users] IBIS ver5.0 [composite current] and [ISSO PU/PD]

This is a multi-part message in MIME format.

- ------=_NextPart_000_0138_01CC1FEC.6AB8A350
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

hello Yuancheng,
 
there will be a talk at the upcoming DAC IBIS forum that may be of interest
to you.
In summary, the BIRD-95/98 power-aware IBIS features work surprisingly well
to match the balance of pwr/gnd/signal currents you observe in
transistor-level models.
To apply power-aware IBIS models you will need both a
transistor-to-behavioral model translator as well as a circuit simulator
than can each apply IBIS 5.0 compliant models. Both are available
commercially, though not yet common.
 
cheers,
 -Brad
 
 
For reference you might want to see
http://www.eda.org/ibis/summits/may11/wolff.pdf
 
Also, coming up will be
IBIS SUMMIT MEETING, DAC, San Diego, CA, USA
Tuesday, June 7, 2011
9:00 AM IBIS PDN Feature Simulation Studies
Randy Wolff, Micron
Lance Wang, IO Methodology
 
 

  _____  

From: owner-ibis-users@eda.org [mailto:owner-ibis-users@eda.org] On Behalf
Of ji xiao
Sent: Tuesday, May 31, 2011 11:20 PM
To: ibis-users
Subject: [IBIS-Users] IBIS ver5.0 [composite current] and [ISSO PU/PD]


Dear all,
As I know, for solving the SSN problem, IBIS version 5.0 adds section
[composite current] and [ISSO PU/PD]. Then I have some questions:
1. How will the simulator work with the [composite current]? Does it
directly adopt the power terminal current value at the [composite current]
when the input voltage over the threshold voltage? But I feel different
rise/fall time will lead to different current value at the power terminal.
 
2. The section [ISSO PU/PD] is likely to provide a gate modulation
coefficent on the original output current. In specification, the
Ipu=Kpu(t)*Ipu(Vcc-Vout(t))*Ksso_pu(Vtable_pu) and
Ipd=Kpd(t)*Ipd(Vout(t))*Ksso_pd(Vtabke_pd). so does it mean the total output
current is Ipu+Ipd? how does the simulator decide the value of Kpu(t) and
Kpd(t) according to the data in IBIS file?
 
Thanks and regards,
 
Yuancheng

- -- 
This message has been scanned for viruses and 
dangerous content by  <http://www.mailscanner.info/> MailScanner, and is 
believed to be clean. 


- -- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


- ------=_NextPart_000_0138_01CC1FEC.6AB8A350
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dus-ascii" http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18928"></HEAD>
<BODY>
<DIV><SPAN class=3D669143006-01062011><FONT color=3D#0000ff size=3D2 face=
=3DArial>hello=20
Yuancheng,</FONT></SPAN></DIV>
<DIV><SPAN class=3D669143006-01062011><FONT color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D669143006-01062011><FONT color=3D#0000ff size=3D2 face=
=3DArial>there=20
will be a talk at the upcoming DAC IBIS forum that may be of interest to=20
you.</FONT></SPAN></DIV>
<DIV><SPAN class=3D669143006-01062011><FONT color=3D#0000ff size=3D2 face=
=3DArial>In=20
summary, the BIRD-95/98 power-aware IBIS features work surprisingly well to=
=20
match the balance of pwr/gnd/signal currents you observe in transistor-leve=
l=20
models.</FONT></SPAN></DIV>
<DIV><SPAN class=3D669143006-01062011><FONT color=3D#0000ff size=3D2 face=
=3DArial>To=20
apply power-aware IBIS models you will need both a transistor-to-behavioral=
=20
model translator as well as a circuit simulator than can each apply IBIS 5.=
0=20
compliant models. Both are available commercially, though not yet=20
common.</FONT></SPAN></DIV>
<DIV><SPAN class=3D669143006-01062011><FONT color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D669143006-01062011><FONT color=3D#0000ff size=3D2=20
face=3DArial>cheers,</FONT></SPAN></DIV>
<DIV><SPAN class=3D669143006-01062011><FONT color=3D#0000ff size=3D2=20
face=3DArial>&nbsp;-Brad</FONT></SPAN></DIV>
<DIV><SPAN class=3D669143006-01062011><FONT color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D669143006-01062011><FONT color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D669143006-01062011><FONT color=3D#0000ff size=3D2 face=
=3DArial>For=20
reference you might want to see <A=20
href=3D"http://www.eda.org/ibis/summits/may11/wolff.pdf">http://www.eda.org=
/ibis/summits/may11/wolff.pdf</A></FONT></SPAN></DIV>
<DIV><SPAN class=3D669143006-01062011><FONT color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D669143006-01062011><FONT color=3D#0000ff size=3D2 face=
=3DArial>Also,=20
coming up will be<BR></FONT></SPAN><SPAN class=3D669143006-01062011><SPAN=
=20
lang=3DEN>IBIS SUMMIT MEETING, DAC, San Diego, CA, USA<BR>Tuesday, June 7,=
=20
2011<BR>9:00 AM IBIS PDN Feature Simulation Studies<BR>Randy Wolff,=20
Micron<BR>Lance Wang, IO Methodology</SPAN></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5p=
x; MARGIN-RIGHT: 0px">
  <DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT size=3D2 face=3DTahoma><B>From:</B> owner-ibis-users@eda.org=20
  [mailto:owner-ibis-users@eda.org] <B>On Behalf Of </B>ji xiao<BR><B>Sent:=
</B>=20
  Tuesday, May 31, 2011 11:20 PM<BR><B>To:</B> ibis-users<BR><B>Subject:</B=
>=20
  [IBIS-Users] IBIS ver5.0 [composite current] and [ISSO=20
  PU/PD]<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV>Dear all,</DIV>
  <DIV>As I know, for solving the SSN problem, IBIS version 5.0 adds sectio=
n=20
  [composite current] and [ISSO PU/PD]. Then I have some questions:</DIV>
  <DIV>1. How will the simulator work with the [composite current]? Does it=
=20
  directly adopt the power terminal current value at the [composite current=
]=20
  when the input voltage over the threshold voltage? But I feel different=
=20
  rise/fall time will lead to different current value at the power=20
  terminal.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>2. The section [ISSO PU/PD] is likely to provide a gate modulation=
=20
  coefficent on the original output current. In specification, the=20
  Ipu=3DKpu(t)*Ipu(Vcc-Vout(t))*Ksso_pu(Vtable_pu) and=20
  Ipd=3DKpd(t)*Ipd(Vout(t))*Ksso_pd(Vtabke_pd). so does it mean the total o=
utput=20
  current is Ipu+Ipd? how does the simulator decide the value of Kpu(t) and=
=20
  Kpd(t) according to the data in IBIS file?</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Thanks and regards,</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Yuancheng</DIV><BR>-- <BR>This message has been scanned for viruses =
and=20
  <BR>dangerous content by <A=20
  href=3D"http://www.mailscanner.info/"><B>MailScanner</B></A>, and is=20
  <BR>believed to be clean. </BLOCKQUOTE><br />--=20
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href=3D"http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</BODY></HTML>

- ------=_NextPart_000_0138_01CC1FEC.6AB8A350--

- --------------------------------------------------------------------
|For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
|with the appropriate command message(s) in the body:
|
|  help
|  subscribe   ibis       <optional e-mail address, if different>
|  subscribe   ibis-users <optional e-mail address, if different>
|  unsubscribe ibis       <optional e-mail address, if different>
|  unsubscribe ibis-users <optional e-mail address, if different>
|
|or e-mail a request to ibis-request@eda-stds.org.
|
|IBIS reflector archives exist under:
|
|  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/users_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993

------------------------------

Date: Tue, 31 May 2011 22:53:17 -0700
From: "Brad Brim" <bradb@sigrity.com>
Subject: RE: [IBIS-Users] Requesting for some help / information regarding the use of IBIS in SI simulation.

hello Scott,

I don't agree with you. Such simulators (or model extractors which write out
such "postprocessed" model data) are no more assured accurate than simply
applying or writing out the base RLC data.

Most package extractors, especially ones you may refer to as applicable
"from the beginning", are based on static RLC simulation in which a single L
and C are extracted at exactly DC from two distinct simulations;
magnetostatic and electrostatic respectively. One has NO CLUE how to form
the equivalent circuit given only the static lumped L and C computed
independently. Of course, as asked and discussed by Ray, if the user has
insight from the physical structure then a more broadband model MIGHT be
generated, but there is no guarantee!
One person assuming a PI circuit (with the C split equally in half - or even
unequally - and the L in the middle) and another person assuming a TEE
circuit (with the L split and the shunt C in the middle) are no more correct
than the other. One has NO IDEA of the high frequency behavior of the
circuit (either just above the quasistatic limit where the likely spectral
content is relevant or higher where it is less likely relevant) without some
form of AC high-frequency simulation or measurement. The behavior at
"infinite" frequency in meaningless and to argue that a uniformly
distributed multi-stage ladder network is valid has no more justification
than another person arguing it should me a lowpass network with all the
inductance on the die side because of wirebond inductance. This argument has
blindly been accepted and argued for many years. It has been unjustified and
wrong, as you would say, "from the beginning".

Want a valid model at higher frequencies, then extract AC information from
which to generate it. One's guess or intuitive argument without AC
information to back it up is only a guess, as Andy stated. The classical
uniformly distributed ladder network is a deceptively simple and intuitively
pleasing assumption that is easy to understand and unfortunately accepted by
way too many people in the industry. This supposed more accurate guess has
failed in too many cases and can even be worse than a simple totally
unbalanced low pass filter assumption over the frequency spectrum of
relevance.

Many commercially available RLC extractors continue to make this assumption
today. Users are placed at significant risk because they falsely believe the
model is in some sense "broadband" or "wideband". It is a guess with no
guarantee to be any better than any other assumed more distributed
equivalent circuit for which there is no theoretical or physical
justification.

If one starts with AC data, assumes an equivalent circuit and *then* selects
element values in such to fit the data then there is reason to argue this is
a more valid model at higher frequencies. One cannot do this from only DC
terminal-based data. Not that it's difficult, it is impossible.

best regards,
 -Brad


> -----Original Message-----
> From: owner-ibis-users@eda.org 
> [mailto:owner-ibis-users@eda.org] On Behalf Of Scott McMorrow
> Sent: Tuesday, May 31, 2011 5:04 PM
> To: Ray Anderson
> Cc: ibis-users; Ray Anderson
> Subject: Re: [IBIS-Users] Requesting for some help / 
> information regarding the use of IBIS in SI simulation.
> 
> Since the beginning of IBIS, the most accurate simulators 
> would turn the RLC package parasitics into a transmission 
> line equivalent.  In lieu of any additional information it is 
> the most reasonable thing to do, since packages can be 
> approximated as transmission lines.
> 
> 
> Scott McMorrow
> Teraspeed Consulting Group LLC
> 121 North River Drive
> Narragansett, RI 02882
> (401) 284-1827 Business
> (401) 284-1840 Fax
> 
> http://www.teraspeed.com
> 
> TeraspeedR is the registered service mark of Teraspeed 
> Consulting Group LLC
> 
> 
> On 5/31/2011 7:59 PM, Ray Anderson wrote:
> > If you are using extracted RLC data to manually set up the package 
> > model you can certainly make intelligent decisions on the 
> topology of 
> > the model and the distribution of the RLC parasitics. 
> However if you 
> > are depending on a simulator to read the data from a IBIS 
> .pkg format 
> > file (or the [PIN] data) and set up a model for you then 
> your results 
> > may differ from simulator to simulator.
> >
> > -Ray
> > Xilinx Inc.
> >
> >
> > -----Original Message-----
> > From: owner-ibis-users@eda.org [mailto:owner-ibis-users@eda.org] On 
> > Behalf Of Andrew Ingraham
> > Sent: Tuesday, May 31, 2011 4:48 PM
> > To: ibis-users
> > Subject: Re: [IBIS-Users] Requesting for some help / information 
> > regarding the use of IBIS in SI simulation.
> >
> > Yes.
> >
> > I am usually tempted to start with an evenly distributed 
> RLC model ...
> > unless I have reason to think that the distribution is 
> otherwise.  For 
> > example, wirebonds might have most of the inductance and 
> resistance, 
> > whereas the leadframe may have more capacitance, which 
> might influence 
> > one to imbalance those factors unequally between die end 
> and pin end.
> > But without hard data to back it up, that is just guessing.
> >
> > Andy
> >
> 
> --
> This message has been scanned for viruses and dangerous 
> content by MailScanner, and is believed to be clean.
> 
> --------------------------------------------------------------------
> |For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org 
> |with the appropriate command message(s) in the body:
> |
> |  help
> |  subscribe   ibis       <optional e-mail address, if different>
> |  subscribe   ibis-users <optional e-mail address, if different>
> |  unsubscribe ibis       <optional e-mail address, if different>
> |  unsubscribe ibis-users <optional e-mail address, if different>
> |
> |or e-mail a request to ibis-request@eda-stds.org.
> |
> |IBIS reflector archives exist under:
> |
> |  http://www.eda-stds.org/pub/ibis/email_archive/ Recent  
> | http://www.eda-stds.org/pub/ibis/users_archive/ Recent
> |  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993
> 


- -- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

- --------------------------------------------------------------------
|For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
|with the appropriate command message(s) in the body:
|
|  help
|  subscribe   ibis       <optional e-mail address, if different>
|  subscribe   ibis-users <optional e-mail address, if different>
|  unsubscribe ibis       <optional e-mail address, if different>
|  unsubscribe ibis-users <optional e-mail address, if different>
|
|or e-mail a request to ibis-request@eda-stds.org.
|
|IBIS reflector archives exist under:
|
|  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/users_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993

------------------------------

Date: Wed, 01 Jun 2011 09:33:05 -0400
From: Scott McMorrow <scott@teraspeed.com>
Subject: Re: [IBIS-Users] Requesting for some help / information regarding the use of IBIS in SI simulation.

Brad

It is certainly your prerogative to disagree with me.  In the context of 
the original question, we are not talking about randomly distributed 
RLC, but rather package connections from board to silicon, which is the 
case in most IBIS models.  Given that, we know the general topology.  
Whether the package uses lead frame, 2 layer FC packaging, 2/4 layer 
organic wire bond packaging, or multilayer buildup packaging, a single 
path from die to ball looks remarkably similar to cascaded transmission 
lines.  Even bond wires look like transmission lines.

If I'm given a single RLC for an IBIS model of a conventionally packaged 
silicon device , then I can guarantee you that the simulation will be 
more faithful to measurements when the transmission line equivalent is 
used, rather than lumped elements.  Been there, done the measurements 
many, many times.  When multiple sections are specified in the IBIS .pkg 
format, then there is no ambiguity, a non-zero RLC section length 
defines a distributed element, and a zero length section defines a 
lumped element.  The simulator should model it as such.

Having done correlation of package modeling to measurements from DC to 
40 GHz on a 12-layer build-up with near zero error, I'm well aware of 
the issues involved with using the wrong modeling method, and poor 
material modeling.  I agree with you that a single RLC is an extremely 
poor approximation of any complex package interconnect, or any 
interconnect for that matter.  However, given that a user is presented 
with an RLC that was extracted with a quasi-static solver, as is the 
case with most IBIS models, I maintain that the result will be closer to 
reality when transformed into the distributed transmission line 
equivalent.  I've seen way too many cases where simulators used a lumped 
RLC directly, grossly over predicting  ringing at the die and in the 
channel, and confirmed by physical measurements.

When we get into full-wave and hybrid full-wave AC modeling of packages 
there are a host of other issues that we can discuss, such as accurate 
dielectric modeling, accurate surface roughness modeling, as-designed 
vs. as-built package geometries, +/- 15% impedance variation due to 
manufacturing process  and electromagnetic non-locality.  But that is 
for another time.


best regards,

Scott


Scott McMorrow
Teraspeed Consulting Group LLC
121 North River Drive
Narragansett, RI 02882
(401) 284-1827 Business
(401) 284-1840 Fax

http://www.teraspeed.com

Teraspeed® is the registered service mark of
Teraspeed Consulting Group LLC


On 6/1/2011 1:53 AM, Brad Brim wrote:
> hello Scott,
>
> I don't agree with you. Such simulators (or model extractors which write out
> such "postprocessed" model data) are no more assured accurate than simply
> applying or writing out the base RLC data.
>
> Most package extractors, especially ones you may refer to as applicable
> "from the beginning", are based on static RLC simulation in which a single L
> and C are extracted at exactly DC from two distinct simulations;
> magnetostatic and electrostatic respectively. One has NO CLUE how to form
> the equivalent circuit given only the static lumped L and C computed
> independently. Of course, as asked and discussed by Ray, if the user has
> insight from the physical structure then a more broadband model MIGHT be
> generated, but there is no guarantee!
> One person assuming a PI circuit (with the C split equally in half - or even
> unequally - and the L in the middle) and another person assuming a TEE
> circuit (with the L split and the shunt C in the middle) are no more correct
> than the other. One has NO IDEA of the high frequency behavior of the
> circuit (either just above the quasistatic limit where the likely spectral
> content is relevant or higher where it is less likely relevant) without some
> form of AC high-frequency simulation or measurement. The behavior at
> "infinite" frequency in meaningless and to argue that a uniformly
> distributed multi-stage ladder network is valid has no more justification
> than another person arguing it should me a lowpass network with all the
> inductance on the die side because of wirebond inductance. This argument has
> blindly been accepted and argued for many years. It has been unjustified and
> wrong, as you would say, "from the beginning".
>
> Want a valid model at higher frequencies, then extract AC information from
> which to generate it. One's guess or intuitive argument without AC
> information to back it up is only a guess, as Andy stated. The classical
> uniformly distributed ladder network is a deceptively simple and intuitively
> pleasing assumption that is easy to understand and unfortunately accepted by
> way too many people in the industry. This supposed more accurate guess has
> failed in too many cases and can even be worse than a simple totally
> unbalanced low pass filter assumption over the frequency spectrum of
> relevance.
>
> Many commercially available RLC extractors continue to make this assumption
> today. Users are placed at significant risk because they falsely believe the
> model is in some sense "broadband" or "wideband". It is a guess with no
> guarantee to be any better than any other assumed more distributed
> equivalent circuit for which there is no theoretical or physical
> justification.
>
> If one starts with AC data, assumes an equivalent circuit and *then* selects
> element values in such to fit the data then there is reason to argue this is
> a more valid model at higher frequencies. One cannot do this from only DC
> terminal-based data. Not that it's difficult, it is impossible.
>
> best regards,
>   -Brad
>
>
>> -----Original Message-----
>> From: owner-ibis-users@eda.org
>> [mailto:owner-ibis-users@eda.org] On Behalf Of Scott McMorrow
>> Sent: Tuesday, May 31, 2011 5:04 PM
>> To: Ray Anderson
>> Cc: ibis-users; Ray Anderson
>> Subject: Re: [IBIS-Users] Requesting for some help /
>> information regarding the use of IBIS in SI simulation.
>>
>> Since the beginning of IBIS, the most accurate simulators
>> would turn the RLC package parasitics into a transmission
>> line equivalent.  In lieu of any additional information it is
>> the most reasonable thing to do, since packages can be
>> approximated as transmission lines.
>>
>>
>> Scott McMorrow
>> Teraspeed Consulting Group LLC
>> 121 North River Drive
>> Narragansett, RI 02882
>> (401) 284-1827 Business
>> (401) 284-1840 Fax
>>
>> http://www.teraspeed.com
>>
>> TeraspeedR is the registered service mark of Teraspeed
>> Consulting Group LLC
>>
>>
>> On 5/31/2011 7:59 PM, Ray Anderson wrote:
>>> If you are using extracted RLC data to manually set up the package
>>> model you can certainly make intelligent decisions on the
>> topology of
>>> the model and the distribution of the RLC parasitics.
>> However if you
>>> are depending on a simulator to read the data from a IBIS
>> .pkg format
>>> file (or the [PIN] data) and set up a model for you then
>> your results
>>> may differ from simulator to simulator.
>>>
>>> -Ray
>>> Xilinx Inc.
>>>
>>>
>>> -----Original Message-----
>>> From: owner-ibis-users@eda.org [mailto:owner-ibis-users@eda.org] On
>>> Behalf Of Andrew Ingraham
>>> Sent: Tuesday, May 31, 2011 4:48 PM
>>> To: ibis-users
>>> Subject: Re: [IBIS-Users] Requesting for some help / information
>>> regarding the use of IBIS in SI simulation.
>>>
>>> Yes.
>>>
>>> I am usually tempted to start with an evenly distributed
>> RLC model ...
>>> unless I have reason to think that the distribution is
>> otherwise.  For
>>> example, wirebonds might have most of the inductance and
>> resistance,
>>> whereas the leadframe may have more capacitance, which
>> might influence
>>> one to imbalance those factors unequally between die end
>> and pin end.
>>> But without hard data to back it up, that is just guessing.
>>>
>>> Andy
>>>
>> --
>> This message has been scanned for viruses and dangerous
>> content by MailScanner, and is believed to be clean.
>>
>> --------------------------------------------------------------------
>> |For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
>> |with the appropriate command message(s) in the body:
>> |
>> |  help
>> |  subscribe   ibis<optional e-mail address, if different>
>> |  subscribe   ibis-users<optional e-mail address, if different>
>> |  unsubscribe ibis<optional e-mail address, if different>
>> |  unsubscribe ibis-users<optional e-mail address, if different>
>> |
>> |or e-mail a request to ibis-request@eda-stds.org.
>> |
>> |IBIS reflector archives exist under:
>> |
>> |  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
>> | http://www.eda-stds.org/pub/ibis/users_archive/ Recent
>> |  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993
>>

- -- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

- --------------------------------------------------------------------
|For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
|with the appropriate command message(s) in the body:
|
|  help
|  subscribe   ibis       <optional e-mail address, if different>
|  subscribe   ibis-users <optional e-mail address, if different>
|  unsubscribe ibis       <optional e-mail address, if different>
|  unsubscribe ibis-users <optional e-mail address, if different>
|
|or e-mail a request to ibis-request@eda-stds.org.
|
|IBIS reflector archives exist under:
|
|  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/users_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993

------------------------------

Date: Fri, 10 Jun 2011 12:30:07 +0530
From: "Ghatawade, Vinayak" <vinayak@ti.com>
Subject: [IBIS-Users] IV clamp range

- --_000_B85A65D85D7EB246BE421B3FB0FBB593024D42652Ddbde02enttico_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,

I have question reagarding the IV sweep ranges used for IBIS IV table gener=
ation.
Cookbook does not have detailed sweep range for all corners specified expli=
citly.
The reason that I am asking this question is we have IV table which has cro=
ss-overs for nom, strong and weak corners.
In spice I see this behavior which is expected as per diode behavior since =
the corners are temp variable as well.
Weak will turn on (125c) first and then followed by nom (25) and strong (-4=
0c). This results in the crossover.
Some customers are not willing to have these crossover (not sure why?). But=
 I feel since this is real behavior you should see the same
reflected in the ibis model.

Do you see a reason why IV crossovers are not allowed (recommended). I did =
not see any checklist or parser giving out any warning /error due this this.

Going back to the sweep voltage range when I see this crossover in spice (I=
 sweep voltages as mentioned in cookbook) and report the strong, weak to fi=
t in the
typical range voltage axis in the ibis model.

Ex 1.8V IO below is the numbers that I use for IV sweep range.

Sweep range that I use for typ
- -1.8 to 3.6

Min/weak will be
- -1.962 to 3.428

Max/strong will be
- -1.602 to 3.798


Thanks
vinayak


- --=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


- --_000_B85A65D85D7EB246BE421B3FB0FBB593024D42652Ddbde02enttico_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
p.listparagraph, li.listparagraph, div.listparagraph
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
- -->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Hello,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>I have question reagarding the IV sweep
ranges used for IBIS IV table generation. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Cookbook does not have detailed sweep
range for all corners specified explicitly.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>The reason that I am asking this quest=
ion
is we have IV table which has cross-overs for nom, strong and weak corners.=
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>In spice I see this behavior which is
expected as per diode behavior since the corners are temp variable as well.=
 <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Weak will turn on (125c) first and then
followed by nom (25) and strong (-40c). This results in the crossover. <o:p=
></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Some customers are not willing to have
these crossover (not sure why?). But I feel since this is real behavior you
should see the same <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>reflected in the ibis model.<o:p></o:p=
></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Do you see a reason why IV crossovers =
are
not allowed (recommended). I did not see any checklist or parser giving out=
 any
warning /error due this this.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Going back to the sweep voltage range =
when
I see this crossover in spice (I sweep voltages as mentioned in cookbook) a=
nd
report the strong, weak to fit in the <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>typical range voltage axis in the ibis
model.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Ex 1.8V IO below is the numbers that I=
 use
for IV sweep range.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Sweep range that I use for typ <o:p></=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>-1.8 to 3.6 <o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Min/weak will be <o:p></o:p></span></f=
ont></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>-1.962 to 3.428 <o:p></o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Max/strong will be <o:p></o:p></span><=
/font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>-1.602 to 3.798<o:p></o:p></span></fon=
t></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Thanks <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:blue'>vinayak</span></font><font color=3Dblu=
e><span
style=3D'color:blue'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<br />--=20
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href=3D"http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body>

</html>

- --_000_B85A65D85D7EB246BE421B3FB0FBB593024D42652Ddbde02enttico_--
- --------------------------------------------------------------------
|For help or to subscribe/unsubscribe, e-mail majordomo@eda-stds.org
|with the appropriate command message(s) in the body:
|
|  help
|  subscribe   ibis       <optional e-mail address, if different>
|  subscribe   ibis-users <optional e-mail address, if different>
|  unsubscribe ibis       <optional e-mail address, if different>
|  unsubscribe ibis-users <optional e-mail address, if different>
|
|or e-mail a request to ibis-request@eda-stds.org.
|
|IBIS reflector archives exist under:
|
|  http://www.eda-stds.org/pub/ibis/email_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/users_archive/ Recent
|  http://www.eda-stds.org/pub/ibis/email/         E-mail since 1993

------------------------------

End of ibis-users V1 #175
*************************

