Xilinx Vivado Vitis 2020.1 Installation

Nase · 2020-06-14 02:22:01

Hi,

I am trying to run to run Xilinx's installer for Vivado and Vitis 2020.1. But it does not run. It always locks up.

Download Xilinx_Unified_2020.1_0602_1208_Lin64.bin from here: https://www.xilinx.com/member/forms/dow … _Lin64.bin
Then extract it like so: ./Xilinx_Unified_2020.1_0602_1208_Lin64.bin --target /tmp/Xilinx/ --noexec
Run the extracted setup executable: /tmp/Xilinx/xsetup

So xsetup will show, that the software is only supported on certain Linux versions. As usual, we don't care and click OK.
For a couple of seconds, the java executable does something. And then CPU usage drops to zero.
After that, I see a Java Windows in the taskbar, but it has no contents.

In the console there are the following messages:

$ /tmp/Xilinx/xsetup 
Exception in thread "SPLASH_LOAD_MESSAGE" java.lang.IllegalStateException: no splash screen available
        at java.desktop/java.awt.SplashScreen.checkVisible(Unknown Source)
        at java.desktop/java.awt.SplashScreen.getBounds(Unknown Source)
        at java.desktop/java.awt.SplashScreen.getSize(Unknown Source)
        at com.xilinx.installer.gui.H.run(Unknown Source)
Exception in thread "main" java.lang.IllegalStateException: no splash screen available
        at java.desktop/java.awt.SplashScreen.checkVisible(Unknown Source)
        at java.desktop/java.awt.SplashScreen.close(Unknown Source)
        at com.xilinx.installer.gui.G.b(Unknown Source)
        at com.xilinx.installer.gui.InstallerGUI.G(Unknown Source)
        at com.xilinx.installer.gui.InstallerGUI.e(Unknown Source)
        at com.xilinx.installer.api.InstallerLauncher.main(Unknown Source)

That's it. No log file that I know of, and no useful messages in the console. Starting with xsetup with --xdebug won't produce any more than the above.

Has anybody figured out how to get this working?

slimdog360 · 2020-06-14 13:11:24

I've been having the same problem and playing around trying to fix it since last night (I'm using Fedora 32 with openjdk 1.8.0_252).

The 2019.2 version works.
https://www.xilinx.com/support/download … 019-2.html

I tested Vivado 2020 on Centos 8 Stream & RHEL 8 and that works fine. They both use the same version of openjdk as what's installed on my Fedora 32.

I'm still playing around trying to fix it, but yeah it's a bit hard with a closed source program and no real debug output. My guess is that some java library was updated and now it's broke. I'm going to keep looking for a solution, but probably the fix will just be to wait 6-12 months for Xilinx to change something and it magically works.

I'll keep an eye on this thread, let me know if you find a solution.

Slithery · 2020-06-14 13:15:36

Have you tried the package in the AUR?

https://aur.archlinux.org/packages/vivado

slimdog360 · 2020-06-14 14:18:53

Slithery wrote:

Have you tried the package in the AUR?
https://aur.archlinux.org/packages/vivado

Oh cool, I didn't see that. But then (at least for me) there's also Xilinx Vitis which needs to work. But maybe the other packages fix everything. Thanks!

Nase · 2020-06-14 16:03:09

slimdog360 wrote:

They both use the same version of openjdk as what's installed on my Fedora 32.

Xilinx Installers (as well as the applications) come with their own JRE/JDK. They do not use the system's JDK. That's what I suspect is part of the issue.

Nase · 2020-06-14 16:11:15

Slithery wrote:

Have you tried the package in the AUR?
https://aur.archlinux.org/packages/vivado

I need Vitis and Vivado. Also, I don't want a full install, I just need the tools for certain processor types. To make things even more complicated, the Xilinx installers have a history of always installing Vivado alongside Vitis, one cannot deselect it, which could mean that an AUR package for Vitis is unlikely to happen. Last, but not least, I really don't like unpacking and recompressing roundabout 30GB to create a 30GB Arch package file. Sorry.

slimdog360 · 2020-06-14 20:51:13

Nase wrote:

slimdog360 wrote:
They both use the same version of openjdk as what's installed on my Fedora 32.
Xilinx Installers (as well as the applications) come with their own JRE/JDK. They do not use the system's JDK. That's what I suspect is part of the issue.

I think the system JRE is needed for the installer. Stock Fedora doesn't come with java, and it complains when trying to open the installer.

The error message when no java is installed

```
Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/selfgz2127011826/tps/lnx64/jre9.0.4/lib/libawt_xawt.so: libXtst.so.6: cannot open shared object file: No such file or directory
at java.base/java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.base/java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.base/java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.base/java.lang.Runtime.load0(Unknown Source)
at java.base/java.lang.System.load(Unknown Source)
at java.base/java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.base/java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.base/java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.base/java.lang.Runtime.loadLibrary0(Unknown Source)
at java.base/java.lang.System.loadLibrary(Unknown Source)
at java.desktop/java.awt.Toolkit$3.run(Unknown Source)
at java.desktop/java.awt.Toolkit$3.run(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.desktop/java.awt.Toolkit.loadLibraries(Unknown Source)
at java.desktop/java.awt.Toolkit.<clinit>(Unknown Source)
at java.desktop/java.awt.Component.<clinit>(Unknown Source)
at com.xilinx.installer.api.InstallerLauncher.main(Unknown Source)
```

