Can't get the Xilinx cable drivers installed on SL6.1 (RHEL

[General Schvantzkoph]

Has anyone been able to get Impact or Chipscope working on SL6.1/CentOS6/
RHEL6?

It failed with the xsetup GUI but it only gave a useless error message
that it failed in the log.

When I tried to run the install script in

LabTools/LabTools/bin/lin64/install_script/install_drivers

I got a bunch of compile errors, apparently it's incompatible with a
2.6.32 kernel.

I also couldn't find libusb-driver in 13.2, the most recent copy that I
had was in 10.

 

[Steve]

On 09/15/2011 08:51 AM, General Schvantzkoph wrote:

Has anyone been able to get Impact or Chipscope working on SL6.1/CentOS6/
RHEL6?

It failed with the xsetup GUI but it only gave a useless error message
that it failed in the log.

When I tried to run the install script in

LabTools/LabTools/bin/lin64/install_script/install_drivers

I got a bunch of compile errors, apparently it's incompatible with a
2.6.32 kernel.

I also couldn't find libusb-driver in 13.2, the most recent copy that I
had was in 10.

I had a similar problem getting my Xilinx USB-JTAG cable working on
Fedora 13. I ended up using the open source Linux driver instead, works
fine:

http://rmdir.de/~michael/xilinx/

Steve Ecob
Silicon On Inspiration
Sydney Australia

 

[General Schvantzkoph]

On Thu, 15 Sep 2011 12:42:21 +1000, Steve wrote:

On 09/15/2011 08:51 AM, General Schvantzkoph wrote:
Has anyone been able to get Impact or Chipscope working on
SL6.1/CentOS6/ RHEL6?

It failed with the xsetup GUI but it only gave a useless error message
that it failed in the log.

When I tried to run the install script in

LabTools/LabTools/bin/lin64/install_script/install_drivers

I got a bunch of compile errors, apparently it's incompatible with a
2.6.32 kernel.

I also couldn't find libusb-driver in 13.2, the most recent copy that I
had was in 10.


I had a similar problem getting my Xilinx USB-JTAG cable working on
Fedora 13. I ended up using the open source Linux driver instead, works
fine:

http://rmdir.de/~michael/xilinx/

Steve Ecob
Silicon On Inspiration
Sydney Australia

I've already tried to build the libusb-driver but it won't build on SL6.1.

 

[Jan Pech]

Is there any particular reason to compile your own libusb instead of
using the distribution packages?

To make the Xilinx JTAG cable working in the RHEL/CentOS/SL 6.x do the
following stops. There is detailed description on my website
http://www.sensor-to-image.cz/doku.php?id=eda:xilinx but unfortunately
it is in Czech language only. Sorry.

1. Install and "fix" libusb:

yum install libusb libusb1 fxload
cd /usr/lib64 (or /usr/lib if you are running 32b system)
ln -s libusb-1.0.so.0.0.0 libusb.so

2. "Fix" the Xilinx cable setup script
<xilinx_install_dir>/ISE_DS/ISE/bin/lin64/setup_pcusb (or the same path
with lin instead of lin64) which does not detect udev correctly:

# Use udev always
#TP_USE_UDEV="0"
#TP_UDEV_ENABLED=`ps -e | grep -c udevd`
TP_USE_UDEV="1"
TP_UDEV_ENABLED="1"

3. Run the script from its directory:

cd <xilinx_install_dir>/ISE_DS/ISE/bin/lin64/setup_pcusb (or lin instead
of lin64)
../setup_pcusb

4. Generated udev rule uses wrong syntax. The rule for current version
of udev /etc/udev/rules.d/xusbdfwu.rules must look like this (long lines
must be retained, see my website for proper formatting):

# version 0003
ATTR{idVendor}=="03fd", ATTR{idProduct}=="0008", MODE="666"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="0007", RUN+="/sbin/fxload -v -t fx2 -I /usr/share/xusbdfwu.hex -D $tempnode"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="0009", RUN+="/sbin/fxload -v -t fx2 -I /usr/share/xusb_xup.hex -D $tempnode"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="000d", RUN+="/sbin/fxload -v -t fx2 -I /usr/share/xusb_emb.hex -D $tempnode"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="000f", RUN+="/sbin/fxload -v -t fx2 -I /usr/share/xusb_xlp.hex -D $tempnode"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="0013", RUN+="/sbin/fxload -v -t fx2 -I /usr/share/xusb_xp2.hex -D $tempnode"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="0015", RUN+="/sbin/fxload -v -t fx2 -I /usr/share/xusb_xse.hex -D $tempnode"

5. Connect/reconnect your cable, check dmesg, test iMPACT/ChipScope.

Regards,
Jan


Sorry if the post appears twice. I had some problems posting the
message.



On Thu, 2011-09-15 at 03:02 +0000, General Schvantzkoph wrote:

On Thu, 15 Sep 2011 12:42:21 +1000, Steve wrote:

