On 26.7.2008 0:01, Scott Gravenhorst wrote:
> I've just received my Digilent USB-JTAG cable.
> 
> Unfortunately, the Adept ExPort software doesn't seem to know about
> the Spartan-3A DSP.  I also have a Spartan-3E Starter Kit and using
> the same cable, the software finds and properly identifies all 3
> devices in the JTAG chain.
> 
> When I use it on the -3A DSP board, it reports:
> 
> Initializing scan chain...
> Found Device.  IDCODE:  03840093
> Initialization complete.
>    Device 1: UNKNOWN
> 
> I've emailed Digilent support, I assume a software change is required.
> 

If you mean the Spartan-3E Starter Kit from Xilinx ( 
http://www.xilinx.com/products/devkits/HW-SPAR3E-SK-US-G.htm ) then you 
should be able to connect your -3A kit to the -3E kit's JTAG chain and 
use iMPACT.

Henri

On Jul 26, 5:48 pm, no.s...@gte.net (Scott Gravenhorst) wrote:

> >In the meantime, don't they also sell a parallel-port JTAG adapter
> >that's (theoretically) compatible with the Xilinx Parallel Cable III?

> I think that's a good idea, I believe I've read that iMPACT supports
> it.

Yes, this is as far as I can tell the cable that came in the box with
the original spartan 3 kits - a digilent-made board ordered from the
xilinx website.  In those days you just used impact - I think adept
came in when xilinx had their propriety usb supported by impact, and
digilent had their own proprietary usb not supported by it.

On Jul 25, 6:30 pm, no.s...@gte.net (Scott Gravenhorst) wrote:

> >This project claims to be a cable server that will translate between
> >the digilent USB cable (amongst others) and Xilinx's impact tool.
>
> >http://sourceforge.net/projects/xilprg
>
> Thanks, I tried both.  cblsrv seems to support only:
>
>                   dlc5     Xilinx Parallel III
>                   bb       Altera ByteBlaster

The cblsrv project description mentions the digilent USB cable.  When
I looked at the source, there's another source file for usb stuff not
included in the msvc project (or presumably in the unix style
Makefiles).  My guess is you'd need to figure out how to include that
file in the build.

>I also tried xilprg, but the DSP FPGA is not in it's list of supported
>devices.

This could be as simple as making a new entry and putting in the
proper valued for the jtag register lengths from the data sheet.  Or
it could involve additional unpublished parameters (or worse,
procedures) derived by experiment - I'm not sure.