Navigation Menu

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

instantiate SystemC model in Verilog dut #1277

Closed
veripoolbot opened this issue Feb 14, 2018 · 1 comment
Closed

instantiate SystemC model in Verilog dut #1277

veripoolbot opened this issue Feb 14, 2018 · 1 comment
Labels
resolution: wontfix Closed; work won't continue on an issue or pull request

Comments

@veripoolbot
Copy link
Contributor


Author Name: Steven Milburn
Original Redmine Issue: 1277 from https://www.veripool.org


Hello,

I'm trying to verilate a system with the following hierarchy:

sim_main.cpp as a testbench instantiating dut.v, which instantiates core.cpp, a systemC model.

I get an error that verilator cannot find file containing module "core". It has looked in a bunch of places looking at extensions [none], .v, and .sv.

My command line is:
verilator -Wall --sc dut.v core_model/core.cpp -Icore_model/include

In this flow, I was going to link in the sim_main.cpp part later with a g++ command.

Is this type of hierarchy workable with SystemC? If so, can someone please explain what I'm missing to make verilator find the systemC model for core?

Thanks

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2018-02-14T12:17:01Z


You cannot have SystemC underneath Verilog, unless you use DPI/VPI to make some sort of harness similar to what you would have to do with a commercial Verilog simulator.

@veripoolbot veripoolbot added the resolution: wontfix Closed; work won't continue on an issue or pull request label Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolution: wontfix Closed; work won't continue on an issue or pull request
Projects
None yet
Development

No branches or pull requests

1 participant