Re: s2ibis2

Thanks to all who responded to my plea for enlightenment. Once I ran
hspice in stand alone mode on the deck that s2ibis2 created and kept the
.lis file, I was able to understand what was happening.

The problem was failure to converge due to excessive current in the nfet
and pfet models at the Ibis sweep extremes(-3.3 to +6.6 volts). I
reduced the sweep range and everything ran. Oh, I had to fix the "gnd"
node by calling it "mygnd", still tying it to node 0 in hspice. This was
for ex2 in the examples.

Is there anyway to limit the automatically generated sweep range in the
.s2i file?

This was with hspice 96.1. Solaris.

Mark Simpson wrote that the deck I attached ran fine in hspice 95.2,
SunOS.

Brock Hannibal wrote:
>
> Hi,
>
> I've been trying to run some of the examples in the v1.1 distribution of
> s2ibis2. I'm using Hspice.
> I'm admittedly not very familiar with Hspice since we have our own
> internal Spice. Unfortunately converinting hspice to our internal Spice
> is not an option at the moment.I get the following standard output:
>
> [salope:ex2]
> /proj/cae/brockh/data/icx/ibis/tools/s2ibis2/bin/s2ibis2.solaris
> tristate.s2i
>
> s2ibis2.solaris v1.1 -- North Carolina State University
> s2ibis2.solaris: Reading input file tristate...done.
> s2ibis2.solaris: Analyzing component MCM Trisate Driver .
> s2ibis2.solaris: Starting HSpice job with input putout.spi.
> s2ibis2.solaris: Spice run (TYP) aborted. See file putout.msg for
> information.
> Curve pullup not generated.
> s2ibis2.solaris: Starting HSpice job with input dutout.spi.
> s2ibis2.solaris: Spice run (TYP) aborted. See file dutout.msg for
> information.
> Curve pullup (output disabled) not generated.
>
> Any clue as to why the pullup and pulldown curves aren't generated. I
> looked in the putout.spi
> file and it looks OK to me but I'll attach it. The file putout.msg is
> very short and looks like
> this:
>
> ^G>error ***** hspice job aborted
>
> real 7.0
> user 0.5
> sys 0.2
>
> Thanks for any insight you may have. I've fiddled around quite a bit and
> am just not seeing the
> problem or oversight.

-- 
Brock Hannibal
Hardware Design Engineer
Tektronix, Inc.
Beaverton, Oregon
"Any ideas or opinions expressed here do not necessarily
       reflect the ideas or opinions of my employer."