RE: Overclocked driver schedule.

Al,

The few cases I've seen that use [driver_schedule] use the clock as the
timing key anyway. The comments in the file state the model is only
accurate at a certain clock frequency and the parameters need to be changed
in order to work at a different clock frequency. I would make the master
stimulus a real master and force drivers to follow it.

Later,
Weston

+ -----Original Message-----
+ From: Al Davis [mailto:aldavis@ieee.org]
+ Sent: Friday, August 11, 2000 12:07 AM
+ To: ibis-users@eda.org; ibis@eda.org
+ Subject: Overclocked driver schedule.
+
+
+ What is the correct behavior for a simulator when driver
+ schedule is overclocked?
+
+ Consider this ....
+
+ [Driver Schedule]
+ foo 3.5ps 5ns NA NA
+
+ .. this gives it an extra kick on a rising edge.
+
+ The question ...
+
+ What should happen when the device is triggered to fall 3ns
+ after the rise begins?
+
+ Some possibilities .....
+
+ 1. It waits another 2 ns (for the total of 5 ns) to turn
+ off?
+
+ 2. It turns off on the falling edge? as if the line was:
+ foo 3.5ps 5ns 0ns NA
+
+ 3. Other?
+
+
+ Should the standard be changed to clarify this?
+
Received on Mon Aug 14 13:12:43 2000