slimdog360 · 2020-06-14 21:00:32

Someone from Japan had the same problem: https://sweetcafe.jp/?*20200605-142650

Nase · 2020-06-14 21:10:30

slimdog360 wrote:

Nase wrote:
slimdog360 wrote:
They both use the same version of openjdk as what's installed on my Fedora 32.
Xilinx Installers (as well as the applications) come with their own JRE/JDK. They do not use the system's JDK. That's what I suspect is part of the issue.
I think the system JRE is needed for the installer. Stock Fedora doesn't come with java, and it complains when trying to open the installer.
The error message when no java is installed

```
Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/selfgz2127011826/tps/lnx64/jre9.0.4/lib/libawt_xawt.so: libXtst.so.6: cannot open shared object file: No such file or directory
at java.base/java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.base/java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.base/java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.base/java.lang.Runtime.load0(Unknown Source)
at java.base/java.lang.System.load(Unknown Source)
at java.base/java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.base/java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.base/java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.base/java.lang.Runtime.loadLibrary0(Unknown Source)
at java.base/java.lang.System.loadLibrary(Unknown Source)
at java.desktop/java.awt.Toolkit$3.run(Unknown Source)
at java.desktop/java.awt.Toolkit$3.run(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.desktop/java.awt.Toolkit.loadLibraries(Unknown Source)
at java.desktop/java.awt.Toolkit.<clinit>(Unknown Source)
at java.desktop/java.awt.Component.<clinit>(Unknown Source)
at com.xilinx.installer.api.InstallerLauncher.main(Unknown Source)
```

The exceptions tells you, that the libawt_xawt.so which is part of the installer's JRE needs libXtst.so.6. By installing Fedora's JDK/JRE, you probably also installed this dependency. So that's why that error message is gone. But it has nothing to do with the installer using the system's JDK/JRE.

Nase · 2020-06-14 21:20:03

slimdog360 wrote:

Someone from Japan had the same problem: https://sweetcafe.jp/?*20200605-142650

Thanks for the link. Well, that person works around the problem by avoiding the GUI. That's a viable option. I should try that.

Also, I finally found where the installer puts the logfiles. My log file ends with "2020-06-14 23:14:47,943 INFO : com.xilinx.installer.gui.G:? - Started in: 40 Sec" with no errors prior to that. I think that it means the following: the installer has started, thinks that it has displayed the main window, but the installer's JRE is bad in a sense and doesn't work with Arch's X libraries.

slimdog360 · 2020-06-14 22:23:44

You've probably already seen this but, if you run the installer with

./Xilinx_Unified_2020.1_0602_1208_Lin64.bin --confirm

It will ask for confirmation at each step. It unzips the contents into the tmp folder

Verifying archive integrity... All good.
About to extract 40 KB in /tmp/selfgz2712931872 ... Proceed ? [Y/n] Y
Uncompressing Xilinx Installer...............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
OK to execute: ./xsetup   ? [Y/n]

So before executing the next step, I copied the files from

/tmp/selfgz2712931872

to my home dir. At least now there's some way to get the installer files and maybe find the issue. Or at least from here you can run xsetup in batch mode like the japanese link, without having to download that entire 35GB full installer.

Last edited by slimdog360 (2020-06-14 22:28:21)

Nase · 2020-06-14 22:57:19

I described how to unpack the installer in my first post. I used "--target /tmp/Xilinx/ --noexec" instead of "--confirm".

slimdog360 · 2020-06-14 22:59:52

Ok last one, it's working now. I'll admit I didn't 100% understand the japanese blog post. But now I do, it's simple to install (probably even easier than the gui).

./Xilinx_Unified_2020.1_0602_1208_Lin64.bin --noexec --target ~/xilinx-installer

This will extract the files to the ~/xilinx-installer directory. Go into that folder.

The next step is to enter you username & password, to generate a authentication token (required so you can download the program).

./xsetup -b AuthTokenGen

Then create a config file which will be used for installation later.

./xsetup -b ConfigGen

It asks a couple of basic questions, then tells you where the config file is stored. Open that config file and modify it how you need. It's in plain text, so is easy to modify.

Then finally install it.

./xsetup --batch Install --agree XilinxEULA,3rdPartyEULA,WebTalkTerms --location ~/Xilinx/Vivado --config "/path/to/.Xilinx/install_config.txt"

Running ./xsetup --help has lots of info in there and will show you what the flags mean.

--batch Install: will stop the gui installer
--agree XilinxEULA,3rdPartyEULA,WebTalkTerms : is for agreeing to the terms and conditions for those three things
--location ... : is where you want to install it
--config ... : is the location of the config file you generated

Pretty simple and it worked for me. Good luck.

Last edited by slimdog360 (2020-06-15 20:50:49)

pekon.gupta@gmail.com · 2020-08-01 23:55:24

Found the solution..

