Difference between revisions of "Xilinx ISE WebPACK"

From ArchWiki
Jump to: navigation, search
m
(according to my PC and https://www.archlinux.org/packages/extra/x86_64/jre7-openjdk/, path to libjvm.so does not include "-amd64")
(32 intermediate revisions by 14 users not shown)
Line 1: Line 1:
Xilinx ISE WebPACK is a complete design suite providing:
+
[[Category:Development]]
* specification of programmable logic, via schematic capture or verilog/VHDL
+
[[Category:Mathematics and science]]
* synthesis and fit of specified logic into Xilinx devices
+
The Xilinx ISE WebPACK is a complete FPGA/CPLD programmable logic design suite providing:
* behavioral and post-fit simulation  
+
* Specification of programmable logic via schematic capture or Verilog/VHDL
* download of configuration into target device via communications cable
+
* Synthesis and Place & Route of specified logic for various Xilinx FPGAs and CPLDs
* support for Linux based development system host
+
* Functional (Behavioral) and Timing (post-Place & Route) simulation
 +
* Download of configuration data into target device via communications cable
  
The ISE WebPACK version is downloadable:
+
While Arch Linux is not one of the officially supported distributions, many features are known to work on Arch Linux.
  
http://www.xilinx.com/support/download/index.htm
+
== Prerequisites ==
  
The download requires registration and licensing agreement, but there is no charge, i.e. it's free as in "Free Beer", but not free as in "Free Speech".
+
=== Dependencies ===
 +
If you plan to develop software for an embedded ARM core (e.g. for Xilinx Zynq SoC devices), you will want to install the GCC cross-compiler bundled included with the Xilinx Embedded Development Kit (EDK). This compiler requires the {{Pkg|glibc}} and {{Pkg|ncurses}} packages. For i686 installations, these will most likely be already present.
  
Make sure you select the Linux version.
+
If you are on a 64-bit Arch installation, you need to install them from the [[multilib]] repository ({{Pkg|lib32-glibc}} and {{Pkg|lib32-ncurses}}).
  
There are a couple of very helpful howto's at Gentoo:
+
=== Default Shell ===
 +
During the installation, the Mentor CodeSourcery toolchains for embedded processors can be installed along with the Xilinx tools. This installation silently fails when the default shell is set to "dash". Make sure {{ic|/usr/bin/sh}} points to {{ic|/usr/bin/bash}}.
  
http://gentoo-wiki.com/Talk:HOWTO_Xilinx/Archive_1
+
This can be checked by running this command:
 +
$ ls -l /usr/bin/sh
  
http://gentoo-wiki.com/HOWTO_Xilinx
+
If the output looks like this:
 +
{{ic|lrwxrwxrwx 1 root root 15 13 Mar 06:47 /usr/bin/sh -> bash}}
 +
then {{ic|/usr/bin/sh}} already points to {{ic|/usr/bin/bash}} (the default in Arch Linux).
  
This is a Xilinx tip for usb install on Linux:
+
If not, run the following commands as root:
 +
$ rm /usr/bin/sh
 +
$ ln -s bash /usr/bin/sh
  
http://www.xilinx.com/support/answers/22648.htm
+
== Installation ==
 +
{{Note|The installation is last known to work with Xilinx ISE 14.6, requiring the dynamic library fix described below.}}
  
I used, and recommend, the "Download Files Individually" option, once you reach the download page. This downloads the entire installer and installation is performed afterward.
+
The ISE Design Tools can be downloaded from [http://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/design-tools.html the official download page]. It requires registration and licensing agreement, but there is no charge, i.e. it's free as in "free beer", but not free as in "free speech".
  
Xilinx only provides official support for redhat and suse distributions, but I found the initial install of ISE to go smoothly on archlinux with kernel-headers 2.6.24.3-1.
+
Once the tarballs has been downloaded, unpack it:
 +
$ tar -xvf Xilinx_ISE_DS_14.6_P.68d_3.tar
  
I first installed ISE WebPACK for Linux version 9.2i, but 10.1 was released shortly thereafter. I was pleased to see this updated version was available for linux at the same time as 10.1 for windoze.
+
The ISE design tools installer is a Qt application. If you are running the KDE desktop environment, the installer may try to load the "Oxygen" widget theme, which will fail due to the older Qt framework bundled with the Xilinx ISE design tools. You need to remove the {{ic|QT_PLUGIN_PATH}} environment variable before executing the installer:
 +
$ unset QT_PLUGIN_PATH
  
After installation, ISE worked fine for design capture, synthesis and simulation. However once I reached the point of trying to download a design to a target device I ran into some trouble. Installing the cable drivers for talking to the target interface cable yielded errors.
+
Then, install the ISE Design Tools:
 +
$ cd Xilinx_ISE_DS_14.6_P.68d_3
 +
$ ./xsetup
  
I downloaded the standalone driver installation utility from:
+
Follow the instructions to install the ISE. By default, the whole application is installed to {{ic|/opt/Xilinx/}}, so make sure the user running the installer has permissions to write to this directory.
  
ftp://ftp.xilinx.com/pub/utilities/fpga/install_drivers.tar.gz
+
During installation, uncheck the "Install Cable Drivers" option. Leaving it checked will cause errors during the installation.
  
This download yields a file named install_drivers.tar.gz
+
=== Launching the ISE design tools ===
 +
The ISE design tools include a shell script that modifies the environment variables (mostly PATH and LD_LIBRARY_PATH). This script must be sourced before starting the ISE tools:
 +
$ source /opt/Xilinx/14.6/ISE_DS/settings64.sh
 +
or, for a 32-bit installation:
 +
$ source /opt/Xilinx/14.6/ISE_DS/settings32.sh
  
tar xzf install_drivers.tar.gz
+
Then, the ISE design tools will be found in your PATH and can be started by typing their name in the terminal (e.g. {{ic|ise}}, {{ic|planAhead}}, {{ic|xsdk}}, ...)
  
yields a directory named install_drivers/ When I attempted to build the drivers from this file I encountered the following errors:
+
=== License Installation ===
 +
After requesting a WebPACK license from Xilinx using their [http://www.xilinx.com/getlicense/ Licensing Site], you will be e-mailed a license file. This file can be imported with the Xilinx License Manager (run {{ic|xlcm -manage}} from the terminal).
  
'''linux_wrappers.c:48:31: error: linux/ioctl32.h: No such file or directory'''
+
Another way to import the license is to simply copy it to the {{ic|~/.Xilinx}} directory.
  
and
+
=== Node-Locked Licenses ===
 +
Arch Linux by default uses systemd's [[Network_Configuration#Device_names|Predictable Network Interface Names]]. This means that your system will most likely not have its network interfaces named "eth0", "eth1" and so forth.
  
'''linux_wrappers.c:1398: error: ‘struct scatterlist’ has no member named ‘page’'''
+
However, the Xilinx License Manager looks for these names to find out the system's MAC addresses, which are used for node-locked licenses. If you require node-locked licenses, you might have to disable this feature to re-gain the kernel naming scheme for network interfaces. The [http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames systemd wiki] describes how to do this.
  
Reading in the gentoo howto's listed above led me to download the latest Jungo source code, which is the core of the Xilinix linux USB support. I modified the link after reading that the latest Jungo driver was 9.20. I got WinDriver 9.20 from:
+
== Post-Installation Fixes and Tweaks ==
 +
After installation, a few manual fixes are required to work around problems caused by running the Xilinx tools on a Linux distribution that is not officially supported by Xilinx. Some of these fixes are taken from [http://zedboard.org/content/ise-142-bug-reports this forum post.]
  
http://www.jungo.com/st/download/WD920LN.tgz
+
=== Dynamic Library Fix (libstdc++.so) ===
 +
The ISE tools supply an outdated version of the libstdc++.so library, which may cause segfaults when using the Xilinx Microprocessor Debugger and prevents the usage of the oxygen-gtk theme. This outdated version is located in two directories within the installation tree: {{ic|/opt/Xilinx/14.6/ISE_DS/ISE/lib/lin64/}} and {{ic|/opt/Xilinx/14.6/ISE_DS/common/lib/lin64}}. To use Arch's newer version of libstdc++, rename or delete the original files and replace them with symlinks:
 +
# cd /opt/Xilinx/14.6/ISE_DS/ISE/lib/lin64/
 +
# mv libstdc++.so libstdc++.so-orig
 +
# mv libstdc++.so.6 libstdc++.so.6-orig
 +
# mv libstdc++.so.6.0.8 libstdc++.so.6.0.8-orig
 +
# ln -s /usr/lib/libstdc++.so
 +
# ln -s libstdc++.so libstdc++.so.6
 +
# ln -s libstdc++.so libstdc++.so.6.0.8
  
tar xzg WD920LN.tgz
+
Then, repeat this process in the {{ic|/opt/Xilinx/14.6/ISE_DS/common/lib/lin64}} directory.
  
yields a directory named WinDriver/ Within this directory you'll find:
+
=== Digilent USB-JTAG Drivers ===
 +
To use Digilent Adept USB-JTAG adapters (e.g. the onboard JTAG adapter on the [http://www.zedboard.org ZedBoard]) from within the Xilinx design tools, you need to install the Digilent [http://www.digilentinc.com/Products/Detail.cfm?Prod=ADEPT2 Adept Runtime] and [http://www.digilentinc.com/Products/Detail.cfm?Prod=DIGILENT-PLUGIN Plugin].
  
ls WinDriver/redist/
+
To install the Digilent Adept Runtime, it is recommended to build and install {{AUR|adept-runtime-xilinx}} and its dependencies {{AUR|libftd2xx-digilent}} and {{AUR|usbdrv}} from the [[Arch User Repository]].
+
configure*      linux_wrappers.c  makefile.in      wdreg*            wdusb_linux.c    windrvr_gcc_v3.a
+
linux_common.h  linux_wrappers.h  setup_inst_dir*  wdusb_interface.h  windrvr_gcc_v2.a  windrvr_gcc_v3_regparm.a
+
  
These are the same core files also found in:
+
To install the Digilent plugin, you have to copy two files to the ISE plugin directory. Run the following commands as root:
 +
$ mkdir -p /opt/Xilinx/14.6/ISE_DS/ISE/lib/lin64/plugins/Digilent/libCseDigilent
 +
$ cd /opt/Xilinx/14.6/ISE_DS/ISE/bin/lin64/digilent/libCseDigilent_2.4.4-x86_64/lin64/14.1/libCseDigilent
 +
$ cp libCseDigilent.{so,xml} /opt/Xilinx/14.6/ISE_DS/ISE/lib/lin64/plugins/Digilent/libCseDigilent
 +
$ chmod -x /opt/Xilinx/14.6/ISE_DS/ISE/lib/lin64/plugins/Digilent/libCseDigilent/libCseDigilent.xml
  
ls install_drivers/linux_drivers/windriver32/windrvr/
+
Finally, add every user that should have access to the Digilent USB-JTAG adapter to the "uucp" group.
+
config.cache    LINUX.2.6.24-ARCH.i386/  makefile        wdusb_interface.h  windrvr_gcc_v3_regparm.a
+
config.log      linux_common.h          makefile.in      wdusb_linux.c
+
config.status*  linux_wrappers.c        setup_inst_dir*  windrvr_gcc_v2.a
+
configure*      linux_wrappers.h        wdreg*          windrvr_gcc_v3.a
+
  
So I copied the 9.20 WinDriver files over those found in the install_drivers/ subdirectory:
+
You may have to add the USB Vendor/Product IDs of your JTAG adapter to the udev rules in {{ic|/etc/udev/rules.d/20-digilent.rules}}.
  
  cp -p WinDriver/redist/* install_drivers/linux_drivers/windriver32/windrvr/
+
=== Locale Issues ===
 +
PlanAhead doesn't like locales using other literals than '.' as the decimal point (e.g. German, which uses ','). Run the following command before launching PlanAhead:
 +
  $ unset LANG
  
This update to the Jungo driver eliminated the error: linux/ioctl32.h: No such file or directory, but the error: ‘struct scatterlist’ has no member named ‘page’ was still persisting.
+
=== Segmentation Fault on PlanAhead ===
 +
When launching PlanAhead to generate a .ucf file, a segmentation fault may occur. The issue seems unrelated to the previous topic. The ISE console will show
 +
"/opt/Xilinx/13.1/ISE_DS/PlanAhead/bin/rdiArgs.sh: line 64: 14275 Segmentation fault      $RDI_PROG $*"
 +
The problem seems to come from the bundled JRE as described [http://forums.xilinx.com/t5/Installation-and-Licensing/RHEL5-64-bit-ISE-13-1-PlanAhead-launch-from-w-in-ISE-fails/td-p/148624/page/2 here]. To fix the issue, symlink the OpenJDK libjvm.so into the Xilinx's installation directory.
 +
# cd /opt/Xilinx/14.6/ISE_DS/PlanAhead/tps/lnx64/jre/lib/amd64/server
 +
# mv libjvm.so{,-orig}
 +
# ln -s /usr/lib/jvm/java-7-openjdk/jre/lib/amd64/server/libjvm.so
  
After research regarding changes to scatterlist.h lead to these discussions:
+
=== GNU make ===
 +
XSDK looks for the {{ic|gmake}} executable, which is not present in Arch Linux by default. Create a symlink somewhere in your path, e.g.
 +
$ ln -s /usr/bin/make /home/<user>/bin/gmake
  
http://kerneltrap.org/Linux/SG_Chaining_Merged
+
Make sure this directory is in your PATH variable.
  
Which describe changes in scatter/gather lists that were implemented in kernel 2.6.23 in Oct/Nov 2007.
+
=== Running Xilinx tools from within KDE ===
 +
KDE by default defines the QT_PLUGIN_PATH shell variable. Some of the Xilinx ISE tools (ISE, Impact, XPS) are Qt applications, which means that they will search for Qt plugins in the locations defined by this shell variable.
  
I implemented the following:
+
Because the Xilinx tools are compiled against and ship with an older version of the Qt framework which cannot use these plugins, they will crash when launched with this environment variable present.
  
cd before/install_drivers/linux_drivers/windriver32/windrvr/
+
To fix this issue, run the following command before launching the tools:
  
and apply the patch indicated below to linux_wrappers.c:
+
  $ unset QT_PLUGIN_PATH
 
+
  diff -r before/install_drivers/linux_drivers/windriver32/windrvr/linux_wrappers.c  \
+
          after/install_drivers/linux_drivers/windriver32/windrvr/linux_wrappers.c
+
61c61
+
<
+
---
+
>
+
124a125,127
+
> /* added to fix scatterlist without page compile bug -jea 2008-05-09 */
+
> // #include <linux/scatterlist.h>
+
>
+
1791c1794
+
<    sgl[0].page = pages[0];
+
---
+
>    sgl[0].page_link = (unsigned long)pages[0];
+
1798c1801
+
<            sgl[i].page = pages[i];
+
---
+
>            sgl[i].page_link = (unsigned long)pages[i];
+
1823c1826
+
<        void *va = page_address(sgl[i].page) + sgl[i].offset;
+
---
+
>        void *va = page_address((struct page *)sgl[i].page_link) + sgl[i].offset;
+
1954,1956c1957,1959
+
<        if (!PageReserved(sgl[i].page))
+
<            SetPageDirty(sgl[i].page);
+
<        page_cache_release(sgl[i].page);
+
---
+
>        if (!PageReserved((struct page *)sgl[i].page_link))
+
>            SetPageDirty((struct page *)sgl[i].page_link);
+
>        page_cache_release((struct page *)sgl[i].page_link);
+
 
+
or, viewed as a unified patch:
+
 
+
--- before/install_drivers/linux_drivers/windriver32/windrvr/linux_wrappers.c  2008-02-19 09:58:43.000000000  -0800
+
+++ after/install_drivers/linux_drivers/windriver32/windrvr/linux_wrappers.c    2008-05-15 20:02:23.000000000  -0700
+
@@ -122,6 +122,9 @@
+
      static struct pci_dev *pci_root_dev;
+
  #endif
+
+
+/* added to fix scatterlist without page compile bug -jea 2008-05-09 */
+
+// #include <linux/scatterlist.h>
+
+
+
  typedef struct
+
  {
+
      struct page **pages;
+
@@ -1788,14 +1791,14 @@
+
+
      memset (sgl, 0, sizeof(struct scatterlist) * page_count);
+
      sgl[0].offset = ((unsigned long)buf) & (~PAGE_MASK);
+
-    sgl[0].page = pages[0];
+
+    sgl[0].page_link = (unsigned long)pages[0];
+
      if (page_count > 1)
+
      {
+
          sgl[0].length = PAGE_SIZE - sgl[0].offset;
+
          size -= sgl[0].length;
+
          for (i=1; i < page_count ; i++, size -= PAGE_SIZE)
+
          {
+
-            sgl[i].page = pages[i];
+
+            sgl[i].page_link = (unsigned long)pages[i];
+
              sgl[i].length = size < PAGE_SIZE ? size : PAGE_SIZE;
+
          }
+
      }
+
@@ -1820,7 +1823,7 @@
+
      for (i=0; i<*dma_sglen; i++)
+
      {
+
  #if defined(_CONFIG_SWIOTLB)
+
-        void *va = page_address(sgl[i].page) + sgl[i].offset;
+
+        void *va = page_address((struct page *)sgl[i].page_link) + sgl[i].offset;
+
          dma_addr_t dma_addr = virt_to_phys(va);
+
+
          if (dma_addr & ~mask)
+
@@ -1951,9 +1954,9 @@
+
  #if defined(_CONFIG_SWIOTLB)
+
          pci_unmap_single(dev_handle, sg_dma_address(&sgl[i]), sg_dma_len(&sgl[i]), (int)dma_direction);
+
  #endif
+
-        if (!PageReserved(sgl[i].page))
+
-            SetPageDirty(sgl[i].page);
+
-        page_cache_release(sgl[i].page);
+
+        if (!PageReserved((struct page *)sgl[i].page_link))
+
+            SetPageDirty((struct page *)sgl[i].page_link);
+
+        page_cache_release((struct page *)sgl[i].page_link);
+
      }
+
      vfree(sgl);
+
  #elif defined(LINUX_24)
+
 
+
This corrected the compile errors in the Jungo USB driver and produced the windrvr6.ko kernel module. However there was still a nagging error in the compilation of install_drivers/linux_drivers/xpc4drvr2_6/xpc4drvr/ which was corrected by the following brutal hack to the Makefile:
+
 
+
diff before/install_drivers/linux_drivers/xpc4drvr2_6/xpc4drvr/  \
+
      after/install_drivers/linux_drivers/xpc4drvr2_6/xpc4drvr/
+
+
25c25
+
< ifeq ($(GET_USER_SIZE_SYM),0)
+
---
+
> #ifeq ($(GET_USER_SIZE_SYM),)
+
27c27
+
< endif
+
---
+
> #endif
+
 
+
This corrected all compilation errors, but the xpc4drvr.ko still yielded the following error in /var/log/everything.log whenever it was attempted to be loaded:
+
 
+
xpc4drvr: Unknown symbol get_user_size
+
 
+
However this did allow compilation of the entire driver tree and the install script was able to successfully install the drivers via:
+
 
+
cd install_drivers/
+
./install_drivers
+
 
+
There is also a udev rule entry that will make the driver accessible to all users after each reboot. (Which I haven't yet applied)
+
 
+
So after this brief modification, I am able to successfully run ISE on ArchLinux-2.6.24 with full USB cable support.
+
 
+
There is a GPL'd libusb based driver mentioned in the Gentoo docs:
+
 
+
http://www.rmdir.de/~michael/xilinx/
+
 
+
that I was particularly interested in using. However while the source built without error, I continued to receive runtime errors when attempting to run it in ISE.
+
 
+
I never attempted to use the Xup driver.
+
 
+
There were quite a few pertinent facts along the way that I'm failing to capture here. Such as the fact that I discovered the same directory:
+
 
+
install_drivers/
+
 
+
in the base install of the entire ISE package under:
+
 
+
/opt/Xilinx/10.1/common/bin/lin/install_script/install_drivers/
+
 
+
I would expect that this procedure could be applied directly to that without the additional step of downloading the install_drivers.tar.gz but I haven't tried this.
+
 
+
All in all this is the crux of what was necessary for me to get the USB support running on Arch.
+

Revision as of 20:11, 6 October 2013

The Xilinx ISE WebPACK is a complete FPGA/CPLD programmable logic design suite providing:

  • Specification of programmable logic via schematic capture or Verilog/VHDL
  • Synthesis and Place & Route of specified logic for various Xilinx FPGAs and CPLDs
  • Functional (Behavioral) and Timing (post-Place & Route) simulation
  • Download of configuration data into target device via communications cable

While Arch Linux is not one of the officially supported distributions, many features are known to work on Arch Linux.

Prerequisites

Dependencies

If you plan to develop software for an embedded ARM core (e.g. for Xilinx Zynq SoC devices), you will want to install the GCC cross-compiler bundled included with the Xilinx Embedded Development Kit (EDK). This compiler requires the glibc and ncurses packages. For i686 installations, these will most likely be already present.

If you are on a 64-bit Arch installation, you need to install them from the multilib repository (lib32-glibc and lib32-ncurses).

Default Shell

During the installation, the Mentor CodeSourcery toolchains for embedded processors can be installed along with the Xilinx tools. This installation silently fails when the default shell is set to "dash". Make sure /usr/bin/sh points to /usr/bin/bash.

This can be checked by running this command:

$ ls -l /usr/bin/sh

If the output looks like this:

lrwxrwxrwx 1 root root 15 13 Mar 06:47 /usr/bin/sh -> bash

then /usr/bin/sh already points to /usr/bin/bash (the default in Arch Linux).

If not, run the following commands as root:

$ rm /usr/bin/sh
$ ln -s bash /usr/bin/sh

Installation

Note: The installation is last known to work with Xilinx ISE 14.6, requiring the dynamic library fix described below.

The ISE Design Tools can be downloaded from the official download page. It requires registration and licensing agreement, but there is no charge, i.e. it's free as in "free beer", but not free as in "free speech".

Once the tarballs has been downloaded, unpack it:

$ tar -xvf Xilinx_ISE_DS_14.6_P.68d_3.tar

The ISE design tools installer is a Qt application. If you are running the KDE desktop environment, the installer may try to load the "Oxygen" widget theme, which will fail due to the older Qt framework bundled with the Xilinx ISE design tools. You need to remove the QT_PLUGIN_PATH environment variable before executing the installer:

$ unset QT_PLUGIN_PATH

Then, install the ISE Design Tools:

$ cd Xilinx_ISE_DS_14.6_P.68d_3
$ ./xsetup

Follow the instructions to install the ISE. By default, the whole application is installed to /opt/Xilinx/, so make sure the user running the installer has permissions to write to this directory.

During installation, uncheck the "Install Cable Drivers" option. Leaving it checked will cause errors during the installation.

Launching the ISE design tools

The ISE design tools include a shell script that modifies the environment variables (mostly PATH and LD_LIBRARY_PATH). This script must be sourced before starting the ISE tools:

$ source /opt/Xilinx/14.6/ISE_DS/settings64.sh

or, for a 32-bit installation:

$ source /opt/Xilinx/14.6/ISE_DS/settings32.sh

Then, the ISE design tools will be found in your PATH and can be started by typing their name in the terminal (e.g. ise, planAhead, xsdk, ...)

License Installation

After requesting a WebPACK license from Xilinx using their Licensing Site, you will be e-mailed a license file. This file can be imported with the Xilinx License Manager (run xlcm -manage from the terminal).

Another way to import the license is to simply copy it to the ~/.Xilinx directory.

Node-Locked Licenses

Arch Linux by default uses systemd's Predictable Network Interface Names. This means that your system will most likely not have its network interfaces named "eth0", "eth1" and so forth.

However, the Xilinx License Manager looks for these names to find out the system's MAC addresses, which are used for node-locked licenses. If you require node-locked licenses, you might have to disable this feature to re-gain the kernel naming scheme for network interfaces. The systemd wiki describes how to do this.

Post-Installation Fixes and Tweaks

After installation, a few manual fixes are required to work around problems caused by running the Xilinx tools on a Linux distribution that is not officially supported by Xilinx. Some of these fixes are taken from this forum post.

Dynamic Library Fix (libstdc++.so)

The ISE tools supply an outdated version of the libstdc++.so library, which may cause segfaults when using the Xilinx Microprocessor Debugger and prevents the usage of the oxygen-gtk theme. This outdated version is located in two directories within the installation tree: /opt/Xilinx/14.6/ISE_DS/ISE/lib/lin64/ and /opt/Xilinx/14.6/ISE_DS/common/lib/lin64. To use Arch's newer version of libstdc++, rename or delete the original files and replace them with symlinks:

# cd /opt/Xilinx/14.6/ISE_DS/ISE/lib/lin64/
# mv libstdc++.so libstdc++.so-orig
# mv libstdc++.so.6 libstdc++.so.6-orig
# mv libstdc++.so.6.0.8 libstdc++.so.6.0.8-orig
# ln -s /usr/lib/libstdc++.so
# ln -s libstdc++.so libstdc++.so.6
# ln -s libstdc++.so libstdc++.so.6.0.8

Then, repeat this process in the /opt/Xilinx/14.6/ISE_DS/common/lib/lin64 directory.

Digilent USB-JTAG Drivers

To use Digilent Adept USB-JTAG adapters (e.g. the onboard JTAG adapter on the ZedBoard) from within the Xilinx design tools, you need to install the Digilent Adept Runtime and Plugin.

To install the Digilent Adept Runtime, it is recommended to build and install adept-runtime-xilinxAUR and its dependencies libftd2xx-digilentAUR and usbdrvAUR from the Arch User Repository.

To install the Digilent plugin, you have to copy two files to the ISE plugin directory. Run the following commands as root:

$ mkdir -p /opt/Xilinx/14.6/ISE_DS/ISE/lib/lin64/plugins/Digilent/libCseDigilent
$ cd /opt/Xilinx/14.6/ISE_DS/ISE/bin/lin64/digilent/libCseDigilent_2.4.4-x86_64/lin64/14.1/libCseDigilent
$ cp libCseDigilent.{so,xml} /opt/Xilinx/14.6/ISE_DS/ISE/lib/lin64/plugins/Digilent/libCseDigilent
$ chmod -x /opt/Xilinx/14.6/ISE_DS/ISE/lib/lin64/plugins/Digilent/libCseDigilent/libCseDigilent.xml

Finally, add every user that should have access to the Digilent USB-JTAG adapter to the "uucp" group.

You may have to add the USB Vendor/Product IDs of your JTAG adapter to the udev rules in /etc/udev/rules.d/20-digilent.rules.

Locale Issues

PlanAhead doesn't like locales using other literals than '.' as the decimal point (e.g. German, which uses ','). Run the following command before launching PlanAhead:

$ unset LANG

Segmentation Fault on PlanAhead

When launching PlanAhead to generate a .ucf file, a segmentation fault may occur. The issue seems unrelated to the previous topic. The ISE console will show

"/opt/Xilinx/13.1/ISE_DS/PlanAhead/bin/rdiArgs.sh: line 64: 14275 Segmentation fault      $RDI_PROG $*"

The problem seems to come from the bundled JRE as described here. To fix the issue, symlink the OpenJDK libjvm.so into the Xilinx's installation directory.

# cd /opt/Xilinx/14.6/ISE_DS/PlanAhead/tps/lnx64/jre/lib/amd64/server
# mv libjvm.so{,-orig}
# ln -s /usr/lib/jvm/java-7-openjdk/jre/lib/amd64/server/libjvm.so

GNU make

XSDK looks for the gmake executable, which is not present in Arch Linux by default. Create a symlink somewhere in your path, e.g.

$ ln -s /usr/bin/make /home/<user>/bin/gmake

Make sure this directory is in your PATH variable.

Running Xilinx tools from within KDE

KDE by default defines the QT_PLUGIN_PATH shell variable. Some of the Xilinx ISE tools (ISE, Impact, XPS) are Qt applications, which means that they will search for Qt plugins in the locations defined by this shell variable.

Because the Xilinx tools are compiled against and ship with an older version of the Qt framework which cannot use these plugins, they will crash when launched with this environment variable present.

To fix this issue, run the following command before launching the tools:

$ unset QT_PLUGIN_PATH