From: John Adair on
A common problem with USB to parallel port converters is they don't
work. You will find many previous postings on this. Sometimes a
Cardbus or Expresscard plug in parallel port will work but many
laptops don't even have these. Some docking stations can offer a
parallel port option and we can use the Xilinx and our own Prog2
Parallel Port cables like that with our HP laptops.

Outside of the fairly expensive Xilinx USB cable there are a number of
indirect USB solutions which don't work directly with Xilinx software.
We also will be offering a low cost USB option (Prog3) with our own
products, that is totally compatible with Xilinx software, later this
month. We will also be offering this option to existing registered
owners of Enterpoint boards.

John Adair
Enterpoint Ltd.


On 3 Jan, 00:03, Angus <angusdun...(a)googlemail.com> wrote:
> Hi,
>
> I am using ISE 9.1
>
> I had an old Digilab IIE board which i want to use. The Digilab IIE
> board can be programmed using the PC's parallel port. However, my PC
> has only USB ports. as such i bought an usb-DB25 cable to connect the
> parallel cable which comes with the board to my PC. Unfortunately when
> trying to configure FPGA through a simple design project, the cable is
> not recognised. the complete error log is attached below. Namely, the
> main error message is:
>
> Connecting to cable (Usb Port - USB21).
> Checking cable driver.
>  File C:\WINDOWS\system32\drivers\xusbdfwu.sys not found.
> Driver file not found. Inf file version = 0.
>  Driver xusbdfwu.sys version: 1021 (1029).
>  Driver windrvr6.sys version = 8.1.0.0. WinDriver v8.10 Jungo (c) 1997
> - 2006 Build Date: Aug 15 2006 X86 32bit SYS 14:21:34, version = 810.
> Cable connection failed.
> PROGRESS_END - End Operation.
>
> I have tried Xilinx Answer 30184)  to noavail. any help please> Many
> thanks
>
> ===========
>
> error message
>
> // *** BATCH CMD : addDevice -p 1 -file "C:/iseProjects/Training/
> BoardIIT/top_level.bit"
> '1': Loading file 'C:/iseProjects/Training/BoardIIT/top_level.bit' ...
> done.
> INFO:iMPACT:1777 -
> Reading C:/Xilinx91i/spartan2e/data/xc2s200e.bsd...
> INFO:iMPACT:501 - '1': Added Device xc2s200e successfully.
> ----------------------------------------------------------------------
> ----------------------------------------------------------------------
>  Count ReleaseSemaphore rc = 298.
> GUI --- Auto connect to cable...
> // *** BATCH CMD : setCable -port auto
> AutoDetecting cable. Please wait.
> PROGRESS_START - Starting Operation.
> Connecting to cable (Parallel Port - LPT1).
> Checking cable driver.
>  Driver windrvr6.sys version = 8.1.0.0. WinDriver v8.10 Jungo (c) 1997
> - 2006 Build Date: Aug 15 2006 X86 32bit SYS 14:21:34, version = 810.
> Cable connection failed.
> Connecting to cable (Parallel Port - LPT2).
> Checking cable driver.
>  Driver windrvr6.sys version = 8.1.0.0. WinDriver v8.10 Jungo (c) 1997
> - 2006 Build Date: Aug 15 2006 X86 32bit SYS 14:21:34, version = 810.
> Cable connection failed.
> Connecting to cable (Parallel Port - LPT3).
> Checking cable driver.
>  Driver windrvr6.sys version = 8.1.0.0. WinDriver v8.10 Jungo (c) 1997
> - 2006 Build Date: Aug 15 2006 X86 32bit SYS 14:21:34, version = 810.
> Cable connection failed.
> Connecting to cable (Parallel Port - LPT4).
> Checking cable driver.
>  Driver windrvr6.sys version = 8.1.0.0. WinDriver v8.10 Jungo (c) 1997
> - 2006 Build Date: Aug 15 2006 X86 32bit SYS 14:21:34, version = 810.
> Cable connection failed.
> Connecting to cable (Usb Port - USB21).
> Checking cable driver.
>  File C:\WINDOWS\system32\drivers\xusbdfwu.sys not found.
> Driver file not found. Inf file version = 0.
>  Driver xusbdfwu.sys version: 1021 (1029).
>  Driver windrvr6.sys version = 8.1.0.0. WinDriver v8.10 Jungo (c) 1997
> - 2006 Build Date: Aug 15 2006 X86 32bit SYS 14:21:34, version = 810.
> Cable connection failed.
> PROGRESS_END - End Operation.
> Elapsed time =      4 sec.
> Cable autodetection failed.
> WARNING:iMPACT:923 - Can not find cable, check cable setup !

From: Angus on
On 3 Jan, 19:15, John Adair <g...(a)enterpoint.co.uk> wrote:
> A common problem with USB to parallel port converters is they don't
> work. You will find many previous postings on this. Sometimes a
> Cardbus or Expresscard plug in parallel port will work but many
> laptops don't even have these. Some docking stations can offer a
> parallel port option and we can use the Xilinx and our own Prog2
> Parallel Port cables like that with our HP laptops.
>
> Outside of the fairly expensive Xilinx USB cable there are a number of
> indirect USB solutions which don't work directly with Xilinx software.
> We also will be offering a low cost USB option (Prog3) with our own
> products, that is totally compatible with Xilinx software, later this
> month. We will also be offering this option to existing registered
> owners of Enterpoint boards.
>
> John Adair
> Enterpoint Ltd.


Many thanks John for your reply. i hope XILINX with take this case
seriously and prepare us a patch.
From: Angus on
i found at last the datasheet@
http://www.digilentinc.com/Data/Products/D2E/D2E-rm.PDF (please p2
onwards re. the configuration cable). can my problem still be
resolved?


From: John Adair on
That's a very old board and about then Digilent did a few like that
with a direct connection to a parallel port. It does complicate a
solution in that direct connection to a Laptop either is going to need
an add-on parallel port by plg in card or docking station methods.

However I think there is a chance of using a physical adaptor to make
this interface work with a modern cable. I would suggest googling
parallel cable III schematics to understand what goes in a parallel
port cable and how it relates to a parallel port pinout. I think if
you can wire to the relevant pins of the interface, enabling any
relevant buffer, you may be able to get the 4 JTAG signals you need.

Of course just buying a new board, with a modern interface, might be
simplier.

John Adair
Enterpoint Ltd.


On 4 Jan, 22:26, Angus <angusdun...(a)googlemail.com> wrote:
> i found at last the datasheet(a)http://www.digilentinc.com/Data/Products/D2E/D2E-rm.PDF(please p2
> onwards re. the configuration cable). can my problem still be
> resolved?