Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Xilinx USB programmer - problems with Debian/Linux - Solved

78 views
Skip to first unread message

wzab

unread,
Oct 21, 2009, 12:16:38 PM10/21/09
to
Hi,

After last upgrade of my Debian/testing system which I use for FPGA
development the Xilinx USB programmer stopped to work.
After some research I've found, that the syntax of udev rules has changed,
and it is necessary to replace $TEMPNODE with $tempnode:

=== xusbdfwu.rules ====
SYSFS{idVendor}=="03fd", SYSFS{idProduct}=="0008", MODE="666"
BUS=="usb", ACTION=="add", SYSFS{idVendor}=="03fd", SYSFS{idProduct}=="0007", RUN+="/sbin/fxload -v -t fx2 -I /usr/local/firmware/xusbdfwu.hex -D $tempnode"
BUS=="usb", ACTION=="add", SYSFS{idVendor}=="03fd", SYSFS{idProduct}=="0009", RUN+="/sbin/fxload -v -t fx2 -I /usr/local/firmware/xusb_xup.hex -D $tempnode"
BUS=="usb", ACTION=="add", SYSFS{idVendor}=="03fd", SYSFS{idProduct}=="000d", RUN+="/sbin/fxload -v -t fx2 -I /usr/local/firmware/xusb_emb.hex -D $tempnode"
BUS=="usb", ACTION=="add", SYSFS{idVendor}=="03fd", SYSFS{idProduct}=="000f", RUN+="/sbin/fxload -v -t fx2 -I /usr/local/firmware/xusb_xlp.hex -D $tempnode"
BUS=="usb", ACTION=="add", SYSFS{idVendor}=="03fd", SYSFS{idProduct}=="0013", RUN+="/sbin/fxload -v -t fx2 -I /usr/local/firmware/xusb_xpr.hex -D $tempnode"
=== end of rules ===

I hope, that this info may be useful for others, experiencing the above problem.
--
HTH & Regards,
Wojtek

Mike Treseler

unread,
Oct 21, 2009, 1:22:19 PM10/21/09
to
wzab wrote:

> After last upgrade of my Debian/testing system which I use for FPGA
> development the Xilinx USB programmer stopped to work.
> After some research I've found, that the syntax of udev rules has changed,
> and it is necessary to replace $TEMPNODE with $tempnode:

I have run into similar problems with file name references
that work on the windows side, but not on linux because
of case mismatches.
For example,
aa.vhd on a file list or script may or may not match the file aA.vhd.

-- Mike Treseler

0 new messages