On Sun, 1 Oct 2017 06:04:45 -0700 (PDT)
roman.eberle@arcor.de wrote:

> Hi,
> 
> anyone having success with a FYDK-XILINX Platform Cable USB
> Model DLC9LP? 
> idVendor=0403, idProduct=6014

I bought four Chinese Platform Cables, and was surprised to
find I had two different types, two with Cypress 8051 + logic
chip, and two with FTDI (0403-6xxx) and level shifters. 

The guy using them got the FTDI ones working with Impact, but
not the Cypress ones which need a firmware file and an extra
package? to upload the 8051 firmware on connection under linux.  

I think that one of the apps is scripted Impact, so it may be
simple to recover the settings. Impact was installed from ISE
14.7. 
   
Jan Coombs

On 10/01/2017 03:04 PM, roman.eberle@arcor.de wrote:
> Hi,
> 
> anyone having success with a FYDK-XILINX Platform Cable USB Model DLC9LP?
>  
> idVendor03, idProduct`14
> 
> With your help I was able to get rid of "windrv6 module not loaded" error message, and it looks as if impact is using libusb-driver.so.
> 
> But I still get "cable not found" error.
> 
> thanks & regards
> 

Hi,

are you sure the given product and vendor IDs are from your Xilinx
Programmer? All my programmers have VendorID 0x03fd and product IDs
between 0x0007 and 0x0015. Once fxload has loaded the cypress firmware
the programmer should have productID 0x0008 and the LED turns orange or
green.

roman.eberle@arcor.de wrote:

> Hi,
> 
> anyone having success with a FYDK-XILINX Platform Cable USB Model DLC9LP?
>  
> idVendor=0403, idProduct=6014
> 
> With your help I was able to get rid of "windrv6 module not loaded" error
> message, and it looks as if impact is using libusb-driver.so.
> 
> But I still get "cable not found" error.
> 
> thanks & regards
I have a DLC9G, don't know how this is different from a DLC9LP.
It works, but I occasionally get into some kind of problem where it will not 
initialize.  I have to go through several menus to reset impact so it scans 
again for the device.  You do NOT need windrvr, that is for the old parallel 
port JTAG device.  

Jon

Hi,

anyone having success with a FYDK-XILINX Platform Cable USB Model DLC9LP?
 
idVendor=0403, idProduct=6014

With your help I was able to get rid of "windrv6 module not loaded" error message, and it looks as if impact is using libusb-driver.so.

But I still get "cable not found" error.

thanks & regards

On 07/25/2016 08:03 PM, adityaishwar1994@gmail.com wrote:
> Getting following error at make step:
> 
> adityapappu@adityapappu-NV55C:/opt/Xilinx/usb-driver$ make cc -Wall
> -fPIC -DUSB_DRIVER_VERSION="\"2016-07-23 20:34:57\""  usb-driver.c
> xpcu.c parport.c config.c jtagmon.c -o libusb-driver.so -ldl -lusb
> -lpthread -shared parport.c: In function ‘parport_transfer’: 
> parport.c:21:23: warning: variable ‘last_pp_write’ set but not used
> [-Wunused-but-set-variable] static unsigned char last_pp_write = 0; 
> ^ /usr/bin/ld: cannot open output file libusb-driver.so: Permission
> denied collect2: error: ld returned 1 exit status Makefile:28: recipe
> for target 'libusb-driver.so' failed make: *** [libusb-driver.so]
> Error 1 adityapappu@adityapappu-NV55C:/opt/Xilinx/usb-driver$
> 
The first one is a warning and may be harmless, the second one says 
it can not open libusb-driver.so: Permission denied. 
check the permissions. Perhaps you had run the build before as root. 
and now it can not overwrite the file, but that is just a guess... 

Getting following error at make step:

adityapappu@adityapappu-NV55C:/opt/Xilinx/usb-driver$ make
cc -Wall -fPIC -DUSB_DRIVER_VERSION="\"2016-07-23 20:34:57\""  usb-driver.c xpcu.c parport.c config.c jtagmon.c -o libusb-driver.so -ldl -lusb -lpthread -shared
parport.c: In function ‘parport_transfer’:
parport.c:21:23: warning: variable ‘last_pp_write’ set but not used [-Wunused-but-set-variable]
  static unsigned char last_pp_write = 0;
                       ^
/usr/bin/ld: cannot open output file libusb-driver.so: Permission denied
collect2: error: ld returned 1 exit status
Makefile:28: recipe for target 'libusb-driver.so' failed
make: *** [libusb-driver.so] Error 1
adityapappu@adityapappu-NV55C:/opt/Xilinx/usb-driver$ 

I found some feedback on the microblaze-uclinux mailing list :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/archive/2007/03/msg00101.html

This is a mail from Paul-Armand Verhaegen, and it explains the 16
steps he followed to use this usb lib with ISE 8.2 SP3 on Ubuntu, to
download the Virtex2 of a XUPV2P board.

Luzerne GANHIR

On 25 mar, 22:17, carlos.as...@gmail.com wrote:
>
> Thank you very much Luzerne for taking the time of explaining it step
> by step really clearly and slowly. I really really appreciate it.
>
> What I was doing wrong was doing "export LD_PRELOAD=/path/Travail/usb-
> driver/libusb-driver.so" in another terminal session since I thought
> this was a kind of global setting.
>
> Again thanks a lot for everything you have done.
>
> Carlos

You're welcome. My post was in fact more a contribution given back to
Michael GERNOTH's work than to you :) but I'm happy to know it helps
someone, and to discover this someone is so grateful :)
But I think your greets are misplaced, as Michael GERNOTH deserves all
of them.

Luzerne GANHIR

On Mar 23, 4:16 am, "Luzerne" <luzerne.gan...@gmail.com> wrote:
> On 23 mar, 07:25, carlos.as...@gmail.com wrote:
>
> > I'm very new to linux but I undestand that you propose an alternative
> > to windrvr that seems to work well.
> > [...]
> > I've spent many hours trying to get the windrvr and your driver to
> > work without success.
> > [...]
> > I would really appreciate some help. I'm new to Linux and I use
> > Kubuntu 6.10.
>
> Here is my "step by step newbie" installation howto for Ubuntu Dapper
> 6.06 :)
>
> Open a terminal (Application menu : Accessory > Terminal), where you
> can enter the given commands (line starting with the $ prompt symbol).
>
> We suppose we are in your prefered directory. For you it is probably
> something like "/home/carlos". For this tutorial il will be replaced
> by a generic "/path" :
>
> $ pwd
> /path
>
> First, you donwload the program's archive in your prefered "/path/
> Download" directory.
>
> $ mkdir Download
> $ wget "http://cvs.zerfleddert.de/cgi-bin/viewcvs.cgi/usb-
> driver.tar.gz?view=3Dtar" -O Download/usb-driver.tar.gz
>
> Now you go in your prefered work directory (for me it is called
> "Travail" :) and you decompress the archive.
>
> $ cd /path/Travail
> $ tar zxvf /path/Download/usb-driver.tar.gz
> $ cd usb-driver
>
> First thing to do is to check if README or INSTALL files exist, and
> _READ_ them.
>
> $ ls -l
> $ more README
>
> Now you know what to do. First you check the required module are
> loaded.
>
> $ lsmod | grep parport
> parport_pc             38340  1
> parport                39560  3 ppdev,lp,parport_pc
>
> If you get something like that, it's ok. You can compile.
>
> $ make
>
> You may get this kind of error :
>
> gcc -fPIC -Wall usb-driver.c -o libusb-driver.so -ldl -lusb -lpthread -
> shared
> usb-driver.c:36:17: erreur: usb.h : Aucun fichier ou r=E9pertoire de ce
> type
>
> It's because you have not installed one of the required libusb and
> libusb-dev library.
> You can install libusb-dev this way :
>
> $ sudo apt-get install libusb-dev
>
> Now you can retry the compilation.
>
> $ make
> gcc -fPIC -Wall usb-driver.c -o libusb-driver.so -ldl -lusb -lpthread -
> shared
> gcc -fPIC -DDEBUG -Wall usb-driver.c -o libusb-driver-DEBUG.so -ldl -
> lusb -lpthread -shared
>
> This time, if everything goes right, you can try impact :) As
> explained in the README, set the preload environnement variable (this
> will be set only for the current terminal) :
>
> $ export LD_PRELOAD=3D/path/Travail/usb-driver/libusb-driver.so
>
> Now, you can run impact. But you may get an error :
>
> Can't open /dev/parport0: Permission denied
> LPT port is already in use. rc =3D 0h
> Cable connection failed.
> Reusing 79063641 key.
> Reusing FD063641 key.
>
> It means you have not the required right on the /dev/parport0 device.
> You can check this this way :
>
> $ ls -l /dev/parport0
> crw-rw 1 root lp 99, 0 2007-03-16 07:48 /dev/parport0
>
> A fast work arround solution is to change the owner of this device :
>
> $ whoami
> luzerne
> $ sudo chown luzerne /dev/parport0
>
> Before retrying to program a device with impact, it may be necessary
> to disbale the eventual impact cable locking. This can be done this
> way :
>
> $ impact -batch
>
> > setMode -bscan
> > cleancablelock
> > quit
>
> Now, you can retry to program a device with impact. This was my "step
> by step" personnal log.
>
> http://www.chezmoicamarche.org/ YMMV / HTH
>
> Luzerne GANHIR

Thank you very much Luzerne for taking the time of explaining it step
by step really clearly and slowly. I really really appreciate it.

What I was doing wrong was doing "export LD_PRELOAD=3D/path/Travail/usb-
driver/libusb-driver.so" in another terminal session since I thought
this was a kind of global setting.

Again thanks a lot for everything you have done.

Carlos

Grant Likely wrote:
> Brilliant!  Seems to work for me.  I can't test it fully right now
> because impact complains with "ERROR:iMPACT:583 - '2': The idcode read
> from the device does not match the idcode in the bsdl File." when I
> try to download to my ml403 board (which happens when I use the kernel
> driver too).
In that case, try lowering the speed in the cable setup menu. The ID
code problem often happens when the cable speed is too high.
Initializing the JTAG chain works most of the time, but after that
transfers fail. Lowering the speed fixes that for me in most cases.

-- 
My email address is only valid until the end of the month.
Try figuring out what the address is going to be after that...