<jevinskie[m]>
Are you using multiple verilator threads?
<qball1>
no
<qball1>
I made is completely single threaded
<qball1>
to be sure
<qball1>
*it
<qball1>
I suspect I know what it is, I have normally have a memory mapped interface between the design and external world. In this case a dual port memory. I use the pub header in verilator to get the memory array, and read/write from there.
<qball1>
reading goes fine, with writing I see an older value sometimes return.
<qball1>
this happens when at the same time (from what I can deduce) the bram has a read at the same address.
<qball1>
so I guess it is how the simulator works.
<qball1>
not sure if I can work around this.
dys has quit [*.net *.split]
_whitelogger has joined #yosys
kraiskil_ has joined #yosys
kraiskil_ has quit [Ping timeout: 252 seconds]
FabM has quit [Remote host closed the connection]
Guest57 has joined #yosys
anticw has quit [Remote host closed the connection]