Stupid Xilinx Rubbish

But seriously, has anyone had any experience (good or bad) programming xilinx devices over JTAG with third party devices in the chain.

I'm using impact under linux, from the command line. And impact is having real trouble with an Atmel BSDL file.

I've tried programming a chain with just xilinx devices and it works fine. As soon as impact has to read a third party BSDL it has a fit and stops working.

Here's the error

ERROR:iMPACT:1353 - ACD entry PROGRAM_PROGRESS_COUNT not found for device family ATMEGA128. EXCEPTION:iMPACT:ConstraintsManager.c:394:1.34.2.1 - Data not found.

I've tried using the Xilinx generic BSDL file and it gives the same error.

INFO: ISE 6.2 (Services Pack 2) JTAG chain: Atmel AVR -> Xilinx Spartan IIE Impact batch file:

setMode -bs setCable -port lpt1 #assignFile -p 1 -file "atmega128.bsd" addDevice -p 1 -part "atmega128.bsd" # BSD file for AVR addDevice -p 2 -file "xmemtest.bit" # Bit File for Spartan program -p 1 quit

If anyone can throw some light on this problem it would be a _REAL_ help.

Many thanks Andy

--
Andrew Greensted            Department of Electronics
Bio-Inspired Engineering    University of York, UK
 Click to see the full signature
Reply to
Andrew Greensted
Loading thread data ...

Think I jumped for the newsgroup too soon there. Spot the deliberate mistake in the batch file, was trying to program the wrong device.

Sorry

Andrew Greensted wrote:

--
Andrew Greensted            Department of Electronics
Bio-Inspired Engineering    University of York, UK
 Click to see the full signature
Reply to
Andrew Greensted

I don't know why your setup fails, but I'm having good luck with a three-device chain: Xilinx CPLD - Xilinx Virtex II - Analog Devices ADSP-2196. I'm using ISE 6.2, iMPACT, and a Xilinx Parallel Cable IV.

I inserted '>' characters to reduce newsreader line-wrap problems.

Here's my iMPACT script:

Here's my adsp2196m.bsd:

"TMS : 4";

Reply to
Gammaburst

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.