fpga jtag port dont't work ?

[ZFDok]

configuration fpga jtag

i have do two pcb fpga board , but they dont work good ,the jatg port does not download bit file ,the error report is read ID 11111111111..., not the correct ID number, one know the reason,who can help me?thanks!

 

[echo47]

parallel cable iii jtag deviceid

Sounds like your JTAG connection is broken or your board is dead.

What type board? What type FPGA? What software are you using? Are there any other devices on the JTAG chain?

Check the web site of the software vendor to see if they have any service announcements such as "oops we broke the JTAG with certain devices, so please download a service pack".

 

[ZFDok]

fpga jtag no hardware

i am use the xc2s15-vq100 and xc2s50-tq144, the two board all sigle chip on the jtag ,no other device, the tdo pin always high level, i use ISE7.1 of xilinx software develop kit. i check the board ,i use series slave mode can config success and work good.

 

[echo47]

xilinx impact setpreference

Are you using the Xilinx Parallel Cable IV interface unit? If you are running Win2k or WinXP, did you allow the ISE installer to install the device driver that provides access to the parallel port?

Are you using the Xilinx iMPACT utility? What happens if you launch iMPACT and click File -> Initialize Chain?

TDO isn't working? How about TDI, TCK, and TMS going into the FPGA?

 

[ZFDok]

setcable svf

the host work is no problem, before i have a debug board with xc2s100-pq208, it can word ,but last it don't work ,i discover the tdo ,tms tck have signal all, but the device id is 000011111111111, why the device id read not correct? i use the parallel cable III. the mode select is right .

 

[echo47]

windrvr6.sys download

"it can word ,but last it don't work" -- sorry but that doesn't make sense.

Is your TDI working? That's important too.

If I unplug my FPGA board from my Parallel Cable IV, iMPACT reports ID = "00001111111111111111111111111111". That sounds similar to your problem.

What happens if you launch iMPACT and click File -> Initialize Chain? Do the error messages say anything interesting?

 

[ZFDok]

info bat jtag

the initial chain appear the communication with the cable cound not be established.

 

[tkbits]

xilinx jtag status word impact id

Have you tried setting the config mode (M0, M1, M2) to boundary-scan?

 

[Matrix_YL]

windrvr6.sys ücretsiz indir

hi all
I meet this problem too!