Step-1: Generate Authentication Token using batch mode
$LINUX> ./Xilinx_Unified_2020.1_0602_1208_Lin64.bin -- -b AuthToken
It will ask you for your Xilinx login/password.

Step-2: Generate batch mode configuration file
$LINUX> ./Xilinx_Unified_2020.1_0602_1208_Lin64.bin -- -b ConfigGen
Select your Product <Vitis/Vivado>
This will generate config file at $HOME/.Xilinx/install_config.txt

Step-3: Edit the config file
$LINUX> vi $HOME/.Xilinx/install_config.txt
# Choose the Products/Devices the you would like to install.
To reduce the download size, deselect FPGA devices which you do not want, by replacing '1'->'0' in front of FPGA family.

Step-4: Edit the config file
NOTE: This install requires 100GB of disk space. I really don't know why. So best is to install on a pen-drive, and then move installation directory to local hard-disk.
$LINUX> vi $HOME/.Xilinx/install_config.txt
# Path where Xilinx software will be installed.
Destination=/<path_to_your_disk_which_has_100GB_free>

Step-5: Install Vitis/Vivado
$LINUX> ./Xilinx_Unified_2020.1_0602_1208_Lin64.bin -- -a 3rdPartyEULA,WebTalkTerms,XilinxEULA -b Install -c $HOME/.Xilinx/install_config.txt

Hope this helps ...

- pekon

Last edited by pekon.gupta@gmail.com (2020-08-02 00:43:24)

Nase · 2020-08-02 00:00:22

Yes, I managed to install it.
Now, when I create projects, it goes into an infinite loop. Probably, some tool is started in the background and fails.

hawke · 2020-09-23 09:03:57

https://forums.xilinx.com/t5/Installati … 510#M29451

The installer has been tested on my arch OS.

1. backup your /usr/lib/os-release.

2. replace the file content with:

NAME="Ubuntu"
VERSION="18.04.3 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.3 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

3. run xsetup

4. restore os-release

Good luck.

GaKu999 · 2020-09-23 15:33:57

hawke wrote:

https://forums.xilinx.com/t5/Installati … 510#M29451
The installer has been tested on my arch OS.
1. backup your /usr/lib/os-release.
2. replace the file content with:
NAME="Ubuntu"
VERSION="18.04.3 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.3 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
3. run xsetup
4. restore os-release
Good luck.

Isn't it better just to unlink /etc/os-release, do the same thing, and relink later?
Also why that is hard dependent on Ubuntu?

Oh I see, java installer breakage...
Instead I recommend using batch mode because faking os-release doesn't always work according to the forum link you posted.

EDIT:

The solution was already said, and this thread is technically solved, just that OP vanished...

Last edited by GaKu999 (2020-09-23 15:36:00)

Freed · 2023-04-20 12:55:25

To make things even more complicated, the Xilinx installers have a history of always installing Vivado alongside Vitis, one cannot deselect it, which could mean that an AUR package for Vitis is unlikely to happen

If you installed vivado, you cannot install vitis due to

Program group entry, Xilinx Design Tools, already exists for 2022.2. Specify a different program group entry.

So if there exist a package `vitis` in AUR, it should contain `vivado`, which is conflict with pacakge `vivado`.

Arch Linux

#1 2020-06-14 02:22:01

Xilinx Vivado Vitis 2020.1 Installation

#2 2020-06-14 13:11:24

Re: Xilinx Vivado Vitis 2020.1 Installation

#3 2020-06-14 13:15:36

Re: Xilinx Vivado Vitis 2020.1 Installation

#4 2020-06-14 14:18:53

Re: Xilinx Vivado Vitis 2020.1 Installation

#5 2020-06-14 16:03:09

Re: Xilinx Vivado Vitis 2020.1 Installation

#6 2020-06-14 16:11:15

Re: Xilinx Vivado Vitis 2020.1 Installation

#7 2020-06-14 20:51:13

Re: Xilinx Vivado Vitis 2020.1 Installation

#8 2020-06-14 21:00:32

Re: Xilinx Vivado Vitis 2020.1 Installation

#9 2020-06-14 21:10:30

Re: Xilinx Vivado Vitis 2020.1 Installation

#10 2020-06-14 21:20:03

Re: Xilinx Vivado Vitis 2020.1 Installation

#11 2020-06-14 22:23:44

Re: Xilinx Vivado Vitis 2020.1 Installation

#12 2020-06-14 22:57:19

Re: Xilinx Vivado Vitis 2020.1 Installation

#13 2020-06-14 22:59:52

Re: Xilinx Vivado Vitis 2020.1 Installation

#14 2020-08-01 23:55:24

Re: Xilinx Vivado Vitis 2020.1 Installation

#15 2020-08-02 00:00:22

Re: Xilinx Vivado Vitis 2020.1 Installation

#16 2020-09-23 09:03:57

Re: Xilinx Vivado Vitis 2020.1 Installation

#17 2020-09-23 15:33:57

Re: Xilinx Vivado Vitis 2020.1 Installation

#18 2023-04-20 12:55:25

Re: Xilinx Vivado Vitis 2020.1 Installation

Board footer