Subject: Re: [IBIS-Users] Using the '.ibis' (note the dot) in HSPICE
From: Mike LaBonte (mike@labonte.com)
Date: Tue Apr 09 2002 - 15:18:56 PDT
The actual node names don't matter, do they? You can name
them anything you want as long as the terminal positions are
correct in the B element call. It wouldn't be SPICE if the actual
names mattered.
I was wondering if Mike is using the power=off parameter, which
causes the power and ground terminal to be used to supply current
to the buffer. This has never worked for me, and I have yet to find
an example of a circuit that works that way.
Mike
At 05:12 PM 4/9/2002 -0400, Mark Bossard wrote:
>I would suggest checking out the Hspice Device Models Manual.
>It should be part of the normal Hspice electronic documentation package.
>It has a fair description and examples of using .ibis .
>
>The Device Models Manual tells you what the node names are (or should
>be).
>
>The names of the input and output nodes for the buffers are:
>INPUT and INPUT_ECL buffers signal name of pin ( in )
>bufn_<pin_number> ( outofin )
>Other types of buffers bufn_<pin_number> ( in ) signal name of pin (
>out )
>n <pin_number> is 1 if this pin is the first pin defined in the [Pin]
>keyword.
>n <pin_number> is 2 if this pin is the second pin. and so on.
>Note: If the buffer has an enable terminal, you must create a node named
>buffer_name_en to enable the buffer.
>
>Good Luck,
>
>Mark Bossard
>
>
>
>Michael Dotson wrote:
> >
> > I have spent the last 2 days puzzling over how to use the ' .ibis ' call in
> > hspice.
> > Using the basic ibis buffer works ok, but this other command was there to
> > try as well.
> >
> > The ibis device I have is a basic TS TTL buffering device that says it is
> > 2.1 compatible.
> >
> > When hspice runs I can see that it allocates a buffer to each input and
> > output pin.
> > However, the stim I put on the input pin does not get propagated to the
> > output pin.
> > I can see the input buffer switching a-ok, but the output buffer does not.
> > I have even tried different enable pin values to see if that had an effect.
> >
> > What seem to be missing is the 'hook' to drive the output buffers nd_in
> > port.
> > Actually, I do not even see a port named nd_in for the output buffers. I
> > can
> > see the pc and pd and en pins OK though.
> >
> > Can someone shed some light on my confusion?
> >
> > thanks,
> > Mike Dotson
> > IBM Endicott Worldwide Field Design Center 607-752-5379 (tl 852)
> >
|------------------------------------------------------------------
|For help or to subscribe/unsubscribe, email majordomo@eda.org
|with just 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 email a written request to ibis-request@eda.org.
|
|IBIS reflector archives exist under:
|
| http://www.eda.org/pub/ibis/email_archive/ Recent
| http://www.eda.org/pub/ibis/users_archive/ Recent
| http://www.eda.org/pub/ibis/email/ E-mail since 1993
This archive was generated by hypermail 2b28 : Tue Apr 09 2002 - 19:36:45 PDT