[question] Trying to understand simulator wait apis (newbie) about spinalhdl HOT 3 CLOSED

For example, in the testbench above, my (limited, maybe wrong) understanding is that dut.clockDomain.forkStimulus(10) call somehow sets the clock and reset signal during each iteration of the eval loop

Not necessarly each eval loop.
SpinalSim emulate time on the top of verilator. So if you have other things happening at other times, that forkStimulus isn't involved.

dut.io.limit #= 7 is executed after some clock cycles have already been evaled by the model

dut.io.limit #= 7 isn't part of the model, it is software.
in SpinalSim, when you do a #= it will always be visible after the end of the current delta cycle and before the start of the next delta cycle

waitSampling() will wait until the clock sampling is detected. It doesn't trigger eval.

In other words, SpinalSim emulate time on the top of verilator by having a queue of callback to execute on given timestamp. that's mostly it ^^

from spinalhdl.

@hMihaiDavid You gave Dolu's answer a thumbs up, did his response answer your question? In that case we could close the Issue.

Two quick hints:

• In the simulation threads are not "real" threads, but run serially so you don't need any locking etc.
• It's not required, but if you have some question that's not a bug or something you can ask them in the gitter chat - more eyes there that can help

from spinalhdl.

It's much more clear now, thank you both.

from spinalhdl.