218
ChipScope Pro Software and Cores User Guide
UG029 (v14.3) October 16, 2012
Appendix A:
ChipScope Pro Tools Troubleshooting Guide
3.
Has the JTAG logic been released by
the programming tool?
If NO or NOT SURE: Programming the FPGA with the iMPACT tool
instead of the ChipScope Pro Analyzer tool can solve this problem. Try
performing the following steps:
1.
Run iMPACT, to program the FPGA.
2.
Exit iMPACT.
3.
Run ChipScope Pro Analyzer tool.
If YES: Go to Issue #4.
4.
Is there a Xilinx System ACE™ MPM
device in the JTAG Chain?
If YES: There is a known issue when the JTAG chain contains a System
ACE MPM. The core unit might not be found. To work around the
problem, put the following line in the ChipScope Pro Analyzer tool project
file (.cpj) and read it in before opening the cable:
avoidUserRegDeviceX=1,2
Replace the "X" with the position index number of the V50E device.
Use index 0 for the first device in the chain. Information messages
about skipping scanning on the V50E device are placed in the
cs_analyzer.log file.
To use the updated .cpj file, follow the steps listed above. Be sure to
load the .cpj file immediately after ChipScope Pro Analyzer tool
launches before any other action.
If NO: Go to Issue #5.
5.
Are there any non-Xilinx devices in
the JTAG chain?
If YES: You must enter the instruction register length for any non-Xilinx
devices in the chain in the ChipScope Pro Analyzer GUI. To find this, you
can examine the BSDL file corresponding to the device. There will be an
entry similar to below:
attribute INSTRUCTION_LENGTH of <entity name> : entity is
XX;
If you do not enter correct instruction register lengths, the ChipScope
Pro Analyzer tool cannot set the JTAG device offsets correctly and will
not be able to identify the devices or debug cores.
If NO: Go to Issue #6.
6.
Has the device correctly exited from
the device start-up sequence?
If NO: The ChipScope Pro Analyzer tool might not be able to find the core
because the configuration options are not set correctly. If the BitGen option
LCK_cycle (or Release DLL in Project Navigator) is not set to "Nowait," the
ChipScope Pro Analyzer tool might not be able to detect the core because
the ChipScope Pro core must be initialized with the release of GWE.
Setting this option to "Nowait" (which is the default option) might solve
this problem.
If YES: Go to Issue #7.
Table A-8:
Troubleshooting Core Detection Issues
(Cont’d)
Issue(s)
Solution(s) or Work-Around(s)