-
Notifications
You must be signed in to change notification settings - Fork 195
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
vivado xsim support for xci or xilinx ip #344
Comments
I think we'd all love to see that if you're willing to give it a go :) |
Yes, that is a known issue. Currently, the vivado backend runs in project mode while xsim runs in non-project mode. My proposal is to convert the xsim backend to run in project mode as well. That should bring a number of other features as well. Haven't got the bandwidth to work on it myself so very happy for any help here. |
xsim doesn't launch vivado at all. It only calls xelab and xsim. It could be treated as a dependency, or any other code generation flow. Is there such framework in fusesoc? |
I implemented a working solution which should be compatible with synthesis. I still have to test synthesis and will release it. In my case, I'm using mig memories, which are entirely described in "mig_a.prj" file. xci file is not needed for these, and ip can be created using 3 lines of tcl:
This will generate myMig Module. this xml file is quite compact and should be easily hand edited. implementation is quite easy thanks to jinja templates |
pull request made |
Hi,
it seems that vivado xsim doesn't support generating xilinx ip for simulation.
It is supported for synthesis
Is it a planned feature?
If not I would be willing to help implementing it.
The text was updated successfully, but these errors were encountered: