CASTalk.com

Ewan D. Milne · Guest

Hello everyone.

I have been having some trouble with iMPACT 5.1i and I was hoping
that someone would recognize the problem and be kind enough to help me.

I am using a 3rd party Parallel Cable III from Digilent, and I cannot
get the iMPACT software to use the Parallel port. When I invoke "Cable
Setup..." I get the messages:

Connecting to cable (Parallel Port - LPT1).
Checking cable driver.
Driver Version = 212.
LPT port is already in use.
Cable connection failed.
// *** BATCH CMD : setCable -port LPT0
// *** BATCH CMD : setMode -bs
=>

The parallel port is set up for Bidirectional mode in the BIOS.
The system is a laptop running Windows 2000. The Xilinx software
fileset.txt and install.log appear to be OK, and I do have windrvr.sys
and xpc4drvr.sys present in the WINNT/system32/drivers
folder.

I know this has to be something fairly basic, but after a lot of
experimenting I just can't seem to figure out what is wrong. I have
searched the web and the Xilinx web site but there doesn't seem to be
anything that resembles the problem I am seeing.

Has anyone seen this before? I tried disabling the LPT port in the
device manager, but that didn't seem to make any difference.

Thanks in advance for any replies. I read this group regularly and
find it to be one of the most interesting and informative groups on
Usenet.

Ewan D. Milne
Egenera, Inc.
milne@egenera.com

Aurelian Lazarut · Guest

Ewan,

it seems that you are forcing (in batch mode) to run to LPT0 and the
cable is attached to LPT1

// *** BATCH CMD : setCable -port LPT0

Aurash

Ewan D. Milne wrote:

Ewan D. Milne · Guest

Aurelian Lazarut wrote:

Neil Glenn Jacobson · Guest

There are a number of possibilities. The first could be that you
actually have something else using the parallel port. Are you using,
perchance, anything by Macraigor? If so this solution record (section
8) will help:

http://support.xilinx.com/xlnx/xil_ans_display.jsp?iLanguageID=1&iCountryID=1&getPagePath=15742

The other items in the solution record may be useful but it seems unlikely.

Another possibility is that you have multiple versions of iMPACT running
(or ChipScope or EDK). Only one can run at a time. It is possible
that you have opened the cable in Slave Serial mode and then tried to
use it in Boundary-Scan mode without first closing it in Slave Serial mode.

These are some possibilities and some issues have been resolved with the
latest versions (6.3i)

I hope this helps.

Ewan D. Milne wrote:

Ewan D. Milne · Guest

I eventually figured out what was wrong, so I'll post the solution
in case anyone ever runs into the same problem.

The problem was the windrvr.sys file in C:\WINNT\system32\drivers
It was present, but it was an older version of the driver. A newer
version was in the $XILINX\bin\nt directory and I copied it to the
right place.

Thanks very much to all who responded.

-Ewan

	CASTalk.com Forum Index -> FPGA	All times are GMT
Page 1 of 1