Bool parameter for boolean VHDL generic produces wrong tcl command for Vivado.
See original GitHub issueYou can check it here: fusesoc_example. Just run fusesoc --cores-root . run --target custom_target_2 ::fusesoc_example
and check file build/fusesoc_example_0/custom_target_2-vivado/fusesoc_example_0.tcl
line 9.
There is:
set_property generic {TOP_ADD_DELAY=1 } [get_filesets sources_1]
Should be:
set_property generic {TOP_ADD_DELAY=true } [get_filesets sources_1]
I could fix this if you tell me how/where the fix should be placed? In fusesoc or edalize?
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Generics not evaluated before synthesis - Xilinx Support
In my top level port I have the following generic: entity TOP is generic( FIRMWARE_IS_CB : boolean := false ); In the code...
Read more >Settings Generics/Parameters for Synthesis - Doulos
Setting Generics/Parameters in Xilinx Vivado ; Select Project Settings from the Project Manager section of the Flow Navigator window. ; Highlight the General ......
Read more >Vivado Design Suite Tcl Command Reference Guide
Enter individual Tcl commands in the Tcl Console at the bottom of the Vivado IDE. • Run Tcl scripts from the Vivado Design...
Read more >Vivado Design Suite User Guide: Logic Simulation (UG900)
Appendix A: Value Rules in Vivado Simulator Tcl Commands ... generic (VHDL) or parameter (Verilog) SIM_COLLISION_CHECK string in block RAM.
Read more >tsfpga package
Path) – Path to a Vivado project that contains generated “simulation” and “synthesis” files of IP cores (the “generate_target” TCL command).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I test with Vivado 2018.3, with
True
the build fails, withtrue
it is successful. I am also astonished. Vivado output doesn’t explicitly inform that the problem is withTrue
as the out in case of failed build is as follows:To make the build successful I need to replace
True
withtrue
. This is Xilinx.Works.