-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simulation gets stuck with SIM=verilator 4.106 #35
Comments
Hi @andreaskuster Only to clarify, I am simply a recent user of cocotbext-axi. I can't right now, but I will try to reproduce it and let you know. Let me say that I ran |
Thanks for your reply. And yes you were right, i meant version Furthermore, i tested different (older) versions of cocotbext-axi, with the same behaviour, so this problem seems to be present for a while. |
Ok, I didn't know about the cocotb limitation using Verilator. I generally use cocotb with GHDL or iverilog. |
Sure, ghdl and iverilog are fine, as long as you work with vhdl or verilog. However, I am currently extending a project written in SystemVerilog, which is why I would like to get verilator up to speed. Well, it is not really a limitation by design, but rather the devil that comes with the fact that verilator is extending the VPI infrastructure. This should eventually become compatible again. However, I am not sure if verilator is really to blame here, since the latest (v1.6.1) cocotb basic examples seem to work with |
I'm not sure what the problem is here. But I'm also not going to do anything with verilator until verilator/verilator#2778 is resolved so that cocotb will work correctly with current versions of verilator. |
Yeah sure I can understand that. Thanks for your clarification. Let's keep this open and come back as soon as verilator has been fixed. BTW: |
I mean, it's also possible that I introduced some sort of bug recently that only affects verilator. So it's probably still worth getting to the bottom of what's going on here. Previously, I think I have tested this on verilator 4.106, and it worked fine. But there have been some changes since then, although I can't think of any change in particular that might have affected verilator specifically. |
I think that the problem either exists for a longer time, or it is already broken in verilator 4.106, since I tried different, older version combinations of cocotbext-axi and cocotb, but with the very same result of getting stuck. |
…/cocotbext-axi#35) has been resolved (questasim works, but need a license)
@andreaskuster I was also facing this issue, where after I upgraded several libraries the simulation for my previously working project got stuck. I'm using Verilator Reverting cocotb-bus to version
When a bus version > |
Thanks a lot for this great project! @alexforencich @rodrigomelo9
I am trying to run the
axi-verilog
designs usingverilator
, however, this library does not seem to be compatible with verilator. I use version4.106
which should be compatible with cocotb (all their base examples work).However, it seems as if the simulation tests are stuck here: https://github.com/alexforencich/cocotbext-axi/blob/master/cocotbext/axi/axi_master.py#L413
Commands for reproduction:
running
make
withoutSIM=verilator
worksThe log for the axi test is:
The text was updated successfully, but these errors were encountered: