Xilinx vivado install linux

Vivado installation on Linux

Contents

Introduction

Vivado is the new FPGA design tool from Xilinx. It replaces ISE and XPS tools for new Xilinx’s products. By default no Armadeus board has a new FPGA supported by Vivado, but, with the APF6, we can use Artix7 on a daughter board (or with Xilinx dev-kit), thanks to PCIe, and enjoy this new Xilinx tool. This page is a tutorial on how to install Vivado on Debian Linux host computer.

Note: Vivado can’t be used with Spartan products, it starts with the «7» FPGA serie (artix7, virtex7, zynq, kintex7, . )

Installation

Requirements

• unsure that Bash is the default shell:

• otherwise:

Download

• Download the file on xilinx website, note that you will need an account (free) to do that.

Launch install

• To launch install simply type :

• Fill forms then wait for about 20 minutes

Launching Vivado

• Go to the installed directory:

• Source the architecture shell file:

• Then launch it:

JTaG probes

Digilent provide a JTAG probe to configure Xilinx FPGA named HS3.

Driver script installation is provided by Vivado in following directory :

Should be launched as root to install drivers:

Источник

Installing Vivado 2020.x on Ubuntu 20.04

December 6, 2020

Vivado is Xilinx’s IDE for HDL synthesis and analysis. It is a powerful tool, but can be a bit of a pain to setup and use. I recently went through the installation process on my main development machine, where I cam currently running Ubuntu 20.04, after I purchased a Digilent Arty A7-35T development board, which is designed around the Xilinx Artix-7 FPGA. While it didn’t take too long to get up and running (ignoring the time waiting for the actual installation to complete), I found the existing installation documentation quite verbose, which made following along more difficult than it should have been. The primary issue I (unsurprisingly) ran into was that Ubuntu 20.04 is not officially supported by Vivado 2020.1, which requires a workaround that is detailed below. The subsequent Vivado 2020.2 release has addressed the issue, but still does not officially support Ubuntu 20.04.

If you prefer to follow the official documentation for installation, it can be found here. There is also helpful documentation from Digilent, which is especially useful if you are primarily using one of their boards.

Downloading the Xilinx Unified Installer

Xilinx provides a number of development tools for their products and follows the familiar pattern of releasing a single unified installer that allows users to install any of them from a single entry point. The following steps describe how to download the installer for your machine.

Here you should be met by a set of tabs, each with a different tool. By default, you should see Vivado (Hardware Developer) tab first. If you scroll down, you should see options to download the Xilinx Unified Installer Self Extracting Web Installer for a variety of platforms.

We want the Linux installer, but we will need to create a Xilinx account first. Click on the Xilinx Unified Installer 2020.2: Linux Self Extracting Web Installer link and you should be redirected to the Xilinx login page.

1. Create a Xilinx Account

Some Vivado editions require that you have a license. To program Artix-7 boards you should typically be fine with just using the Design Edition, which only requires a Xilinx account. Walk through the steps to create a new account and activate your user.

1. Download the Unified Installer

After you have created and activated your user, you can navigate back to the downloads page and click the link again. The installer should now download successfully.

It is a good idea to verify the integrity of the installer after download. As pictured in the screenshots above, Xilinx provides digests, signature, and a public key for the download. The official documentation has a great section on how you can verify your downloads, so I will omit those steps here for brevity.

(Optional) Faking Your OS Version

As I mentioned in the introduction, Vivado 2020.x does not officially support Ubuntu 20.04. However, in my experience (and the experience of many others online), it mostly works just fine. Do keep in mind that it is generally not advisable to deceive a program into thinking it is running on a different platform than it is, and there is inherent risk in doing so. Additionally, you will likely be installing Vivado 2020.2 now that it is available.

That being said, if you are installing Vivado 2020.1 on an incompatible version of Ubuntu, you can fake an older OS version by editing the /etc/os-version file. If you do not do so, you will likely see the following output when attempting to run the installer. It program doesn’t fully crash, but you won’t be able to use the GUI.

The /etc/os-version likely looks something like the following for you:

The specific field you will want to change is VERSION , and it should be set to 18.04.4 or earlier. You will need to edit as super user as os-version will be a read only file.

After saving your changes, the unified installer should run successfully.

