Re[2]: [SI-LIST] : How to identify SSO

Arpad Muranyi (Arpad_Muranyi@ccm.fm.intel.com)
Wed, 14 Jan 98 03:04:00 PST

Text item:

The statement below is not true for all vendors. As far as I know, our specs
are valid at the pin (not the unpackaged die-pad) and they also include the
on-the-die SSO effects. (Of course we also supply IBIS models for our chips).

Arpad Muranyi
Intel Corporation
==============================================================================

Andy,

Vendors' data reflects buffers in non-packaged environment without
taking the SSO into account. For smart users, vendors sometimes supply IBIS
models for simulations. For "smart" users, vendors give the step_B option...

And... ... ... do not forget the reliability issue when a bus is switching
on a low voltage (0.25u/0/18u) process and the transients from the inductance
miht hurt oxide...

Regards, yehuda

>
> D. C. Sessions wrote:
>
> > What causes ME to sweat nights is the fact that SSO causes driver
> > starvation. For the last couple of years it's the largest single
> > term in our clock-to-output timing.
>
> Since the tradition is to specify delays and timing with one output
> switching at a time, how accurate do you suppose vendor's data
> sheets are, these days?
>
> Regards,
> Andy
>

--

+++++++++++++++++++++++++++++++++ + + + Yehuda D. Yizraeli + + + + Zoran Microelectronics LTD. + + P.O.Box 2495 + + Advanced Technology Center + + Haifa , Israel 31024 + + + + Tel: +972-485-45777 + + Tel: 04-854-5777 + + Fax: +972-485-51550 + + + + E-mail: yehuda@zoran.co.il + + + + http://www.zoran.com + + + +++++++++++++++++++++++++++++++++

Text item: External Message Header

The following mail header is for administrative use and may be ignored unless there are problems.

***IF THERE ARE PROBLEMS SAVE THESE HEADERS***.

Precedence: bulk Sender: owner-si-list@silab.Eng.Sun.COM Content-Type: text X-Mailer: ELM [version 2.4 PL20] Organization: Zoran Microelectronics LTD Reply-To: yehuda@zoran.co.il From: "Yehuda D. Yizraeli" <yehuda@zoran.co.il> In-Reply-To: <9801120312.AA21483@us8rmc.bb.dec.com> from "Andrew Ingraham" at Ja n 11, 98 10:12:52 pm Cc: si-list@silab.Eng.Sun.COM, ingraham@wrksys.ENET.dec.com Date: Mon, 12 Jan 1998 07:27:47 +0200 (EET) To: ingraham@wrksys.ENET.dec.com (Andrew Ingraham) Subject: Re: [SI-LIST] : How to identify SSO Message-Id: <199801120527.HAA13690@en51> Received: by en51 (SMI-8.6/Spike-2.0-Alx) id HAA13690; Mon, 12 Jan 1998 07:27:47 +0200 Received: from en51 (en51.zoran.co.il [199.203.69.51]) by ca41.zoran.co.il (8.8. 5/8.7.3) with SMTP id HAA11330; Mon, 12 Jan 1998 07:25:13 +0200 (IST) Received: from ca41.zoran.co.il ([199.203.69.11]) by saturn.sun.com (8.8.8/8.8.8) with ESMTP id VAA23213 for <si-list@silab.Eng.Sun.COM>; Sun, 11 Jan 1998 21:21:50 -0800 (PST) Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2]) by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id VAA21985 for <si-list@silab.Eng.Sun.COM>; Sun, 11 Jan 1998 21:21:15 -0800 Received: from Eng.Sun.COM by silab.eng.sun.com (SMI-8.6/SMI-SVR4) id VAA24244; Sun, 11 Jan 1998 21:22:40 -0800 Errors-To: si-list-approval@silab.Eng.Sun.COM Received: by silab.eng.sun.com (SMI-8.6/SMI-SVR4) id VAA24248; Sun, 11 Jan 1998 21:22:46 -0800 Received: from silab.eng.sun.com (silab.Eng.Sun.COM [129.146.121.121]) by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id VAA23220; Sun, 11 Jan 1998 21:37:01 -0800 Received: from Eng.Sun.COM ([129.146.1.13]) by mercury.Sun.COM (SMI-8.6/mail.bya ddr) with SMTP id VAA12450; Sun, 11 Jan 1998 21:37:07 -0800 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by thalia.fm.intel.com (8.8.6/8.8.5) with SMTP id VAA03676; Sun, 11 Jan 1998 21:52:05 -0800 (PST) Received: from thalia.fm.intel.com (thalia.fm.intel.com [132.233.247.11]) by fmm ail.fm.intel.com (8.8.5/8.7.3) with ESMTP id VAA08584; Sun, 11 Jan 1998 21:49:59 -0800 (PST) Return-Path: owner-si-list@silab.Eng.Sun.COM