From: TING.STEVE@inventec.com.tw [mailto:TING.STEVE@inventec.com.tw]
Sent: Wednesday, 19 May, 1999 2:51 AM
Subject: RE: [SI-LIST] : Looking Inside IBIS Model
Thank you for your comment.
In my example, I try to express the idea:
The Tco_max was 2.5nS in my example, which was based on the same test
loading used to generate TIME_TO_VM.
And after Quad's mtest's calculation, I'll have TWO different values for
TIME_TO_VM: 0.8nS for rising and 1.8nS for falling.
I'll then think that the Tco_max must came from falling and the real Tco for
rising should be smaller than 2.5nS, maybe
around 1.5nS (I guess, because 1nS difference on TIME_TO_VM).
Then If I can have longer allowable flight time about 4nS (7.5-1.5-2.0=4.0)
purely for rising.
If it is true, the Tflight_rise of 3.1nS(<4.0nS) won't break my timing! Am I
By the way, I assume zero skew and jitter in my formula just for
simplication, I didn't mean I can really do that in practical.
And I won't do the TIME_TO_VM correction manually in my simulation, I'll
enable the VM correction function in Quad if I have
reliable TIME_TO_VM values in XTK models.
From: Beal, Weston [ mailto:Weston.Beal@COMPAQ.com
Sent: Wednesday, May 19, 1999 12:21 AM
**** 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 http://www.qsl.net/wb6tpu/si-list ****