Is this a Win7 PC? Do you recall getting the Firewall warnings? Did you make sure to check the boxes to Allow Access? You can check this with the following steps:
- Open Control Panel
- Select Windows Firewall
- Select "Allow a program or feature through Windows Firewall"
- Look for "eclipse"
- You should have an entry for each version of Xilinx tools you have installed. Select and click Details to see which version is which. I have both Domain and Home/Work boxes checked.
- 2013.4 and prior have entries for hw_server
- Look for "Java(TM) Platform SE binary"
- Look for "rdi_xmd" for 2014.1 and newer
- 2013.3 has an entry for vcse_server
- 2013.4 and prior have entries for "xmd"
We have heard of corrupt Xilinx tool installs from users who installed from an archive that wasn't cross-checked with the checksum. Did you check the archive checksum before installing?
Have you tried the command-line XMD advice given to you on the Xilinx forums?
One more thought -- did you modify the Run Configuration to NOT source the initialization TCL? That would be bad.
Thanks Bryan. The Run Configuration no longer sourced the TCL. I didn't intentionally or consciously modify it so it didn't, and it must have been there when I went through chapter 2, so I don't know how I did it.
Where do I check if ps7_init.tcl is sourced?
Within the SDK once you have created an application right click on the application in the Project Explorer pane on the left. Select either "Run As" or "Debug As" and select 'Configurations. In the "Target Setup" tab in the configuration you can make sure that "Run ps7_init" is checked.
I have the same ID 64 problem when trying to send my "*.elf" file to my zynq (zedboard).
However, SDK 2017.3 does not allow me to check " Run_ps7_init"!!
Any suggestion plz
Did you export a .hdf file from Vivado?
We have a new rev D ZedBoard, and it runs out of the box with the pre-configured SD card image once the jumpers are set for SD card boot.
Setting the jumpers for cascaded JTAG (Jp7 - JP11 all set to GND) and trying to run logic and software built with Vivado 2014.1 and SDK 2014.1 is causing me great pain.
I have been trying to follow the tutorials in chapters 2 and 3 in zedboard_CTT_v2013_2_130807.pdf. This has been written for v2013.2, so I'm not surprised that there have been little issues I've had to resolve along the way.
Nevertheless I have bumbled my way through chapter 2 and most of chapter 3. I've has to wire in a proc_sys_reset block that wasn't mentioned in the tutorial due to Vivado critical warnings without it.
Now I finally have everything building in SDK with the hardware generated in Vivado, but I've hit a showstopper I can't get past without help. I've set up a Xilinx C/C++ Application GDB run configuration with the generated .elf. I am able to program the PL and the blue DONE LED lights up, but when I attempt to run the .elf with the run configuration I get an error "No Target with ID 64 in the System" as in the title.
Another thread (http://zedboard.org/content/zynqintro-lab-5) has mentioned this error in a different context, but no answers there have helped, other than to suggest the SDK can't find the ARM (ID 64). This is strange, because the tutorial in chapter 2 (without a PL configuration) didn't have this problem.
Is anyone able to help?