On 09/15/2011 08:51 AM, General Schvantzkoph wrote:
Has anyone been able to get Impact or Chipscope working on
SL6.1/CentOS6/ RHEL6?

It failed with the xsetup GUI but it only gave a useless error message
that it failed in the log.

When I tried to run the install script in

LabTools/LabTools/bin/lin64/install_script/install_drivers

I got a bunch of compile errors, apparently it's incompatible with a
2.6.32 kernel.

I also couldn't find libusb-driver in 13.2, the most recent copy that I
had was in 10.


I had a similar problem getting my Xilinx USB-JTAG cable working on
Fedora 13. I ended up using the open source Linux driver instead, works
fine:

http://rmdir.de/~michael/xilinx/

Steve Ecob
Silicon On Inspiration
Sydney Australia

I've already tried to build the libusb-driver but it won't build on SL6.1..

 

[General Schvantzkoph]

On Thu, 15 Sep 2011 08:31:17 +0200, Jan Pech wrote:

Is there any particular reason to compile your own libusb instead of
using the distribution packages?

To make the Xilinx JTAG cable working in the RHEL/CentOS/SL 6.x do the
following stops. There is detailed description on my website
http://www.sensor-to-image.cz/doku.php?id=eda:xilinx but unfortunately
it is in Czech language only. Sorry.

1. Install and "fix" libusb:

yum install libusb libusb1 fxload
cd /usr/lib64 (or /usr/lib if you are running 32b system) ln -s
libusb-1.0.so.0.0.0 libusb.so

2. "Fix" the Xilinx cable setup script
xilinx_install_dir>/ISE_DS/ISE/bin/lin64/setup_pcusb (or the same path
with lin instead of lin64) which does not detect udev correctly:

# Use udev always
#TP_USE_UDEV="0"
#TP_UDEV_ENABLED=`ps -e | grep -c udevd` TP_USE_UDEV="1"
TP_UDEV_ENABLED="1"

3. Run the script from its directory:

cd <xilinx_install_dir>/ISE_DS/ISE/bin/lin64/setup_pcusb (or lin instead
of lin64)
./setup_pcusb

4. Generated udev rule uses wrong syntax. The rule for current version
of udev /etc/udev/rules.d/xusbdfwu.rules must look like this (long lines
must be retained, see my website for proper formatting):

# version 0003
ATTR{idVendor}=="03fd", ATTR{idProduct}=="0008", MODE="666"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd",
ATTR{idProduct}=="0007", RUN+="/sbin/fxload -v -t fx2 -I
/usr/share/xusbdfwu.hex -D $tempnode" SUBSYSTEM=="usb", ACTION=="add",
ATTR{idVendor}=="03fd", ATTR{idProduct}=="0009", RUN+="/sbin/fxload -v
-t fx2 -I /usr/share/xusb_xup.hex -D $tempnode" SUBSYSTEM=="usb",
ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="000d",
RUN+="/sbin/fxload -v -t fx2 -I /usr/share/xusb_emb.hex -D $tempnode"
SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="03fd",
ATTR{idProduct}=="000f", RUN+="/sbin/fxload -v -t fx2 -I
/usr/share/xusb_xlp.hex -D $tempnode" SUBSYSTEM=="usb", ACTION=="add",
ATTR{idVendor}=="03fd", ATTR{idProduct}=="0013", RUN+="/sbin/fxload -v
-t fx2 -I /usr/share/xusb_xp2.hex -D $tempnode" SUBSYSTEM=="usb",
ACTION=="add", ATTR{idVendor}=="03fd", ATTR{idProduct}=="0015",
RUN+="/sbin/fxload -v -t fx2 -I /usr/share/xusb_xse.hex -D $tempnode"

5. Connect/reconnect your cable, check dmesg, test iMPACT/ChipScope.

Regards,
Jan


Sorry if the post appears twice. I had some problems posting the
message.



On Thu, 2011-09-15 at 03:02 +0000, General Schvantzkoph wrote:
On Thu, 15 Sep 2011 12:42:21 +1000, Steve wrote:

On 09/15/2011 08:51 AM, General Schvantzkoph wrote:
Has anyone been able to get Impact or Chipscope working on
SL6.1/CentOS6/ RHEL6?

It failed with the xsetup GUI but it only gave a useless error
message that it failed in the log.

When I tried to run the install script in

LabTools/LabTools/bin/lin64/install_script/install_drivers

I got a bunch of compile errors, apparently it's incompatible with a
2.6.32 kernel.

I also couldn't find libusb-driver in 13.2, the most recent copy
that I had was in 10.


I had a similar problem getting my Xilinx USB-JTAG cable working on
Fedora 13. I ended up using the open source Linux driver instead,
works fine:

http://rmdir.de/~michael/xilinx/

Steve Ecob
Silicon On Inspiration
Sydney Australia

I've already tried to build the libusb-driver but it won't build on
SL6.1.

Thanks that worked.

 

[ngill]

