10-20-2017 08:51 PM
We bought new VC707, but when trying to 'open target' in Hardware manager, a critical messages appear and cannot connect with it like below pictures.
I checked cable and VC707's power(VC707's led is on), switches, jumpers many times, but there is still the same critical messages.
Is there solution of this? or do we need initialize it?
10-22-2017 07:41 AM
Make sure that the cable drivers for the digilent adapter is installed and working as expected.
Also make sure that the USB connection is reliable which includes the USB power supply.
Hope this helps,
10-23-2017 04:33 AM
You can check digilent jtag adapters with the djtgcfg tool like this ...
$ djtgcfg enum Found 1 device(s) Device: CmodA7 Product Name: Digilent Cmod A7 - 35T User Name: CmodA7 Serial Number: 210328A41652
... the Device Name can then be used to init the scan chain ...
$ djtgcfg -d CmodA7 init Initializing scan chain... Found Device ID: 0362d093 Found 1 device(s): Device 0: XC7A35T
... and finally you can check communication with ...
$ djtgcfg -d CmodA7 -i 0 loop -c 100 Looping... Device ID: 0362d093 successfully looped 100 iterations.
Note that your board will show up under a different name than CmodA7, so you need to adjust this accordingly.
Maybe this helps,
10-25-2017 01:49 PM
Is it problem of VC707?
At least a problem with the connection between the Digilent Module and the VC707 JTAG.
Looking at the JTAG Chain Block Diagram (Figure 1-7 of UG885), there are a number of potential reasons for the JTAG failing, like for example ...
I would suggest to check the Mode Pins first, because those are easy to check and modify.
A good starting config would be SW11 (ON, OFF, ON, OFF, ON).
The next step could be to use a separate/external JTAG cable to see if maybe the digilent module is broken.
Hope this helps,