We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 59719

2013.4 EDK – System Debugger skips breakpoints during remote debug


When debugging via TCF/System Debugger to a remote machine, TCF will not show the C-source and will skip all breakpoints.

The application otherwise runs as expected.


This occurs when using System Debugger on a remote system with a different operating system than the host machine (for example a Local Windows machine connecting to a remote Linux machine).

This is because the debugger cannot find the symbols on the remote end.

There are two workarounds for this.
Work around 1:

  1. Save the desired ELF file on a drive mapped/accessible to the remote machine.
  2. In SDK on the host, click "Run > Debug Configurations"
  3. In this window, select the TCF/System Debugger debug configuration you are using and click on the "Application" tab.
  4. Check the "Stop at program entry" box.
  5. Click Apply > Click Debug.
  6. In the Debug Perspective View of SDK (Window > Open Perspective > Debug) right-click on your desired processor and select "Symbol Files"
  7. Click "Add" and insert the path to your ELF file in the format the remote machine accepts.
    (If the remote machine is Linux based, your path will start with "/". If it is Windows based, it will start with something like "c:/")
  8. Click OK. You should see the debug window update with your source code, and stepping/breaking will work as expected.
Work-around 2:
Use the GDB debugger instead of TCF/System Debugger.
The TCF/System Debugger is the preferred method of debug.
AR# 59719
Date Created 03/10/2014
Last Updated 09/26/2014
Status Active
Type General Article
  • Vivado Design Suite - 2013.4