I vote or recommend to use number 1) answer of the previous e-mail. Some companies are very responsive and some are not on this. IBIS models are supposed to open to everyone. It should not be too difficult to get and use it. Here I simply hope to confirm the background philosophy for "IBIS as opposed to SPICE". And... I believe the answer from your IC vendor won't be long:-) Cheers, Kihong Joshua Kim SI Engineer in Electronics and Photonics On 10/11/07, Powell, Jon N <jon.n.powell@xxxxxxxxx> wrote: > > It looks like they didn't specify any model for some of the differential > pins and just put an NC for a place holder. Depending on what you want > to simulate I would: > > 1) Ask the model vendor to fix the problem > 2) Get a differential model of similar nature from somewhere else and > put it in here. > 3) Remove the Diff Pin mappings (and don't expect to simulate those > pins). > > It does seem like the diff pin statements are what is causing the > error....... > > > > -----Original Message----- > From: si-list-bounce@xxxxxxxxxxxxx [mailto:si-list-bounce@xxxxxxxxxxxxx] > On Behalf Of Han Li > Sent: Thursday, October 11, 2007 5:40 AM > To: SI LIST > Subject: [SI-LIST] A ibis problem in Hyperlynx simulation > > Hi experts: > when i simulate BCM5421s with ibis model in hyperlynx, a error > occured:"Differential pin 116 is paired with a Nc pin in component > BCM5421s > of file E:\........" > I open the model, the differential pins are like this in ibis file: > 115 SGIN+ NC > 116 SGIN- NC > > 118 SGOUT+ NC > 119 SGOUT- NC > > 121 SCLK+ NC > 122 SCLK- NC > > |*********************************************************************** > * > [Diff Pin] inv_pin vdiff tdelay_typ > 115 116 100mV 0 > 118 119 0V 0 > 121 122 0V 0 > > > > but the analog differential pins are OK, they are: > 47 TRD[0]+ NC > 48 TRD[0]- NC > 49 TRD[1]- NC > 50 TRD[1]+ NC > > Could anyone provide some advices on fixing the problem? Thanks a lot. > > > ------------------------------------------------------------------ > To unsubscribe from si-list: > si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field > > or to administer your membership from a web page, go to: > //www.freelists.org/webpage/si-list > > For help: > si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field > > > List technical documents are available at: > http://www.si-list.net > > List archives are viewable at: =20 > //www.freelists.org/archives/si-list > or at our remote archives: > http://groups.yahoo.com/group/si-list/messages > Old (prior to June 6, 2001) list archives are viewable at: > http://www.qsl.net/wb6tpu > =20 > ------------------------------------------------------------------ > To unsubscribe from si-list: > si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field > > or to administer your membership from a web page, go to: > //www.freelists.org/webpage/si-list > > For help: > si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field > > > List technical documents are available at: > http://www.si-list.net > > List archives are viewable at: > //www.freelists.org/archives/si-list > or at our remote archives: > http://groups.yahoo.com/group/si-list/messages > Old (prior to June 6, 2001) list archives are viewable at: > http://www.qsl.net/wb6tpu > > > ------------------------------------------------------------------ To unsubscribe from si-list: si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field or to administer your membership from a web page, go to: //www.freelists.org/webpage/si-list For help: si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field List technical documents are available at: http://www.si-list.net List archives are viewable at: //www.freelists.org/archives/si-list or at our remote archives: http://groups.yahoo.com/group/si-list/messages Old (prior to June 6, 2001) list archives are viewable at: http://www.qsl.net/wb6tpu