Showing results for 
Show  only  | Search instead for 
Did you mean: 
Registered: ‎06-09-2014

No Target with ID 64 in the System

Forums: Using Xilinx Tools




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 (attached).  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 had 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 on the zedboard site ( 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?

0 Kudos
3 Replies
Registered: ‎04-17-2011

Where you able to use XMD to program and run software? Does it show same error?

XMD% connect arm hw
XMD% fpga -f /path/to/bitfile.bit
XMD% source /path/to/hw_platform_spec/ps7_init.tcl
XMD% ps7_init
XMD% dow /path/to/program.elf
XMD% con

Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful and reply oriented.
Registered: ‎06-09-2014

Thank you Debraj, This did work. The key is the ps7_init.tcl file. The run configuration no longer referred to it. It did when I went through chapter 2 or I would have had this problem then. I don't know how the .tcl reference got lost. Steve
0 Kudos
Registered: ‎11-29-2008

I have the same problem... some times I can download program to arm, sometimes not...

error is the same even when I do it through xmd


****** Xilinx Microprocessor Debugger (XMD) Engine
****** XMD v2016.2 (64-bit)
  **** SW Build 1577090 on Thu Jun  2 16:32:40 MDT 2016
    ** Copyright 1986-2016 Xilinx, Inc. All Rights Reserved.

WARNING: XMD has been deprecated and will be removed in future.
         XSDB replaces XMD and provides additional functionality.
         We recommend you switch to XSDB for commandline debugging.
         Please refer to SDK help for more details.

Accepted a new TCLSock connection from on port 52794

Accepted a new TCLSock connection from on port 52794
Processor Reset .... DONE
Downloading Program -- C:/AAAAAAAAAA/A_data/antoine_developpement_xilinx/cartes/zedboard/test_sdcard/test_conformite_hard/test_conformite_hard.sdk/hello/Debug/hello.elf
    section, .text: 0x00100000-0x0010197f
    section, .init: 0x00101980-0x00101997
    section, .fini: 0x00101998-0x001019af
    section, .rodata: 0x001019b0-0x00101a07
    section, .data: 0x00101a08-0x00101e7b
    section, .eh_frame: 0x00101e7c-0x00101e7f
    section, .mmu_tbl: 0x00104000-0x00107fff
    section, .init_array: 0x00108000-0x00108007
    section, .fini_array: 0x00108008-0x0010800b
    section, .bss: 0x0010800c-0x00108033
    section, .heap: 0x00108034-0x0010a03f
    section, .stack: 0x0010a040-0x0010d83f
Download Progress.
Setting PC with Program Start Address 0x00100000

XMD% connect arm hw

JTAG chain configuration
Device   ID Code        IR Length    Part Name
 1       4ba00477           4        arm_dap
 2       03727093           6        xc7z020

Enabling extended memory access checks for Zynq.
Writes to reserved memory are not permitted and reads return 0.
To disable this feature, run "debugconfig -memory_access_check disable".


CortexA9 Processor Configuration
User ID.............................0x00000000
No of PC Breakpoints................6
No of Addr/Data Watchpoints.........4

Connected to "arm" target. id = 64
Starting GDB server for "arm" target (id = 64) at TCP port no 1234
XMD% source ps7_init.tcl
couldn't read file "ps7_init.tcl": no such file or directory
XMD% pwd
XMD% source /path/to/hw_platform_spec/ps7_init.tcl
couldn't read file "/path/to/hw_platform_spec/ps7_init.tcl": no such file or directory
XMD% source C:\AAAAAAAAAA\A_data\antoine_developpement_xilinx\cartes\zedboard\test_sdcard\test_conformite_hard\test_conformite_hard.sdk\design_1_wrapper_hw_platform_0/ps7_init.tcl
couldn't read file "C:AAAAAAAAAAA_datantoine_developpement_xilinxcarteszedboard    est_sdcard    est_conformite_hard    est_conformite_hard.sdkdesign_1_wrapper_hw_platform_0/ps7_init.tcl": no such file or directory
XMD% source C:/AAAAAAAAAA/A_data/antoine_developpement_xilinx/cartes/zedboard/test_sdcard/test_conformite_hard/test_conformite_hard.sdk/design_1_wrapper_hw_platform_0/ps7_init.tcl
XMD% ps7_init
ERROR: Cannot write to target

    AP transaction error (DP CTRL_STAT=0xf0000021)
    Error Address = 0xf8000008


the only solution seams to switch off the board, or /and restart sdk


what can I do else?

0 Kudos