Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cocotb only supports Verilator 4.106

See original GitHub issue

cocotb: master 9b442d07870751ff656eb1ed53d24a3d806e9610 os: centos 7 64bit simulator: Verilator 4.107 devel Python: 3.7.6 (conda)

log:

     -.--ns INFO     cocotb.gpi                         ..mbed/gpi_embed.cpp:74   in set_program_name_in_venv        Did not detect Python virtual environment. Using system-wide Python interpreter
     -.--ns INFO     cocotb.gpi                         ../gpi/GpiCommon.cpp:105  in gpi_print_registered_impl       VPI registered
     -.--ns INFO     cocotb.gpi                         ..mbed/gpi_embed.cpp:244  in embed_sim_init                  Python interpreter initialized and cocotb loaded!
     0.00ns INFO     cocotb                                      __init__.py:212  in _initialise_testbench           Running on Verilator version 4.107 devel
     0.00ns INFO     cocotb                                      __init__.py:219  in _initialise_testbench           Running tests with cocotb v1.5.0.dev0 from /themperek/git/cocotb/cocotb
     0.00ns INFO     cocotb                                      __init__.py:239  in _initialise_testbench           Seeding Python random module with 1608640613
     0.00ns INFO     cocotb.regression                         regression.py:127  in __init__                        Found test test_dff.test_dff_simple
     0.00ns INFO     cocotb.regression                         regression.py:466  in _start_test                     Running test 1/1: test_dff_simple
     0.00ns INFO     ..st.test_dff_simple.0x7f08b057d650       decorators.py:313  in _advance                        Starting test: "test_dff_simple"
                                                                                                                     Description:  Test that d propagates to q

simple_dff_verilator.log

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:17 (14 by maintainers)

Top GitHub Comments

2reactions

ktbarrettcommented, Jan 25, 2021

I agree that outright stating that Verilator support is still experimental is probably a good idea. But I’m trying to whittle down work before we can release 1.5, not do more 😄. I’ll add a note.

1reaction

markusddcommented, Nov 13, 2022

Thanks @vighneshiyer for providing this fix. With that it works for now.

Nevertheless: Is there any chance of this moving forward? Verilator&CocoTB in combination are just awesome and especially for exhaustive module testing there is hardly any better combo right now.

I’m more than happy to try out new stuff with my testbenches but it seems that this has ground to a halt somehow.