Make sure that you change the version back to its appropriate value after installing Vivado. Failure to do so can cause issues when running other applications on your machine.

Running the Unified Installer

You can run the unified installer by making it executable and running as super user.

Digilent documentation will specify that you run the installer as root. With newer versions, such as 2020.x, this is no longer necessary as cable driver installation has been isolated as a separate step. More on this below.

After a few seconds, you should be greeted with the Welcome window.

Here we are presented with the helpful reminder that our OS version is not supported, but we will press on. The next window will ask you to login to your Xilinx account. The same credentials you provided when creating your user at the beginning of this account should be utilized here.

Next, you’ll need to agree to terms and conditions.

Now we will actually begin to customize the installation. As mentioned earlier, this installer can be used to install many different Xilinx products. The two you would likely be considering are Vivado, of course, and Vitis. Vitis is a newer development suite from Xilinx that is targeted more at software developers rather than hardware developers. The initial press release does a pretty good of explaining the motivation behind it. This quote is particularly illustrative of when you might want to choose Vitis over Vivado:

Vitis is separate to the Vivado® Design Suite, which will still be supported for those who want to program using hardware code, but Vitis can also boost the productivity of hardware developers by packaging hardware modules as software-callable functions.

As part of the announcement, Xilinx also announced a new developer portal, which has some examples that will give you an idea of what the Vitis workflow looks like. It should also be noted that, as shown in the screenshot below, installing Vitis will also install Vivado. Today we are just going to be installing Vivado as our primary goal will be programming at the hardware level.

Next we will select the version of Vivado we want to install. Since we are not purchasing a license, the Systems Edition will not be an option. The WebPACK version is a fine option for getting started, but there is a good chance you will want some of features in the Design Edition eventually, so it likely makes sense to go ahead and start off with it (as you will see later, it is preferable to not frequently reinstall these tools).

You will also have to configure options for your installation. I chose the defaults minus “Acquire or Manage a License Key” and “Enable WebTalk for Vivado to send usage statistics to Xilinx” (sorry Xilinx).

The final steps are to choose an installation location and confirm install. It is a large installation to say the least (see “Final Disk Usage: 48.97 GB”), and as such will take quite a long time to install. I started mine on a Saturday morning and checked back in during the afternoon and it had finished by that point.

You should not see the same errors displayed for me as they are only due to the fact that I had previously already installed Vivado 2020.1.

Hit install and you are off to the races!

Installing Cable Drivers

I mentioned earlier that cable drivers are now installed separately from the Vivado installation process. After your installation is complete, you should find a script that you can run to make sure the correct drivers are installed.

Launch Vivado

Vivado should be ready to go at this point. You’ll need to add vivado to your PATH . Xilinx has once again provided a helper script to add the relevant executables.

This will only add to PATH for the current session. Add export PATH=/tools/Xilinx/Vivado/2020.1/bin:$PATH to

/.profile if you want vivado to be available in any session.

Now you should be able to enter vivado and see the following quick start window.

Wrapping Up

Hardware programming can feel intimidating, but the more you interact with the various toolchains the more you begin to gain familiarity. I will continue to share guides and tutorials here, and, as always, please feel free to send me a message @hasheddan on Twitter with any questions or comments!

Источник

Xilinx Vivado

This article or section needs language, wiki syntax or style improvements. See Help:Style for reference.

Arch Linux is not officially supported by Vivado, but as happens with Xilinx ISE WebPACK, most of its features can be used with a bit of hacking.

Contents

Installation

Xilinx Vivado can be downloaded from its official website [1]. It’s recommended to download «Vivado HLx . : All OS installer Single-File Download» tarball, but make sure not to be in a hurry, as it’s a large download (over 35 GB). Update tarballs can also be downloaded and installed later.

AUR Package

The vivado AUR AUR 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.

Manual Installation

Dependencies

The installer needs ncurses5 libs, and will not work with ncurses 6 available at official repos. You can work-around this problem by installing ncurses5-compat-libs AUR from the AUR. You will also need to install libpng12 and lib32-libpng12 for Xilinx Document Navigator to launch.

SDK 2018.3 (potentially also other versions) needs gtk2 library. You may need to install gtk2 if you are planning to use SDK. Vitis needs xorg-xlsclients in order to work properly.

