Skip to content

Instantly share code, notes, and snippets.

@b-Tomas
Last active May 15, 2025 23:46
Show Gist options
  • Save b-Tomas/7452266bc0cf7c61119a8fe7f71f0a12 to your computer and use it in GitHub Desktop.
Save b-Tomas/7452266bc0cf7c61119a8fe7f71f0a12 to your computer and use it in GitHub Desktop.
Install Xilinx Vivado on Ubuntu Linux

Install Vivado 2024.2 on Ubuntu 24.04 LTS (and other distros)

Tested on:

  • Pop!_OS 24.10

Dependencies

# Vivado requires libtinfo5. Ubuntu comes with libtinfo6 but they are compatible enough.
# List libtinfo versions
ls /usr/lib/x86_64-linux-gnu/libtinfo.so*
# If libtinfo5 is not installed, create a symbolic link to libtinfo6
sudo ln -s /usr/lib/x86_64-linux-gnu/libtinfo.so.6 /usr/lib/x86_64-linux-gnu/libtinfo.so.5

Result:

❯ ls /usr/lib/x86_64-linux-gnu/libtinfo.so*
lrwxrwxrwx 1 root root     39 May 15 19:19 /usr/lib/x86_64-linux-gnu/libtinfo.so.5 -> /usr/lib/x86_64-linux-gnu/libtinfo.so.6
lrwxrwxrwx 1 root root     15 May 16  2023 /usr/lib/x86_64-linux-gnu/libtinfo.so.6 -> libtinfo.so.6.3
-rw-r--r-- 1 root root 200136 May 16  2023 /usr/lib/x86_64-linux-gnu/libtinfo.so.6.3

Installation steps

  1. Download the installer from the official website.
  2. Install:
chmod +x FPGAs_AdaptiveSoCs_Unified_2024.2_1113_1001_Lin64.bin
./FPGAs_AdaptiveSoCs_Unified_2024.2_1113_1001_Lin64.bin
  1. Log in with your AMD account.
  2. Select "Vivado" in the installer.
  3. Choose "Vivado ML Standard" in the installer.
  4. Additional components are optional. The default options require a download size of 23.37GB and an installation size of 85.39GB.

Post-installation

Once installed, the program can be executed with:

exec /tools/Xilinx/Vivado/2024.2/bin/vivado

This can be added to the PATH variable by adding the following line to your ~/.bashrc file:

cat << 'EOF' >> ~/.bashrc
# Vivado 2024.2 PATH configuration
export PATH=$PATH:/tools/Xilinx/Vivado/2024.2/bin
EOF

# Reload the .bashrc file to apply changes
exec bash

# Test the `vivado` command
which vivado
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment