-
Notifications
You must be signed in to change notification settings - Fork 23
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
Can't find top module when using plugin #2430
Comments
Do not build nor install Yosys separately. Use the yosys exec built under the synlig directory |
ahh, that explains it, I have yosys installed already. Am I correct in saying that systemverilog is not a plugin for yosys then? its a "plugin" but requires a modified yosys or it won't work? If yosys does need modified, why not put a patch into the main yosys package? I'll have to find time to uninstall the system yosys and try again. at the moment I have things sortof working with sv2v. |
Correct, it does not really work as a plugin as it is, you have to build it alltogether the way it was setup. The Synlig plugin is not compatible with the latest Yosys api, so you can't use the latest yosys starting about 2 months ago. Synlig checks out the compatible version and patches it. No funds to integrate properly with Yosys are available at this point (both on Yosys and Synlig side). There is another integration model used here were both are built separately, but it is an expert build level that I would not recommend unless you want to tinker with cmake: https://github.com/os-fpga/Raptor_Tools/tree/8705ea7ef18c3b0f6aa41e490f1edb03a672f08e/parser_plugins |
I've installed
yosys
. I've installed thesystemverilog
plugin fromhttps://github.com/chipsalliance/synlig
.I can load the plugin, but then it can't find the
top
module.all that is in
src/main.sv
is a simple top module to count on some leds:This same code WILL build with just Verilog, but I'm trying to get it to build as SystemVerilog as I want to start using SystemVerilog features.
What am I doing wrong?
The text was updated successfully, but these errors were encountered: