lekernel changed the topic of #m-labs to: Mixxeo, Migen, MiSoC & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
xiangfu has joined #m-labs
Martoni has joined #m-labs
kyak has quit [Ping timeout: 252 seconds]
xiangfu has quit [Ping timeout: 265 seconds]
xiangfu has joined #m-labs
kyak has joined #m-labs
kyak has joined #m-labs
kyak has quit [Changing host]
xiangfu has quit [Ping timeout: 244 seconds]
xiangfu has joined #m-labs
xiangfu_ has joined #m-labs
xiangfu has quit [Quit: leaving]
xiangfu_ has quit [Client Quit]
xiangfu has joined #m-labs
xiangfu has quit [Remote host closed the connection]
kmehall_ has joined #m-labs
kmehall has quit [Ping timeout: 245 seconds]
kmehall_ is now known as kmehall
bvernoux has joined #m-labs
mumptai has joined #m-labs
<mumptai>
hi
<mumptai>
i ran the examples of the migen tutorial, and observed a interesting behavior, where the vcd is not written if the simulation is stopped at 100 cycles, but works if its set to a 1000
<davidc__>
mumptai: that'd probably be an iverilog bug or something
<davidc__>
mumptai: since VCD generation/etc is all just icarus verilog
<mumptai>
probably
<mumptai>
k, if i find time tomorrow and it's not a know issue(?), i could put some time in it
<sb0>
hmm, I've run very short simulations with VCD output, and didn't run into that problem
<sb0>
mumptai, how are you running the simulator?
<sb0>
maybe you are not properly shutting it down
<sb0>
you should use Simulator as a context manager, or the run_simulation function
<mumptai>
as far as i understand it, it should be stoped by the ncycles parameter
<sb0>
ncycles doesn't permanently shut down the simulation, i.e. you can call Simulator.run() again