Xilinx Vivado

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 (<year>.<version>), not the minor updates (<year>.<version>.<update>); if these are required, install Vivado manually instead.

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.

Start vivado, then set the scaling rate as follow:

Tools -> Setting -> Display -> Scaling

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.

/opt/Xilinx/Vivado/<version>/bin/setupEnv.sh

...

export HTTPS_PROXY=localhost

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.

See https://support.xilinx.com/s/article/76524?language=en_USdead+link+2021-11-19 ⓘ

Create file

/Xilinx_path/Vitis_HLS/yyyy.Q/bin/compat_firefox

#!/bin/sh
unset LD_LIBRARY_PATH
firefox $@

then configure the script at Window-->Preferences–> Web Browser

See https://support.xilinx.com/s/question/0D52E00006hpY4PSAU/vitishls-20202-not-starting-only-splash-screen-visibledead+link+2021-11-19 ⓘ

When you run /Xilinx_path/Vitis_HLS/yyyy.Q/bin/vitis_hls (the path of Vitis_HLS in *.Desktop file), you may get

/Xilinx_path/Vitis_HLS/yyyy.Q/bin/vitis_hls

****** Vitis HLS - High-Level Synthesis from C, C++ and OpenCL v2021.2 (64-bit)
  **** SW Build 3367213 on Tue Oct 19 02:47:39 MDT 2021
  **** IP Build 3369179 on Thu Oct 21 08:25:16 MDT 2021
    ** Copyright 1986-2021 Xilinx, Inc. All Rights Reserved.

source /opt/Xilinx/Vitis_HLS/2021.2/scripts/vitis_hls/hls.tcl -notrace
INFO: [HLS 200-10] Running '/opt/Xilinx/Vitis_HLS/2021.2/bin/unwrapped/lnx64.o/vitis_hls'
INFO: [HLS 200-10] For user 'username' on host 'hostname' (Linux_x86_64 version 5.14.16-arch1-1) on Sun Nov 07 21:57:50 CST 2021
INFO: [HLS 200-10] On os "Arch Linux"
INFO: [HLS 200-10] In directory '$HOME'
INFO: [HLS 200-10] Bringing up Vitis HLS GUI ...

Then it is stuck here or exit directly.

To fix this issue, first change the file /Xilinx_path/Vitis_HLS/yyyy.Q/common/scripts/autopilot_init.tcl line 40

from

----%r&-'%rl%&n__SUB_LEVEL_SECTION_8__amp;lt'v-=

to

----%r&-'%rl%&n__SUB_LEVEL_SECTION_8__amp;lt'v->

Then add

osgi.locking=none

to file

/Xilinx_path/Vitis_HLS/yyyy.Q/lnx64/tools/eclipse/configuration/config.ini

See https://support.xilinx.com/s/feed/0D52E00006hpUycSAE?language=en_US

You will need to recompile (just take the PKGBUILD from the abs) with . Instead of patching the system libc in , copy the newly compiled libpthread-2.25.so and libc-2.25.so to Do not forget to repeat this when gets upgraded.

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

Segmentation fault (core dumped) "$RDI_BINROOT"/unwrapped/"$RDI_PLATFORM$RDI_OPT_EXT"/rlwrap -rc -f "$RDI_APPROOT"/scripts/xsdb/xsdb/cmdlist -H "$HOME"/.xsctcmdhistory "$RDI_BINROOT"/loader -exec rdi_xsct "${RDI_ARGS[@]}"

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

To the following:

Vivado requires an older version of (2.26).

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

Run:

 # /opt/Xilinx/Vivado/2018.1/lnx64/tools/gcc/libexec/gcc/x86_64-unknown-linux-gnu/4.6.3/install-tools/mkheaders /opt/Xilinx/Vivado/2018.1/lnx64/tools/gcc

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

hs_err_pid*.log

#
# An unexpected error has occurred (11)
#
Stack:
/opt/Xilinx/Vivado/2018.2/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x923da9) [0x7fced0c19da9]
/opt/Xilinx/Vivado/2018.2/tps/lnx64/jre/lib/amd64/server/libjvm.so(JVM_handle_linux_signal+0xb6) [0x7fced0c203f6]
/opt/Xilinx/Vivado/2018.2/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x9209d3) [0x7fced0c169d3]
/usr/lib/libc.so.6(+0x368f0) [0x7fcf0ea408f0]
/opt/Xilinx/Vivado/2018.2/tps/lnx64/jre/lib/amd64/libawt_xawt.so(+0x42028) [0x7fceb1a20028]
/opt/Xilinx/Vivado/2018.2/tps/lnx64/jre/lib/amd64/libawt_xawt.so(+0x42288) [0x7fceb1a20288]
/opt/Xilinx/Vivado/2018.2/tps/lnx64/jre/lib/amd64/libawt_xawt.so(Java_sun_awt_X11_XRobotPeer_getRGBPixelsImpl+0x17c) [0x7fceb1a1867c]
[0x7fcec0cb94cf]

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

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

# ./xsetup -b Update

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

See

When editing an IP with Vivado 2021.2, Vivado may crash and report the following error:

This is due to a conflict between Vivado's and system's version of library.

A possible workaround is to force Vivado to use the system , by renaming the

# mv /opt/Xilinx/Vivado/2021.2/tps/lnx64/jre11.0.11_9/lib/libharfbuzz.so /opt/Xilinx/Vivado/2021.2/tps/lnx64/jre11.0.11_9/lib/libharfbuzz.so.bak

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

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

export LC_NUMERIC=en_US.UTF-8

to .

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 to the JVM options.

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

This is a common issue in a number of window managers. (DWM, Awesome, bspwm) Java does not play well with these window managers.

You run vitis:

$ /tools/Xilinx/Vitis/2022.2/bin/vitis

You get error messages here

This problem is due to libstdc++.so.6.

Make sure libstdc++.so.6 has been installed in your computer.

$ find /usr/lib -iname 'libstdc++.so.6'

Let's fix it:

# cd /tools/Xilinx/Vitis/2022.2/lib/lnx64.o/Default/
# mv libstdc++.so.6 libstdc++.so.6.bak
# ln -sf /usr/lib/libstdc++.so.6 ./libstdc++.so

Above way should solve this problem when you run Vitis.

Set the environment variable 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.

Generate a license file at https://www.xilinx.com/getlicense . You will shortly receive an automatically generated email with the license file . Download this to directory.