Xilinx Vivado 2019.1 Download
Carri Seargent
Is there a way to specify which version of Xilinx Compilation Tools to use when compiling an FPGA VI? I want to try the Vivado version of the tools rather than the ISE version to see if there is any improvement. I've listed some information about my setup below.
In the past I have used the 'LabVIEW 2014 FPGA Module Xilinx Tools 14.7' to compile my code. But I also want to try the Vivado version, 'LabVIEW 2014 FPGA Module Xilinx Tools Vivado 2013.4', to see if it gives better results.
Based on the 'Compatibility between Xilinx Compilation Tools and NI FPGA Hardware' page here:
-between-xilinx-compilatio...
It looks like the PXIe7966 FPGA should be compatible with the Vivado 2013.4 tools.
I have tried uninstalling the ISE 14.7 version of the tools, and installing the Vivado 2013.4 tools (so that the Vivado 2013.4 tools are the only xilinx tools installed on the computer). But LabVIEW still complains that the ISE 14.7 tools are not installed and does not compile the FPGA VI.
Thanks for the additional reference link! Although I am going to mark the other reply as the solution because this was really due to the fact that vivado does not support any virtex 5 FPGAs (not really a LabVIEW concern).
Get Vivado running before messing with nix. The Vivado install tools (both command line and Java-based) have annoyingly rigid dependencies on particular versions of Linux OS. For example, v2020.2 supports the follows Ubuntu variants:
Just because Vivado support 18.04.4 LTS does not mean it supports 18.04.5 LTS. You'd think it would trivial to get 18.04.5 to work but it's not. Command line install and the several well-intentioned Xilinx support threads didn't help me.
We're installing Vivado on NixOS directly, which isn't supported by Xilinx but works nevertheless. You can use buildFHSUserEnv to simulate a traditional distro (AFAIK also works on non-NixOS Nix with reproducibility benefits); an alternative approach is to use patchelf.
This GUI installer bug can be worked around by running the installation in command line like this:
-labs.hk/d/75-configuring-a-custom-kalsi-crate/5
And the Xilinx installer does not really need sudo, it just needs to write to the destination directory.
For anyone reading this again: The ARTIQ-7+ development shell (nix develop) now provides a vivado-env command that spawns another shell containing all the dependencies for the Vivado installer to work, on any distro.
When you instantiate a component in your design, the simulator must reference a librarythat describes the functionality of the component to ensure proper simulation. Thus,before performing simulation of the design that contains Xilinx components in Active-HDL,you should attach the proper simulation libraries.
You can either use pre-compiled simulation libraries provided by Aldec (libraries can bedownloaded from Aldec's website) or you can compile them yourself in the Xilinx VivadoDesign Suite and then attach the compiled libraries into Active-HDL.
You can either use the compile_simlib command or the Compile Simulation Librarieswizard that simplifies compiling simulation libraries. With these tools, you cancompile all IP core libraries included in the Vivado IP Catalog and the following basicXilinx Vivado simulation libraries:
Under the Compiled Library Location, select the directory where you want the compiled libraries to be saved. Under the Simulator Executable Path, provide the path to the directory containing the avhdl.exe file in the Active-HDL installation directory. In the GCC executable path, add the path to the C/C++ compiler required for building SystemC IP cores.
By default, all the IP modules available in the Vivado IP Catalog are selected for compilation. You can change that behavior by clearing the Compile Xilinx IP check box. When cleared, only the basic simulation libraries are compiled. You may also want to enable recompilation of libraries already present in the output directory. To do so, select the Overwrite the current pre-compiled libraries check box.
The above command will compile all simulation and IP libraries written in VHDL, Verilog,and SystemC for all devices available in Vivado. To disable compilation of IP Corelibraries and compile only Xilinx simulation libraries, invoke the compile_simlib commandwith the -no_ip_compile argument. You may also want to disable recompilation of librariesalready present in the output directory by issuing the -force argument.To obtain the complete list of available arguments, type compile_simlib -helpin the Vivado Tcl Console.
After generating the compiled Xilinx libraries, they have to be attached into Active-HDL.You can either use the amap command or the Attach Library wizard to add requiredlibraries. If you are using Active-HDL as the default simulator in Xilinx Vivado 2017.4or later, you can attach the libraries within that environment.
In Vivado, specify the path to the directory with the compiled libraries in the Compiled library location field which is available in the Project Settings Simulation category of the Settings window when a project is loaded.
Select the Use precompiled IP simulation libraries check box in the Project Settings IP Simulation category of the Settings dialog box. If this option is enabled, all the required libraries such as the precompiled IP simulation libraries and the xilinx_vip and xpm libraries are included as mappings in the generated macros so they are not recompiled when invoking the Active-HDL simulator.
Select the location of the compiled Xilinx libraries, then select the *.lib file of the selected library. If you are using Active-HDL as the default simulator in Xilinx Vivado,make sure that the Attach as Global Library check box is selected. Click Open.
This will map the libraries locally to the library.cfg file from the current designdirectory. If you want to map all the Xilinx Vivado libraries compiled in previous steps,invoke the following command:
In order to simulate Xilinx Vivado designs in Active-HDL, Xilinx simulation librariesare required. You can either use pre-compiled libraries provided by Aldecor you can compile the libraries yourself in Vivado Design Suite. After compiling the librariesin Vivado, they have to be attached into Active-HDL in order to run the simulation.
Xilinx Vivado can be downloaded from its official website [1]. It is recommended to download "Vivado HLx .: All OS installer Single-File Download" tarball, but make sure not to be in a hurry, as it is a large download (over 70 GB). Update tarballs can also be downloaded and installed later. The other installer can also be used, but see the troubleshooting section below first.
The vivadoAUR package can be used to create a Vivado installation managed by pacman. Since the download of the installer is locked behind a login wall, it needs to be downloaded manually as outlined above and placed in the same directory as the PKGBUILD. The package only builds the latest major version (.), not the minor updates (..); if these are required, install Vivado manually instead.
The free WebPACK license does not let you disable this feature which uploads usage data to Xilinx's servers when generating a bitstream, but synthesis will complete just fine if the connection fails. A simple way to make it fail consistently for Vivado tools only is to set an invalid HTTPS proxy for it.
This is a problem with the rlwrap version bundled with Vivado, probably due to the lack of legacy vsyscall emulation in Arch Linux.To fix this issue, either drop rlwrap altogether (losing command history and auto-completion), or install rlwrap and edit the path to the rlwrap binary in the affected command startup script(s) from:
With OpenJDK 11 and Vivado display scaling activated, the menu and other UI element fonts may render without any anti-antialiasing regardless of desktop environment settings. This can be fixed by editing the Vivado launch script to append awt.useSystemAAFontSettings=on to the JVM options.
Xilinx Vivado contains modules called Intelectual Property (IP) cores and as the name suggests, you should expect licenses to be required for these modules. Two modes of licensing are possible: Floating (server) or Nodelocked (license file).
c80f0f1006