Activity

Update: I re-transmitted again and on the second batch of data, then a_ready_in is asserted the clock cycles I set with RECEIVE_READY_DELAY_CYCLES. See here: https://ibb.co/MxD4D0fF

Is there any specific reason? Is it possible to set at the beginning of the process whether tready should be 1 or 0?

Hi Jim,

Are there any updates on this?

I am also looking to not having tready asserted by the receiver at the beginning, but instead using RECEIVE_READY_BEFORE_VALID=FALSE and RECEIVE_READY_DELAY_CYCLES to assert tready after tvalid is asserted. See here https://ibb.co/jZVyy9ZH
Thank you.

ps: Do you have a new and updated documentation for the…[Read more]

Hi Jim,

Are there any updates on this?

I am also looking to not having tready asserted by the receiver at the beginning, but instead using RECEIVE_READY_BEFORE_VALID=FALSE and RECEIVE_READY_DELAY_CYCLES to assert tready after tvalid is asserted.

Thank you.

Of course! I assumed gtkwave would update when updating to the latest ghdl version. It wasn’t the case. Now with gtkwave 3.3.221 it opens as expected.

What about running the simulation in vivado? I’m mostly interested in post synthesis functional simulation as I have a vhdl module currently that works fine in behavioral simulation and works…[Read more]

Your GTKwave is propably too old. You have 3.3.104, whereas GTKwave is now at 3.3.121.

What platform do you use?
Linux, macOS, Windows, MSYS2, …?

As an alternative: https://surfer-project.org/
Unfortunately, the made there own GHW reader as far as I know. So it could be failing as well.

GHW is a waveform format from GHDL specially made for…[Read more]