Skip to content
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

Unable to produce dump.vcd file using run function with Verilator #267

Open
TamirBr-H opened this issue Dec 1, 2024 · 0 comments
Open

Comments

@TamirBr-H
Copy link

Description

I am unable to generate the dump.vcd waveform file when using the run function from cocotb-test.

Steps for reproduce:

1. Environment setup
cocotb-test version: 0.2.5
Python version: 3.9.16
Verilator version: 5.030
cocotb version: 1.9.2
OS: CentOS 7
2. Run the following Python code:

from cocotb_test.simulator import run

run(
    verilog_sources=["path/to/your.sv"],  # Replace with your Verilog source file path
    simulator="verilator",
    toplevel="toplevel_module_name",      # Replace with your top-level module name
    module="test",                        # Replace with your test module name
    extra_args=["--trace", "--trace-structs"],
    plus_args=["--trace"],
    waves=True,
    force_compile=False
)

Expected Behavior: The dump.vcd file should be produced in the expected output location, containing the simulation waveforms.

Actual Behavior: The simulation runs without errors, but the dump.vcd file is not generated.

Additional Notes

  • I also tried variations in the run configuration, such as moving "--trace-structs" from extra_args to plus_args, but the issue persists.
  • This issue might be related to how Verilator interacts with cocotb-test, or there could be a missing configuration step.
@TamirBr-H TamirBr-H changed the title Unable to produce dump.vcd file using run function with Verilator. Unable to produce dump.vcd file using run function with Verilator Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant