Re: [Xc3sprog-users] Programming XCFxxP flash PROMs

[Uwe B. <bo...@el...>]

>>>>> "Joris" == Joris van Rantwijk <J.F...@sr...> writes:

...
    Joris> I don't know; could not get Impact to work on Linux :-).  I will
    Joris> check tomorrow on a different machine.

Make sure that your ISE/Impact installation has loaded the FX2 hex files on
your system. For me on Linux these files are loaded to /usr/share

/usr/share> ls -l *hex
-rw-r--r-- 1 root root 22231 25. Jul 2009  xusbdfwu.hex
-rw-r--r-- 1 root root 22274 25. Jul 2009  xusb_emb.hex
-rw-r--r-- 1 root root 22274 25. Jul 2009  xusb_xlp.hex
-rw-r--r-- 1 root root 23542 25. Jul 2009  xusb_xp2.hex
-rw-r--r-- 1 root root 21275 25. Jul 2009  xusb_xpr.hex
-rw-r--r-- 1 root root 23542 25. Jul 2009  xusb_xse.hex
-rw-r--r-- 1 root root 22231 25. Jul 2009  xusb_xup.hex

You can find the hexfiles on the Xilinx site too.

The appropriate hex files are loaded on the initial VID/PID of the
dongle. For me this happens with udev and the file
/etc/udev/rules.d/xusbdfwu.rules

> cat /etc/udev/rules.d/xusbdfwu.rules
# version 0003
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/share/xusbdfwu.hex -D $TEMPNODE"
BUS=="usb", ACTION=="add", SYSFS{idVendor}=="03fd",
SYSFS{idProduct}=="0009", RUN+="/sbin/fxload -v -t fx2 -I
/usr/share/xusb_xup.hex -D $TEMPNODE"
BUS=="usb", ACTION=="add", SYSFS{idVendor}=="03fd",
SYSFS{idProduct}=="000d", RUN+="/sbin/fxload -v -t fx2 -I
/usr/share/xusb_emb.hex -D $TEMPNODE"
BUS=="usb", ACTION=="add", SYSFS{idVendor}=="03fd",
SYSFS{idProduct}=="000f", RUN+="/sbin/fxload -v -t fx2 -I
/usr/share/xusb_xlp.hex -D $TEMPNODE"
BUS=="usb", ACTION=="add", SYSFS{idVendor}=="03fd",
SYSFS{idProduct}=="0013", RUN+="/sbin/fxload -v -t fx2 -I
/usr/share/xusb_xp2.hex -D $TEMPNODE"
BUS=="usb", ACTION=="add", SYSFS{idVendor}=="03fd",
SYSFS{idProduct}=="0015", RUN+="/sbin/fxload -v -t fx2 -I
/usr/share/xusb_xse.hex -D $TEMPNODE"

You can load the hexfile with fxload by hand too. The arguments might
differ. There may also be a mismatch with large hexfiles and the arguments
in  xusbdfwu.rules. The -t argument amy need a change.

After a successfull load of the hexfile, the device reenumerates as
03fd/0008. This is the VID-PID combination xc3sprog looks for.

But as you tested the cable with xc3sprog, this seems to work fine.

Did you try the hints at 
http://rmdir.de/~michael/xilinx/
? 
-- 
Uwe Bonnes                bo...@el...

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------