// *** BATCH CMD : setPreference -pref UserLevel:NOVICE
// *** BATCH CMD : setPreference -pref MessageLevelETAILED
// *** BATCH CMD : setPreference -pref ConcurrentMode:FALSE
// *** BATCH CMD : setPreference -pref UseHighz:TRUE
// *** BATCH CMD : setPreference -pref ConfigOnFailure:STOP
// *** BATCH CMD : setPreference -pref StartupCLock:AUTO_CORRECTION
// *** BATCH CMD : setPreference -pref AutoSignature:FALSE
// *** BATCH CMD : setPreference -pref KeepSVF:FALSE
// *** BATCH CMD : setPreference -pref svfUseTime:FALSE
// *** BATCH CMD : setPreference -pref UserLevel:NOVICE
// *** BATCH CMD : setPreference -pref MessageLevelETAILED
// *** BATCH CMD : setPreference -pref ConcurrentMode:FALSE
// *** BATCH CMD : setPreference -pref UseHighz:TRUE
// *** BATCH CMD : setPreference -pref ConfigOnFailure:STOP
// *** BATCH CMD : setPreference -pref StartupCLock:AUTO_CORRECTION
// *** BATCH CMD : setPreference -pref AutoSignature:FALSE
// *** BATCH CMD : setPreference -pref KeepSVF:FALSE
// *** BATCH CMD : setPreference -pref svfUseTime:FALSE
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bsfile
// *** BATCH CMD : setCable -port svf -file "E:\FPGASTUDY\pic_test\hehe.svf"
// *** BATCH CMD : addDevice -position 1 -file "E:\FPGASTUDY\pic_test\test_1.bit"
'1': Loading file 'E:\FPGASTUDY\pic_test\test_1.bit' ...
done.
INFO:iMPACT:1777 -
Reading D:/Xilinx/spartan2/data/xc2s200.bsd...
WARNING:iMPACT:2257 - Startup Clock has been changed to 'JtagClk' in the bitstream stored in memory,
but the original bitstream file remains unchanged.
INFO:iMPACT:501 - '1': Added Device xc2s200 successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
GUI --- Add one device.
Device #1 selected
// *** BATCH CMD : setAttribute -position 1 -attr configFileName -value "E:\FPGASTUDY\pic_test\test_1.bit"
'1': Loading file 'E:\FPGASTUDY\pic_test\test_1.bit' ...
done.
INFO:iMPACT:501 - '1': Added Device xc2s200 successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
----------------------------------------------------------------------
----------------------------------------------------------------------
Device #1 selected
// *** BATCH CMD : Program -p 1
PROGRESS_START - Starting Operation.
Validating chain...
Boundary-scan chain validated successfully.
'1'rogramming device...
done.
INFO:iMPACT:579 - '1': Completed downloading bit file to device.
INFO:iMPACT:580 - '1':Checking done pin ....done.
'1': Programmed successfully.
PROGRESS_END - End Operation.
Elapsed time = 1 sec.
GUI --- PROM Formatter selected
// *** BATCH CMD : setMode -pff
// *** BATCH CMD : setMode -pff
// *** BATCH CMD : setMode -pff
// *** BATCH CMD : setMode -pff
// *** BATCH CMD : setSubmode -pffserial
// *** BATCH CMD : setAttribute -configdevice -attr name -value "PFFConfigDevice"
// *** BATCH CMD : setAttribute -configdevice -attr size -value "0"
// *** BATCH CMD : addCollection -name "Untitled"
// *** BATCH CMD : setAttribute -collection -attr dir -value "UP"
// *** BATCH CMD : addDesign -version 0 -name "0000"
// *** BATCH CMD : addDeviceChain -index 0
// *** BATCH CMD : addDevice -position 1 -file "E:\FPGASTUDY\pic_test\test_1.bit"
'1': Loading file 'E:\FPGASTUDY\pic_test\test_1.bit' ...
INFO:iMPACT - Elapsed time = 0 sec.
done.
INFO:iMPACT:501 - '1': Added Device xc2s200 successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
GUI --- Add one device.
// *** BATCH CMD : setMode -pff
Collection : Untitled
Design : 0
Device Chain : 0
----------------------------------------------------------------------
Position PartName FileName
1 xc2s200 E:\FPGASTUDY\pic_test\test_1.bit
----------------------------------------------------------------------
// *** BATCH CMD : setAttribute -configdevice -attr fillValue -value "FF"
// *** BATCH CMD : setAttribute -configdevice -attr fileFormat -value "mcs"
// *** BATCH CMD : setAttribute -collection -attr dir -value "UP"
// *** BATCH CMD : setAttribute -configdevice -attr path -value "e:\fpgastudy\pic_test/"
// *** BATCH CMD : setAttribute -collection -attr name -value "Untitled"
// *** BATCH CMD : generate -generic
'1': Added Device xc17v01 successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
Generating Prom file using the following auto generated Prom(s):
xc17v01
----------------------------------------------------------------------
0x28c44 (166980) bytes loaded up from 0x0
Using user-specified prom size of 205K
Writing file "e:\fpgastudy\pic_test//Untitled.mcs".
Writing file "e:\fpgastudy\pic_test//Untitled.prm".
Writing file "e:\fpgastudy\pic_test//Untitled.sig".
GUI --- Total configuration bit size = 1335840 bits.
GUI --- Total configuration byte size = 166980 bytes.
// *** BATCH CMD : setCurrentDesign -version 0
GUI --- System ACE selected
// *** BATCH CMD : setMode -bs
GUI --- Boundary-Scan File selected
// *** BATCH CMD : setMode -bsfile
GUI --- Switch to Configuration Mode
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : addDevice -position 1 -file "E:\FPGASTUDY\pic_test\test_1.bit"
'1': Loading file 'E:\FPGASTUDY\pic_test\test_1.bit' ...
done.
INFO:iMPACT:501 - '1': Added Device xc2s200 successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
GUI --- #1 xc2s200 E:\FPGASTUDY\pic_test\test_1.bit
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bsfile
Device #1 selected
// *** BATCH CMD : setMode -bs
GUI --- Auto connect to cable...
// *** BATCH CMD : setCable -port auto
AutoDetecting cable. Please wait.
CB_PROGRESS_START - Starting Operation.
Connecting to cable (USB Port).
Cable connection failed.
Connecting to cable (Parallel Port - LPT1).
Checking cable driver.
Driver windrvr6.sys version = 6.2.3.0. LPT base address = 0378h.
ECP base address = FFFFFFFFh.
Cable connection failed.
Connecting to cable (Parallel Port - LPT2).
Checking cable driver.
Driver windrvr6.sys version = 6.2.3.0.Cable connection failed.
Connecting to cable (Parallel Port - LPT3).
Checking cable driver.
Driver windrvr6.sys version = 6.2.3.0.Cable connection failed.
Connecting to cable (Parallel Port - LPT4).
Checking cable driver.
Driver windrvr6.sys version = 6.2.3.0.Cable connection failed.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
Driver xusbdfwu.sys version: 1018 (1018).
Driver windrvr6.sys version = 6.2.3.0. Max current requested during enumeration is 280 mA.
Cable Type = 3, Revision = 0.
Setting cable speed to 6 MHz.
Cable connection established.
Firmware version = 1018.
CPLD file version = 0006h.
CPLD version = 0006h.
CB_PROGRESS_END - End Operation.
Elapsed time = 2 sec.
// *** BATCH CMD : Program -p 1
PROGRESS_START - Starting Operation.

ERROR:iMPACT:583 - '1': The idcode read from the device does not match the idcode in the bsdl File.
INFO:iMPACT:1578 - '1': Device IDCODE : 00001101101101101101101101101101
INFO:iMPACT:1579 - '1': Expected IDCODE: 00000000011000011100000010010011
PROGRESS_END - End Operation.
Elapsed time = 3 sec.
Device #1 selected
// *** BATCH CMD : ReadIdcode -p 1
ERROR:iMPACT:583 - '1': The idcode read from the device does not match the idcode in the bsdl File.
INFO:iMPACT:1578 - '1': Device IDCODE : 00001101101101101101101101101101
INFO:iMPACT:1579 - '1': Expected IDCODE: 00000000011000011100000010010011
Cable is not connected.

]
what's wrong with it ? Can anyone help us ?

 

[echo47]

fpga jtag id code

That looks like a log of many steps. Too many. Can you insert comments saying what you tried to do at each step?

What devices are on your JTAG chain? Does the iMPACT diagram match your hardware?

I see four copies of the message "Added Device xc2s200 successfully". Why so many? If you accidentally insert duplicate copies of devices, the JTAG chain will be wrong and you will get mixed up IDCODEs.

 

[Matrix_YL]

jtag broken chain

Thank you all


My problem was solved,A PAD unconnect with PCB.