Actions
Forum Thread Details
  • State Verified Answer
  • Replies 3 replies
  • Subscribers 298 subscribers
  • Views 970 views
  • Users 0 members are here
Related

Error: No Elf file associated with target  - ZedBoard Concepts, Tools, Techniques Tutorial

rathseg
I'm doing the latest Zedboard Concepts, Tools, Techniques tutorial which appears to be for Vivado 2014.2 ( I am using Vivado 2016.4 ) and I have gotten the following error when I tried Step 13 ("Run Hello World") from section 2.1.2:
 
01:51:28 INFO : Registering command handlers for SDK TCF services
01:51:28 INFO : Launching XSCT server: xsct.bat -interactive C:\zedboard\zedboard_ctt_2\retry_zedboard_tutorial\retry_zedboard_tutorial.sdk\temp_xsdb_launch_script.tcl
01:51:29 INFO : XSCT server has started successfully.
01:51:30 INFO : Successfully done setting XSCT server connection channel  
01:51:30 INFO : Successfully done setting SDK workspace  
01:51:30 INFO : Processing command line option -hwspec C:/zedboard/zedboard_ctt_2/retry_zedboard_tutorial/retry_zedboard_tutorial.sdk/system_wrapper.hdf.
01:53:24 INFO : Connected to target on host '127.0.0.1' and port '3121'.
01:59:51 ERROR : Unexpected error while launching program.
java.lang.RuntimeException: Error while running ps7_init method.
No Elf file associated with target
 
 
at com.xilinx.sdk.targetmanager.internal.TM.run_ps7_init(TM.java:1089)
at com.xilinx.sdk.debug.core.XilinxAppLaunchConfigurationDelegate.runTargetSetup(XilinxAppLaunchConfigurationDelegate.java:514)
at com.xilinx.sdk.debug.core.XilinxAppLaunchConfigurationDelegate.runApplication(XilinxAppLaunchConfigurationDelegate.java:616)
at com.xilinx.sdk.debug.core.XilinxAppLaunchConfigurationDelegate.launch(XilinxAppLaunchConfigurationDelegate.java:309)
at com.xilinx.sdk.debug.ui.XilinxAppLaunchDelegateWrapper.launch(XilinxAppLaunchDelegateWrapper.java:31)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
 
 
Everything seemed to be going fine until this point.  The Elf file was made and does exist in my project directories.  I tried searching for the searching for error message to see if that could give me a better idea of what was causing the error but found nothing ( I searched for "elf" in all the various ps_init files ).  The USB JTAG is connected and when you view its properties the SDK sees it.  The UART is also working from when I tested it during the UART setup guide ( and I did change the jumper settings to match the need of this tutorial ).  Just in case I missed something in the tutorial I started from scratch an second time and still got the exact same problem.  I'm out of ideas to debug this further.  Any ideas?
 
One question I have is that is that on step 11 of section 2.1.1.2 ( Generate Block Design ) there were synthesis options and the tutorial said nothing about them.  I left it as the default which was "Out of Context per IP" and things seemed to go ok in that step but I don't know if it will affect things further down the tutorial.  Should I leave that at the default?
 
  • 0

    Hi Rathseg,

    I am going to suggest that you go through the tutorial using Vivado/SDK 2014.2. The reason for this is that as Vivado releases updates, the various IPs, Drivers, design Flow tends to change/tweak a bit. For instance you noticed one difference yourself as you asked about the generate block design pop up window(default selection should be fine.).

    So please run through the tutorial using the 2014.2 tool version and report back if this solved your issue.

    --Josh

  • 0

    Yeah, that solved it.  Thanks.

     

    Given how basic that tutorial was though, does that mean that the zedboard is not really supported on anything other than 2014.2?  Should I only use 2014.2 for all my work with the zedboard?  The differences between 2014.2 and 2016.4 seemed to be small user interface differences, not much of substance, so unless a behind the scenes default setting/value got changed it seems like it should have still worked.  I went through all the Release notes for the versions after 2014.2 and it looks like there are a fair bit of performance improvements to Vivado, which while not essential would be nice to have. 

  • 0

    Hi Rathseg,

    We always suggest to use the newest version of Vivado when doing your own/new development. The Zedboard and all of our Zynq producs are most defeinitly supported in Vivado 2016.4. Like I said in the previous post, your issue most likely stems from a driver/IP update. If you look at the change log of various IPs/Drivers you used I am sure there were some significant changes in the last two years(2014.2 was release about 2 years ago).

    --Josh