You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Moving the assignments to wrport.addr and wrport.data into a comb block restores the expected behaviour, so I guess it's to do with the addr/data being driven from a sync block?
The text was updated successfully, but these errors were encountered:
I noticed in my design that two memories, both defined the same way and in the same clock domain, seemed to have different write behaviours:
This first one is what I'd expect: one cycle after addr=2 and data=2, mem(2) gets the value 2:
This is the weird one: last cycle's data is written to this cycle's slot:
I made a small reproduction of the buggy case:
Moving the assignments to
wrport.addr
andwrport.data
into a comb block restores the expected behaviour, so I guess it's to do with the addr/data being driven from a sync block?The text was updated successfully, but these errors were encountered: