Has anyone else experienced systems crashes caused by the Xilinx platform cable, it's happening to me a couple of times a day.
I'm using SL6.1 (RHEL 6.1 clone) and ISE 13.3. The scenario is that Chipscope can no longer see the JTAG chain. I exit out, try to clean things up with the following script, then restart Chipscope. When it tries to rescan the JTAG bus the system crashes (a real crash, I can't ping the box). In all of my years that I've been using Linux this is the only thing that's ever brought it down.
#!/bin/csh -f source ${HDLMAKER_LIB}/csh/xilinx.cshrc setenv XIL_IMPACT_USE_LIBUSB 1 udevadm trigger --attr-match=03fd impact -batch $HDLMAKER_LIB/csh/xilinx_unlock
I'm using the following rules file /etc/udev/rules.d/xusbdfwe.rules # 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"