-
I've read this post on SO:
https://stackoverflow.com/questions/42980036/how-to-combine-multiple-vunit-run-py-files-into-a-single-vunit-run
I want to start a discussion, if it is possible to provid…
-
Hi,
I tried to add tcl a tcl script to a core to be build with Vivado. Specifically I have a build script for a Vivado IP integrator block design (created with the write_bd macro) which I want to ad…
-
I'm currently working on projects that use both Quartus Std and Quartus Pro. The Pro version of the tools have made a few changes around the tool executable names and how QSYS gets invoked - this make…
-
I added a local fusesoc.conf file with the --config option to my fusesoc command line. This is the content of the file:
````
[main]
cores_root =~/development/bonfire
build_root = ~/development/Viv…
-
Hello! I'm currently experimenting with FuseSoC to see if I can make use of it to build some of our projects. I've noticed that the Quartus backend does not presently look for a logical_name associate…
-
Hello,
Im having this error:
```
cruiz@carlos-pc:~/repositorio/pyvivado/tests$ python3.5 test_project.py
Traceback (most recent call last):
File "test_project.py", line 6, in
from py…
-
Please check:
~/Projects/openrisc$ fusesoc sim --sim=icarus i2c
WARN: plusargs section is deprecated and will not be parsed by FuseSoC. Please migrate to parameters in fifo-1.0
WARN: plusargs sec…
-
Hi,
At the moment modelsim simulations are run by default in command line mode using the `-c` switch which is hard-coded in the run target of modelsim.py. Specifying the `-gui` or `-i` switches in` v…
-
Currently we put the templates of the generated project files (e.g. the TCL file for Vivado) inside the backend code itself. That's hard to maintain and annoying to modify.
How about using a templa…
-
Fusesoc by default writes a file 'fusesoc.log' into the working directory. Even though this is common for many EDA tools, I suggest removing this functionality by default.
Why?
- Having two fuseso…