UPGRADE YOUR BROWSER

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# 20653

6.3 EDK, SDK - Download fails because the timeout is too short for large downloads

Description


General Description:

During the download of an executable in SDK/Eclipse, the following stack trace is generated:



"org.eclipse.cdt.debug.core.cdi.CDIException: Error initializing XMD

Debugger load: Target is not responding (timed out) at

com.xilinx.mdt.edk.debug.XMDDebugger.execLoadCommand(XMDDebugger.java:184) at

com.xilinx.mdt.edk.debug.XMDDebugger.createLaunchSession(XMDDebugger.java:104) at

org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.launch(LocalCLaunchConfigurationDelegate.java:90) at

org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:569) at

org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:788) at

org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlugin.java:955) at

org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)^M

!SUBENTRY 1 org.eclipse.cdt.launch 4 150 Aug 23, 2004 12:02:47.218

!MESSAGE Error initializing XMD Debugger load: Target is not responding

(timed out)

!STACK 0

org.eclipse.cdt.debug.core.cdi.CDIException: Error initializing XMD

Debugger load: Target is not responding (timed out) at

com.xilinx.mdt.edk.debug.XMDDebugger.execLoadCommand(XMDDebugger.java:184) at

com.xilinx.mdt.edk.debug.XMDDebugger.createLaunchSession(XMDDebugger.java:104) at

org.eclipse.cdt.launch.internal.LocalCLaunchConfigurationDelegate.launch(LocalCLaunchConfigurationDelegate.java:90) at

org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:569) at

org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:788) at

org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlugin.java:955) at

org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)^M"

Solution


This problem occurs when the ELF file that is being debugged is too large. You can work around this issue, by specifying a larger timeout value in the SDK environment preferences.To set the preferences, select the following:



Window -> Preferences -> C/C++ -> Debug -> GDB MI



The Eclipse-CDT defined default timeout for the debug operations (including the ELF file load) is ten seconds. The type of download cable used (PC-III or PC-IV) determines the maximum size of the ELF file that can be completely downloaded before the load operation times out.



However, setting a large default timeout for debugging can cause undesirable effects and can slow the overall debug behavior. Xilinx recommends the ten second default because SDK requires different timeout periods for downloading the ELF file (file might be very large), as well as for other GDB operations (such as, single-stepping). Consequently, setting a timeout of ten minutes (for example) allows enough time for the ELF file download, however, it will take ten minutes to display an error message box during single-stepping. You should set this option with these limitations in mind.
AR# 20653
Date Created 09/03/2007
Last Updated 02/22/2012
Status Archive
Type General Article