Instead of manually installing all these dependencies separately, the xilinx-vivado-dummy AUR metapackage can be used instead.

On some Tiling Window Managers (confirmed dwm and Xmonad), you may need to set this environment variable before launching xsetup (otherwise the installation GUI will not render).

You must install the main package, and it is also recommended to install the latest update patch.

Fonts may render incorrectly making some text hard to read and causing some UI elements to be cut off. This can be fixed by installing noto-fonts .

Dependencies for petalinux-tools

Before Launch petalinux-tools, please install:

and Aur Package

Enable the multilib repository and install the multilib-devel group.

Vivado and SDK

Once downloaded and unpacked the tarball, run:

It is recommended to install the suite at the default location /opt/Xilinx , as further instructions in this page will assume the suite is installed there.

Linux cable driver

Then run as root privilege:

Desktop Shortcuts

The installation process must be run as root for write access to /opt/Xilinx. If shortcuts in application menus are desired, they must be moved from the root account to /usr/share. Desktop shortcuts must be moved to the users desktop.

The following commands assume only Xilinx has been installed to the root account and the user has the username username.

To copy the application menu shortcuts:

To copy the desktop shortcuts:

Digilent USB-JTAG Drivers

To use Digilent Adept USB-JTAG adapters (e.g. the onboard JTAG adapter on the ZedBoard) from Vivado, you need to install the Digilent Adept Runtime.

Make sure you have installed fxload AUR from the AUR .

To install the Digilent Adept Runtime, it is recommended to install digilent.adept.runtime AUR from the AUR.

In addition, installing digilent.adept.utilities AUR may do good to configuring your board.

Tips and tricks

Enable display scaling

Start vivado, then set the scaling rate as follow:

Disable WebTalk

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 method will not pollute your environment, only the temporary environment that is configured upon startup of the tools, so it should not break anything else.

Troubleshooting

Synthesis segfaults

You will need to recompile glibc (just take the PKGBUILD from the abs) with —disable-lock-elision . Instead of patching the system libc in /usr/lib , copy the newly compiled libpthread-2.25.so and libc-2.25.so to /opt/Xilinx/Vivado/2016.4/ids_lite/ISE/lib/lin64 Do not forget to repeat this when glibc gets upgraded.

xsct, xsdb, xmd, and tclsh segfault

The Xilinx Vivado command-line tools xsct, xsdb, xmd, and tclsh may crash with a message similar to the following:

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 from the official repo and edit the path to the rlwrap binary in the affected command startup script(s) from:

To the following:

Vivado HLS testbench error with GCC

Vivado requires an older version of glibc (2.26).

The solution proposed in this thread from Xilinx forums suggests to update the fixed headers shipped by Xilinx.

Vivado Crashes with Wayland

If Vivado crashes and the error file contains something similar to this:

Switch to using Xorg instead of Wayland. The version of Java Vivado uses has compatibility problems with Wayland.

Vivado 2020.1 installer does not start

The Vivado 2020.1 installer may not start on Arch Linux. The splash-screen and warning about the unsupported OS show up, but nothing happens after closing the dialog:

A possible workaround is to start the installation using the batch installer. First generate a configuration file and select your product (Vitis includes Vivado):

Then edit the configuration file generated at

/.Xilinx/install_config.txt with your desired install location. Finally run the installer:

To update Vivado from 2020.1 to Vivado 2020.1.1

If your 2020.1 installation failed to launch and needed to be installed in batch mode, you will need to update using batch mode:

If Vivado was originally installed by the root user, you will need to launch the update as the root user.

Synthesis fails on certain locales

If your system locale does not use a dot . as the decimal seperator, but for example a comma , (e.g. de_DE ), synthesis may fail with errors such as wrong operator types for + .

A possible workaround is to force Vivado to use en_US.UTF-8 as the locale for numerics. This can be easily done by appending

Fonts ignore system anti-aliasing settings

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.

Assuming Vivado is installed in the default location of /opt/Xilinx/Vivado/YYYY.Q where YYYY.Q is the verion (i.e. 2020.2), modify vivado to include the following:

Licensing

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).

Floating License

Set the environment variable XILINX_LICENSE_FILE to point to a floating server license. You will have to be on the same network as the server, so connecting with a VPN might me required.

Источник