[SI-LIST] Re: Run Scheduled Drivers IBIS models on HSPICE 2001.4
- From: Linnenbruegger Dirk <Dirk.Linnenbruegger@xxxxxxxxxxxxxxxxxxx>
- To: "'tracyb@xxxxxxxxxxxxxx'" <tracyb@xxxxxxxxxxxxxx>,Michael.Chan@xxxxxxxxxx
- Date: Thu, 18 Apr 2002 09:48:17 +0200
Hi Michael,
I've had the same problems with the [DRIVER_SCHEDULE]
devices as you mentioned.
After I had a closer look to the IBIS file I found out=20
that the top level model is an I/O open drain buffer and=20
the scheduled drivers are open drain (MODEL1_N ) and=20
open source buffers (MODEL1_P).
When I use the following buffer syntax (all buffers use
the same nodelist -as Tracy mentioned-), Hspice always=20
aborts with:
****** Star-HSPICE -- 2001.4 **************************
b_BUFFER_io BUFFER_pu BUFFER_pd =20
+ BUFFER_out BUFFER_in =20
+ BUFFER_nd_en BUFFER_V_out_of_in =20
+ file =3D '../Lib/model1.ibs'
+ model =3D 'MODEL1'
+ buffer =3D 6 $ I/O open drain (top level model)
**error** Inconsisitent nodelist between the top and the=20
scheduled model where File =3D ../Lib/model1.ibs Model =3D MODEL1
My workaround to solve this problem is to change the buffer=20
type of the scheduled buffers in the IBIS file in the=20
following way:
[Model] MODEL1_N =20
Model_type open_drain -> I/O_open_drain
[Model] CPU_MID_MODEL1_P
Model_type open_source -> I/O_open_source
Maybe this will help you.
Dirk Linnenbruegger
Fujitsu Siemens Computers GmbH
> -----Urspr=FCngliche Nachricht-----
> Von: Tracy Barclay [mailto:tracyb@xxxxxxxxxxxxxx]
> Gesendet: Mittwoch, 17. April 2002 20:34
> An: Michael.Chan@xxxxxxxxxx
> Cc: si-list@xxxxxxxxxxxxx
> Betreff: [SI-LIST] Re: Run Scheduled Drivers IBIS models on HSPICE
> 2001.4
>=20
>=20
>=20
> Hi Michael,
>=20
> You do not have to add anything into your netlist in order for =
[Driver
> Schedule] to work. Hspice reads the [Driver Schedule] data and the
> corresponding 'scheduled' models from the IBIS file. In the=20
> IBIS file, the
> [Driver Schedule] data will look something like:
>=20
> [Driver Schedule]
> | Model_name Rise_on_dly Rise_off_dly Fall_on_dly Fall_off_dly
> CPU_N 0 NA
> 0 NA
> CPU_P 0.250ns 2.5ns NA =20
> NA
>=20
> In this example, the scheduled models are CPU_N and CPU_P. =20
> The models must
> be of the same model type as the top level model that these=20
> are scheduled
> for So, if the top level model is model type I/O, then both=20
> the scheduled
> models CPU_N and CPU_P must also be I/O buffers. If the=20
> scheduled buffers
> are not of the same model type as the top level buffer, you=20
> will get a error
> message, "Inconsistent nodelist between the top and the=20
> scheduled model" and
> Hspice will abort.
>=20
> The driver schedule implementation will be improved in the=20
> next release so
> that the scheduled models do not have to be the same model=20
> type as the top
> level model.
>=20
> Let me know if you have any other questions about this.
>=20
> Tracy Barclay
> Star-Hspice Product Specialist
> Avant! Corporation
>=20
> > Gurus:
> > I have a scheduled drivers IBIS model that I try=20
> to run on =3D
> > HSPICE 2001.4. HSPICE manual does not seems to have a=20
> nodelist format =3D
> > for=3D20
> > the scheduled drivesr IBIS model. Am I supposed to use the=20
> nodelist as a =3D
> > generic I/O buffer as described inside the manual or I have=20
> to use a=3D20
> > specific nodelist just for scheduled drivers ? I sent a request to =
=3D
> > AVANTI but no response so far. Thanks.
> >
> > Regards,
> > Michael Chan
> >
> > ------------------------------------------------------------------
> > To unsubscribe from si-list:
> > si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the=20
> 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 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
> >
>=20
> ------------------------------------------------------------------
> To unsubscribe from si-list:
> si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
>=20
> or to administer your membership from a web page, go to:
> //www.freelists.org/webpage/si-list
>=20
> For help:
> si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field
>=20
> 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=20
> Old (prior to June 6, 2001) list archives are viewable at:
> http://www.qsl.net/wb6tpu
> =20
>=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 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
Other related posts:
