cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
254 Views
Registered: ‎02-11-2019

JTAG PROGRAMMING ISSUE

Hello..

I have Open3S500E Standard, XILINX Development Board . When i try to programe the .bit file through JTAG i am facing the issues like below . Please help me with this ? The JTAG can able to detect the device but programming .bit file issue is happing .

 

 

GUI --- Auto connect to cable...
INFO:iMPACT - Digilent Plugin: Plugin Version: 2.4.4
INFO:iMPACT - Digilent Plugin: no JTAG device was found.
AutoDetecting cable. Please wait.
*** WARNING ***: When port is set to auto detect mode, cable speed is set to default 6 MHz regardless of explicit arguments supplied for setting the baud rates
PROGRESS_START - Starting Operation.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
Driver file xusb_xp2.sys found.
Driver version: src=2301, dest=2301.
Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 x86_64 64bit SYS 14:14:44, version = 1021.
Cable PID = 0008.
Max current requested during enumeration is 300 mA.
Type = 0x0005.
Cable Type = 3, Revision = 0.
Setting cable speed to 6 MHz.
Cable connection established.
Firmware version = 2401.
File version of C:/Xilinx/14.7/ISE_DS/ISE/data/xusb_xp2.hex = 2401.
Firmware hex file version = 2401.
PLD file version = 200Dh.
PLD version = 200Dh.
PROGRESS_END - End Operation.
Elapsed time = 0 sec.
Type = 0x0005.
ESN option: 000019BB91A201.
Attempting to identify devices in the boundary-scan chain configuration...
INFO:iMPACT - Current time: 23-11-2020 17:07:01
PROGRESS_START - Starting Operation.
Identifying chain contents...'0': : Manufacturer's ID = Xilinx xcf04s, Version : 13
INFO:iMPACT:1777 -
Reading C:/Xilinx/14.7/ISE_DS/ISE/xcf/data/xcf04s.bsd...
INFO:iMPACT:501 - '1': Added Device xcf04s successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
'1': : Manufacturer's ID = Xilinx xc3s500e, Version : 4
INFO:iMPACT:1777 -
Reading C:/Xilinx/14.7/ISE_DS/ISE/spartan3e/data/xc3s500e.bsd...
INFO:iMPACT:501 - '1': Added Device xc3s500e successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
done.
PROGRESS_END - End Operation.
Elapsed time = 0 sec.
'1': Loading file 'E:/BEL/DAQ_System/sites/test16.bit' ...
done.
INFO:iMPACT:2257 - Startup Clock has been changed to 'JtagClk' in the bitstream stored in memory,
but the original bitstream file remains unchanged.
UserID read from the bitstream file = 0xFFFFFFFF.
----------------------------------------------------------------------
INFO:iMPACT:501 - '1': Added Device xc3s500e successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
INFO:iMPACT - Current time: 23-11-2020 17:07:33
PROGRESS_START - Starting Operation.
'1': Programming device...
LCK_cycle = NoWait.
LCK cycle: NoWait
done.
INFO:iMPACT:2219 - Status register values:
INFO:iMPACT - 0011 0000 0001 0000 0000 0000 0000 0000
INFO:iMPACT:579 - '1': Completed downloading bit file to device.
INFO:iMPACT:188 - '1': Programming completed successfully.
LCK_cycle = NoWait.
LCK cycle: NoWait
INFO:iMPACT - '1': Checking done pin....done.
'1': Programming terminated. DONE did not go high.
PROGRESS_END - End Operation.
Elapsed time = 1 sec.

 

 

 

 

 

 

 

 

 

 

 

0 Kudos
3 Replies
drjohnsmith
Teacher
Teacher
241 Views
Registered: ‎07-09-2009

Well,
" DONE did not go high" means it failed.

which is not to helpful is it !

out with scope, see if the signals on the JTAG lines look as expected,

Has this board and this programmer / software worked before or is this new ?
<== If this was helpful, please feel free to give Kudos, and close if it answers your question ==>
0 Kudos
237 Views
Registered: ‎02-11-2019

Hello..
Same JTAG is working fine for other evalution boards.
0 Kudos
drjohnsmith
Teacher
Teacher
217 Views
Registered: ‎07-09-2009

That's great news,
so it means yo have a none working board.

out with scope, contrast and compare the jtag signals of the working and none working board.

remember the obvious, such as power supply missing, pull ups missing,
<== If this was helpful, please feel free to give Kudos, and close if it answers your question ==>
0 Kudos