Access to a clock counter

[ucb-bar]

Access to a clock counter

[ducky64]

So under the current single-clock semantics, such a counter is fairly straightforward, but under multiclock semantics with some notion of simulator time, it might become less clear.

For those, I was thinking:

• Probably have a way to inspect simulator time, defined in seconds
• Maybe have a way to count rising edges of clocks since the beginning of simulation, though this will need a treadle API (@chick ?) since not all clocks are necessarily under the user's control and testers2 may not be able to track everything. Note that we currently only track clocks that we know about (threads are blocked on), so rising-edges-since-beginning-of-simulation, while intuitive, might not be practical to implement. An alternative might be to have a ClockCounter / etc construct that you declare, and it tracks the number of rising edges since instantiation, but it'd be another special construct...

[edwardcwang]

Seems like the best way would be a per-clock API/object instantiated by the user...

[schoeberl]

Yes, just per clock should do it. Something like: dut.clock().ticks()

[schoeberl]

Continue the discussion here: about ticks under reset: start counting after reset is released. Just like you would have a hardware counter:

cnt = RegInit(0.U(32.W))
cnt := cnt + 1.U

That's what I do as workaround.