Hi,
I have a strange issue, hopefully you will be able to help me.
Programming a VP780 board, using a bit file created by ISE works
without a problem. But the same project ported to vivado, the generated
bitstream gives the following error during programming (using the same
setup):
XC3SPROG (c) 2004-2011 xc3sprog project $Rev: 774 $ OS: Linux
...
Using /etc/xc3sprog/devlist.txt
Using /etc/xc3sprog/cablelist.txt
Cable jtaghs2 type ftdi VID 0x0403 PID 0x6014 Desc "Digilent USB
Device" dbus data e8 enable eb cbus data 00 data 60
Using Libftdi, Using JTAG frequency 6.000 MHz from undivided clock
JTAG chainpos: 2 Device IDCODE = 0x33691093 Desc: XC7VX690T
Created from NCD file:
vp780_adcpolyphase;COMPRESS=TRUE;UserID=0XFFFFFFFF;Version=2018.2
Target device: 7vx690tffg1930
Created: 2019/07/25 17:50:52
Bitstream length: 138409888 bits
done. Programming time 23754.6 ms
Device failed to configure, INSTRUCTION_CAPTURE is 0x19
USB transactions: Write 8537 read 80 retries 64
I tried to google it, or look at the xc3sprog documentations, but
couldn't find anything that would hint on where the issue lies.
Also tried to program it from vivado itself from a different PC, with
the bit file that was generated from ISE:
set_property PROBES.FILE {} [get_hw_devices xc7vx690t_2]
set_property FULL_PROBES.FILE {} [get_hw_devices xc7vx690t_2]
set_property PROGRAM.FILE
{C:/Users/jellet/Documents/vp780_adcpolyphase_Pulsdetection_2017_11_23.bit}
[get_hw_devices xc7vx690t_2]
program_hw_devices [get_hw_devices xc7vx690t_2]
INFO: [Labtools 27-3164] End of startup status: HIGH
...
and vivado's bitstream:
set_property PROBES.FILE {} [get_hw_devices xc7vx690t_2]
set_property FULL_PROBES.FILE {} [get_hw_devices xc7vx690t_2]
set_property PROGRAM.FILE
{C:/Users/jellet/Documents/vp780_adcpolyphase_Pulsedetection_2019_07_25_3.bit}
[get_hw_devices xc7vx690t_2]
program_hw_devices [get_hw_devices xc7vx690t_2]
ERROR: [Labtools 27-3165] End of startup status: LOW
...
Also tried to google on this, but there are many questions and no
answers in the forums.
Could anybody please tell me what "INSTRUCTION_CAPTURE is 0x19" means?
What causes it? And why?
Every help is appreciated.
Kind Regards,
Dániel
|
