If your edge rate is less then 5% of your cycle time the fast edge creates
more problems than benefits. I have been lucky and work side by side with
ASIC I/O cell designers. We look at early versions of cells (spice models)
and determine compatibility with the board environment. We sometimes make
recommendations and fight for new cell versions when applicable. With
reduced cycle times and tighter product schedules, higher ASIC pinout,
higher di/dt's and in general noisier board environments, it is imperative
to optimize I/O cell edge rates. When selecting jelly beans this is a
critical area. I would also recommend spending time in the lab breadboarding
and/or building test chips to prevent painful months in the lab with a scope
probe in your hands.
Depending on what you are designing, you eventually will reach the point
where whole board simulations are necessary. We have been doing it for some
time and it helps prevent many issues/problems that can creep into a design.
But whole board analysis is no substitute for good up front SI what if
I also agree with D.C. and think we should blow up the ancient carving of
the 50 pf standard load on that cave wall. :-)
just my $0.02
Robert J. Haller
Compaq Computer Corporation
AlphaServer Product Development
Phone: (978) 493-4112
Fax: (978) 493-0941
From: Roy Leventhal [mailto:Roy_Leventhal@mw.3com.com]
Sent: Friday, July 16, 1999 9:36 AM
Subject: RE: [SI-LIST] : response to semiconductor I/O edge rates
The simple answer is that this is a big, proprietary development ASIC. The
designer never had any intention that it should have such a fast edge rate.
a matter of prudent checking he had me check the signal integrity once we
the IBIS model and partially routed board. That's when we discovered that
edge rate was so fast. The semiconductor house had never given us a heads-up
that the edge rate was likely to be so fast. Or so I understand it. Now the
house is telling us they can't do anything about it.
It is possible that the circuit designer knew about the edge rate earlier
think and was hoping that some simulation or layout/routing magic pixy dust
would be sprinkled on his circuit. I don't think I'll ever know the answer
that. I do see wishful thinking about avoiding a conservative (expensive)
approach to design. Speeds are becoming such that those hopes are rarely
fulfilled anymore. Even reasonable engineering judgement isn't that great a
guide anymore and we are contemplating making whole-board simulations part
our design process.
The common approach to design is to avoid the unpleasant (in this case no
for termination networks or time for a new supplier) and end up with
the back end of a design where cost factors are multiplied by 10 to 1000 (or
even more) to fix. Once again, I don't know if this was a factor.
What I have learned is this: Simulation as a board is being routed is too
to find such problems. At that point they directly affect layout, schedules
the viability of the project. At that point simulation should just be a
(virtual) verification check of previous good design choices. Per D.C.
suggestion, simulation at the timing/topology choice stage with feedback to
supplier of a user modified/developed behavioral model to see if can be
is much timelier.
**** To unsubscribe from si-list: send e-mail to
email@example.com. In the BODY of message put: UNSUBSCRIBE
si-list, for more help, put HELP. si-list archives are accessible at
**** To unsubscribe from si-list: send e-mail to firstname.lastname@example.org. In the BODY of message put: UNSUBSCRIBE si-list, for more help, put HELP. si-list archives are accessible at http://www.qsl.net/wb6tpu/si-list ****