Chris- If your simulator conforms to the IBIS standard, the model in the [Package] section (either inline or external) should supersede the data in the [Pin] section. -Ray Raymond Anderson Senior Signal Integrity Staff Engineer Programmable Platforms Development Silicon Technology Group Signal Integrity and Package Development Department Xilinx Inc. 2100 Logic Drive San Jose, California 95124 (408) 626-6277 > -----Original Message----- > From: si-list-bounce@xxxxxxxxxxxxx [mailto:si-list-bounce@xxxxxxxxxxxxx] > On Behalf Of Chris.McGrath@xxxxxxxx > Sent: Wednesday, January 14, 2009 11:48 AM > To: Seshadri Venkataramanan > Cc: si-list@xxxxxxxxxxxxx > Subject: [SI-LIST] Re: IBIS Model Using Package Model Error > > Seshadri, > I just tried appending the package model after "End [Component]" and > before "[End]". > > That seems to work since I now have zero errors. I'm still very curious > as to why I cannot reference a separate file. > > > Another question to the group: > If an IBIS model defines a Package Model does this supersede any lumped > element data in the R_pin, L_pin, and C_pin fields under [Pin]? > Or, is this dependent on the simulator? > > Thanks, > Chris > > > ------------------------------------------------------------------------ -- > --- > Chris McGrath > Applications Engineer - Mobile Technology Solutions > chris.mcgrath@xxxxxxxx > Office: 480.704.7061 > Blackberry: 480.747.3848 > www.smsc.com > ------------------------------------------------------------------------ -- > --- > > > > > > "Seshadri Venkataramanan" <jayanth.neo@xxxxxxxxx> > 01/14/2009 11:47 AM > > To > Chris McGrath/SMSC@SMSC > cc > > Subject > Re: [SI-LIST] Re: IBIS Model Using Package Model Error > > > > > > > Hi, > > I am sorry not to have known about that. But did you try including the > contents of the package file into your IBIS Model to see if that works? > > On Wed, Jan 14, 2009 at 11:43 AM, <Chris.McGrath@xxxxxxxx> wrote: > > I'm not sure if I agree with that. Here is the text from the IBIS spec, > version 4.0 which states that "If the matching package model is in an > external .pkg file, it must be located in the same directory as the .ibs > file". > > > |======================================================================= == > ==== > > | Keyword: [Package Model] > | Required: No > | Description: Indicates the name of the package model to be used for the > | component. > | Usage Rules: The package model name is limited to 40 characters. Spaces > | are allowed in the name. The name should include the company > | name or initials to help ensure uniqueness. The EDA tool > | will search for a matching package model name as an argument > | to a [Define Package Model] keyword in the current IBIS file > | first. If a match is not found, the EDA tool will next look > | for a match in an external .pkg file. If the matching package > | model is in an external .pkg file, it must be located in the > | same directory as the .ibs file. The file names of .pkg files > | must follow the rules for file names given in Section 3, > | GENERAL SYNTAX RULES AND GUIDELINES. > | Other Notes: Use the [Package Model] keyword within a [Component] to > | indicate which package model should be used for that > | component. The specification permits .ibs files to contain > | [Define Package Model] keywords as well. These are described > | in the "Package Modeling" section near the end of this > | specification. When package model definitions occur within a > | .ibs file, their scope is "local", i.e., they are known only > | within that .ibs file and no other. In addition, within that > | .ibs file, they override any globally defined package models > | that have the same name. > |----------------------------------------------------------------------- -- > ---- > > > > ------------------------------------------------------------------------ -- > --- > Chris McGrath > Applications Engineer - Mobile Technology Solutions > chris.mcgrath@xxxxxxxx > Office: 480.704.7061 > Blackberry: 480.747.3848 > www.smsc.com > ------------------------------------------------------------------------ -- > --- > > > > > "Seshadri Venkataramanan" <jayanth.neo@xxxxxxxxx> > Sent by: si-list-bounce@xxxxxxxxxxxxx > 01/14/2009 11:39 AM > > > To > Chris McGrath/SMSC@SMSC > cc > si-list@xxxxxxxxxxxxx > Subject > [SI-LIST] Re: IBIS Model Using Package Model Error > > > > > > > > > Hi, > Did you make sure that you included the contents of the package model in > your IBIS file? You have to include the contents of the package model in > to > your IBIS file before referencing it. It doenst look up the directory > where > you have the package file stored. Rather it searches in the IBIS file > itself. > > On Wed, Jan 14, 2009 at 11:26 AM, <Chris.McGrath@xxxxxxxx> wrote: > > > I'm creating an IBIS model that references a .pkg package model. While > I > > think that my syntax is correct, I'm failing the Committee Parser and I > > can't figure out why. Your help is greatly appreciated. > > Here is the error: > > ERROR - Unable to find Package Model 'device_package' for Component > > 'device' > > > > > > In my IBIS model (filename is "device.ibs"), here is my syntax > referencing > > the package file: > > [IBIS Ver] 4.0 > > [Comment char] |_char > > [File name] device.ibs > > [File Rev] 1.0 > > [Date] 14-JAN-2009 > > . > > . > > . > > [Component] device > > [Manufacturer] SMSC > > [Package Model] device_package > > > > > > > > Here is the .pkg syntax that I am using: > > [IBIS ver] 4.0 > > [File name] device.pkg > > [File Rev] 1.0 > > [Date] January 14, 2009 > > [Source] TBD > > [Notes] None > > [Disclaimer] TBD > > [Copyright] 2009 > > [Define Package Model] device_package > > > > > > > > I have both files in the same directory on my C drive. > > > > Any ideas why this is failing the Parser? > > > > Thanks, > > Chris > > > > > > > ------------------------------------------------------------------------ -- > --- > > Chris McGrath > > Applications Engineer - Mobile Technology Solutions > > chris.mcgrath@xxxxxxxx > > Office: 480.704.7061 > > Blackberry: 480.747.3848 > > www.smsc.com > > > > > ------------------------------------------------------------------------ -- > --- > > > > > > > > ------------------------------------------------------------------ > > 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 > > > > > > > > > -- > Seshadri Venkataramanan > > Graduate Student > MS - Electrical Engineering > ( Mixed Signal Circuit Design) / Student Design Intern. > Arizona State University/ NXP Semiconductors. > > Joe E. Lewis - "There's only one thing money won't buy, and that is > poverty." > > > ------------------------------------------------------------------ > 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 > > > > > > > -- > Seshadri Venkataramanan > > Graduate Student > MS - Electrical Engineering > ( Mixed Signal Circuit Design) / Student Design Intern. > Arizona State University/ NXP Semiconductors. > > Richard Dawkins - "By all means let's be open-minded, but not so > open-minded that our brains drop out." > > > ------------------------------------------------------------------ > 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 > > This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. ------------------------------------------------------------------ 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