Is there any particular reason to compile your own libusb instead of
using the distribution packages?

To make the Xilinx JTAG cable working in the RHEL/CentOS/SL 6.x do the
following stops. There is detailed description on my website
http://www.sensor-to-image.cz/doku.php?id=3Deda:xilinx but unfortunately
it is in Czech language only. Sorry.

1. Install and "fix" libusb:

yum install libusb libusb1 fxload
cd /usr/lib64 (or /usr/lib if you are running 32b system)
ln -s libusb-1.0.so.0.0.0 libusb.so

2. "Fix" the Xilinx cable setup script
xilinx_install_dir>/ISE_DS/ISE/bin/lin64/setup_pcusb (or the same path
with lin instead of lin64) which does not detect udev correctly:

# Use udev always
#TP_USE_UDEV=3D"0"
#TP_UDEV_ENABLED=3D`ps -e | grep -c udevd`
TP_USE_UDEV=3D"1"
TP_UDEV_ENABLED=3D"1"

3. Run the script from its directory:

cd <xilinx_install_dir>/ISE_DS/ISE/bin/lin64/setup_pcusb (or lin instead
of lin64)
./setup_pcusb

4. Generated udev rule uses wrong syntax. The rule for current version
of udev /etc/udev/rules.d/xusbdfwu.rules must look like this (long lines
must be retained, see my website for proper formatting):

# version 0003
ATTR{idVendor}=3D=3D"03fd", ATTR{idProduct}=3D=3D"0008", MODE=3D"666"
SUBSYSTEM=3D=3D"usb", ACTION=3D=3D"add", ATTR{idVendor}=3D=3D"03fd"
ATTR{i=
dProduct}=3D=3D"0007", RUN+=3D"/sbin/fxload -v -t fx2 -
/usr/share/xusbdfw=
u.hex -D $tempnode"
SUBSYSTEM=3D=3D"usb", ACTION=3D=3D"add", ATTR{idVendor}=3D=3D"03fd"
ATTR{i=
dProduct}=3D=3D"0009", RUN+=3D"/sbin/fxload -v -t fx2 -
/usr/share/xusb_xu=
p.hex -D $tempnode"
SUBSYSTEM=3D=3D"usb", ACTION=3D=3D"add", ATTR{idVendor}=3D=3D"03fd"
ATTR{i=
dProduct}=3D=3D"000d", RUN+=3D"/sbin/fxload -v -t fx2 -
/usr/share/xusb_em=
b.hex -D $tempnode"
SUBSYSTEM=3D=3D"usb", ACTION=3D=3D"add", ATTR{idVendor}=3D=3D"03fd"
ATTR{i=
dProduct}=3D=3D"000f", RUN+=3D"/sbin/fxload -v -t fx2 -
/usr/share/xusb_xl=
p.hex -D $tempnode"
SUBSYSTEM=3D=3D"usb", ACTION=3D=3D"add", ATTR{idVendor}=3D=3D"03fd"
ATTR{i=
dProduct}=3D=3D"0013", RUN+=3D"/sbin/fxload -v -t fx2 -
/usr/share/xusb_xp=
2.hex -D $tempnode"
SUBSYSTEM=3D=3D"usb", ACTION=3D=3D"add", ATTR{idVendor}=3D=3D"03fd"
ATTR{i=
dProduct}=3D=3D"0015", RUN+=3D"/sbin/fxload -v -t fx2 -
/usr/share/xusb_xs=
e.hex -D $tempnode"

5. Connect/reconnect your cable, check dmesg, test iMPACT/ChipScope.

Regards,
Jan


Sorry if the post appears twice. I had some problems posting the
message.

Jan,

Thanks for the tutorial. Im attempting to do the same thing wit
SL6.1/CentOS6/RHEL6 and the Xilinx 10.1.03 tools with no success. After
configure everything as you prescribe when I run impact and try to read th
jtag chain it bombs and says "Module windrvr6 is not loaded. Pleas
reinstall the cable drivers". Your solution should bypass the windrvr
module correct? Any idea why it would still be looking for it?

Thanks,
Nat



---------------------------------------
Posted through http://www.FPGARelated.com

 

[Jan Pech]

On Thu, 2012-01-12 at 06:45 -0600, ngill wrote:

Jan,

Thanks for the tutorial. Im attempting to do the same thing with
SL6.1/CentOS6/RHEL6 and the Xilinx 10.1.03 tools with no success. After I
configure everything as you prescribe when I run impact and try to read the
jtag chain it bombs and says "Module windrvr6 is not loaded. Please
reinstall the cable drivers". Your solution should bypass the windrvr6
module correct? Any idea why it would still be looking for it?

Thanks,
Nat



---------------------------------------
Posted through http://www.FPGARelated.com

Xilinx ISE version 10 uses the windrvr6 module by default. You have to
set the XIL_IMPACT_USE_LIBUSB environment variable to force the tools to
use the libusb. See http://www.xilinx.com/support/answers/29310.htm for
details.

Jan