-
Notifications
You must be signed in to change notification settings - Fork 297
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
Option --toolchain=openxc7 ignored for Genesys2 #624
Comments
The same issue of the toolchain option being ignored, using Vivado as default instead, also happens with --toolchain=yosys+nextpnr and --toolchain=f4pga and also in combination with litex-boards/litex_boards/targets/xilinx_kc705.py |
In fact |
@trabucayre Thank you, I tried the changes and the toolchain option is recognised properly now. I am now running into path and dependency issues, as I installed openXC7 with the recommended nix based installer instead of the snap one that the LiteX core expects; but regarding the Genesys2 target file, this is fine and the option is properly handled now. Please merge it as-is. |
targets/digilent_genesys2.py: added toolchain option (#624)
I am trying to generate the LiteX example SoC for a Kintex-7 based Digilent Genesys2 board with a fresh LiteX install, using the openXC7 toolchain. But it seems as if the option --toolchain=openxc7 is ignored.
~/FPGA/LiteX/litex-boards/litex_boards/targets/digilent_genesys2.py --toolchain=openxc7 --output-dir=experiment-nogates --build --no-compile-gateware
Results in a build_digilent_genesys2.sh file to launch Vivado instead of Yosys (
vivado -mode batch -source digilent_genesys2.tcl
) along with the .tcl file necessary for Vivado.Likewise, using this command
~/FPGA/LiteX/litex-boards/litex_boards/targets/digilent_genesys2.py --toolchain=openxc7 --output-dir=experiment --build
ends with this error message:
I would expect it to create a shell script to invoke yosys and nextpnr-xilinx as provided by the openxc7 toolchain.
The text was updated successfully, but these errors were encountered: