| Git Clone URL: | https://aur.archlinux.org/vivado.git (read-only, click to copy) |
|---|---|
| Package Base: | vivado |
| Description: | FPGA/CPLD design suite for AMD devices – Vivado edition |
| Upstream URL: | https://www.xilinx.com/products/design-tools/vivado.html |
| Licenses: | custom |
| Conflicts: | vitis |
| Submitter: | xiretza |
| Maintainer: | VitalyR (leuko) |
| Last Packager: | leuko |
| Votes: | 17 |
| Popularity: | 0.031913 |
| First Submitted: | 2019-06-18 22:23 (UTC) |
| Last Updated: | 2024-11-20 22:25 (UTC) |
You don't actually have to download the entire (now over 100 GiB) unified installer.
The self-extracting web installer (~300 MiB) can create a customised bundle identical to the unified installer - thus only downloading the components you require.
I've written down what I did to install Vivado and support for Artix 7 only in this gist.
I am against including 2023.2.2 patch in the PKGBUILD. This is only a patch for newer devices. I guess less than 10% of the package users need this patch. (So I unflagged the package.)
From the installation page:
...
For customers using these devices, AMD recommends installing Vivado 2023.2.{1,2} For other devices, please continue to use Vivado ML 2023.2.
@Lacsapix and @miree Can confirm. After "pacman -Syu" Vivado keeps crashing during synthesis with the Seg Fault mentiones. Can also confirm that 2023.2 and 2023.1 have this problem (with or without the license environment variables), while 2022.2 works as usual.
@Lacsapix
I had the same issue today trying to use vivado (older version 2023.1, not latest 2023.2) after a recent "pacman -Syu".
The segfault disappears when I don't set LM_LICENSE_FILE and XILINXD_LICENSE_FILE environment variables.
Hi everyone! After yesterdays "pacman -Syu" I keep getting the same error during synthesis: "/opt/Xilinx/Vivado/2023.2/bin/rdiArgs.sh: line 369: 33600 Segmentation fault (core dumped) "$RDI_PROG" "$@""
Line 369 in rdiArgs.sh is the following if function:
RDI_EXEC_COMMANDS() {
if [ -f $RDI_PROG ]; then
"$RDI_PROG" "$@"
fi
return
}
Vivado 2022.2 seems to be working great, its just 2023.2. Is anyone else having this same issue or is this just a me-problem?
Unable to install package facing the following problem:
-> Downloading FPGAs_AdaptiveSoCs_Unified_2023.2_1013_2256.tar.gz...
curl: (37) Couldn't open file /FPGAs_AdaptiveSoCs_Unified_2023.2_1013_2256.tar.gz
==> ERROR: Failure while downloading file:///FPGAs_AdaptiveSoCs_Unified_2023.2_1013_2256.tar.gz
Updated the package to fix _srcname=FPGAs_AdaptiveSoCs_Unified. I did not increment the package version to avoid unnecessary repackaging.
Thanks VitalyR, I will update the package until the end of next week.
Pinned Comments
leuko commented on 2024-01-14 21:14 (UTC) (edited on 2024-09-26 06:41 (UTC) by leuko)
PKGBUILDcannot download Vivado, you have to download Vivado before executing thePKGBUILD. Refer toPKGBUILD.This
PKGBUILDis also able to install Vitis with some errors, however there is a standalone package called vitis AUR which seems to be more advanced than the installation in thisPKGBUILD.