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!

cancel
Showing results for 
Search instead for 
Did you mean: 
Scholar muravin
Scholar
10,057 Views
Registered: ‎11-21-2013

VIVADO 2015.1 fails running with input XML script

Hi All,

 

As subject - can someone please tell us what is wrong?  VIVADO 2015.1, Linux x64.

 

Thank you in advance. Attached there are 3 files:

1. Eclipse2 - we've been running with 2014.4 and earlier revisions, no problems running XSDK with XML input script

2. Eclipse1 - newly created with 2015.1 (the different is paths only), the error message we get in the VIVADO is given below.

3. log - an output of the SDK when running the following command (all variables are set correctly)

" sdk -wait -script [current_project]/[current_project].sdk/[current_project].xml -workspace $WS "

 

****** Xilinx Software Development Kit
****** SDK v2015.1 (64-bit)
  **** SW Build 1215546 on Mon Apr 27 19:19:00 MDT 2015
    ** Copyright 1986-2015 Xilinx, Inc. All Rights Reserved.

Launching SDK with command /opt/Xilinx/SDK/2015.1/eclipse/lnx64.o/eclipse -data eclipse1/eclipse1.sdk/sdk_workspace -nosplash -application org.eclipse.ant.core.antRunner -buildfile eclipse1/eclipse1.sdk/eclipse1.xml -vmargs -Xms64m -Xmx512m
Buildfile: eclipse1/eclipse1.sdk/eclipse1.xml

main:

BUILD FAILED
/home/IGNIS/vmuravin/projects/orchestra/vivado/eclipse/eclipse1/eclipse1/eclipse1.sdk/eclipse1.xml:3: Problem: failed to create task or type createHwProject
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.

Vladislav Muravin
0 Kudos
22 Replies
Explorer
Explorer
10,013 Views
Registered: ‎11-12-2007

Re: VIVADO 2015.1 fails running with input XML script

Same issue here.

I guess Xilinx has changed the name of a well working command-line tool *again* :-(

0 Kudos
Scholar muravin
Scholar
10,010 Views
Registered: ‎11-21-2013

Re: VIVADO 2015.1 fails running with input XML script

The issue is bigger than that. Even if I follow that step-by-step XSDK or XSCT commands, the build of the SDK fails on some missing libraries, and I don't even know what they are or how to link them.

I have no issues if tools are released with bugs, appreciating that they are complicated etc but having at least an example would be helpful.

Xilinx, would you mind please responding to the original post?
Vladislav Muravin
0 Kudos
Scholar muravin
Scholar
9,970 Views
Registered: ‎11-21-2013

Re: VIVADO 2015.1 fails running with input XML script

Webcase 1048995 has been opened. Updates to follow. If anyone figured this one out, please let us know in this post.
Thanks
Vlad
Vladislav Muravin
0 Kudos
Scholar sampatd
Scholar
9,931 Views
Registered: ‎09-05-2011

Re: VIVADO 2015.1 fails running with input XML script

Yes, this is an issue that we have indeed seen with SDK 2015.1. We are actively pursuing towards a fix. Please watch this space for an update.

Thanks.
0 Kudos
Scholar muravin
Scholar
9,912 Views
Registered: ‎11-21-2013

Re: VIVADO 2015.1 fails running with input XML script

Okay, thanks. I am open to other alternatives and workaround as so far was not able to run even SDK in batch mode.

Cheers Vlad

Vladislav Muravin
0 Kudos
Scholar sampatd
Scholar
9,900 Views
Registered: ‎09-05-2011

Re: VIVADO 2015.1 fails running with input XML script

Hi Vlad,

XSCT (SDK 2015.1) does not support xml scripts. XSCT is purely TCL based.

You can achieve the same using xsct commands:
http://www.xilinx.com/support/documentation/sw_manuals/xilinx2015_1/SDK_Doc/SDK_concepts/sdk_c_batch_mode.html
0 Kudos
Scholar stephenm
Scholar
9,891 Views
Registered: ‎05-06-2012

Re: VIVADO 2015.1 fails running with input XML script

I have created an AR for the xsct. this will be public in the next day or so. All this can be found in the SDK help search found xsct.

With respect to this issue. This is a limitation. Only tcl files are excepted.

Can you let me know if you see other issues with xsct commands in generating your SDK projects please?
0 Kudos
Explorer
Explorer
9,882 Views
Registered: ‎11-12-2007

Re: VIVADO 2015.1 fails running with input XML script

Hi,

thanks that helps alot.

 

But xsct fauils when I try to generate a device-tree:

I use these commands in a tcl script, variables are all set correct.

sdk set_workspace $(WS_DEVTREE)
sdk set_user_repo_path $(DEVTREE_REPO)
sdk create_hw_project -name $(HW_PROJ_NAME) -hwspec $(HDF)
sdk create_bsp_project -name $(DEVTREE_PROJ_NAME) -hwproject (HW_PROJ_NAME) -proc ps7_cortexa9_0 -os device_tree
	

 

And I get the follwoing Error:

 

rlwrap: warning: your $TERM is 'xterm' but rlwrap couldn't find it in the terminfo database. Expect some problems.
Got $XILINX_SDK: /opt/Xilinx/SDK/2015.1
Hardware platform project 'system_hw_platform_0' created successfully.
org.eclipse.core.runtime.CoreException: Error generating bsp sources. Please check the SDK.log file under the workspace folder for further details.
at com.xilinx.sdk.sw.SwPlatformCreator.createFromOs(SwPlatformCreator.java:102)
at com.xilinx.sdk.sw.core.BspProjectHandler.createBsp(BspProjectHandler.java:61)
at com.xilinx.sdk.sw.core.BspProjectHandler.access$0(BspProjectHandler.java:52)
at com.xilinx.sdk.sw.core.BspProjectHandler$1.run(BspProjectHandler.java:42)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2327)
at com.xilinx.sdk.sw.core.BspProjectHandler.execute(BspProjectHandler.java:39)
at com.xilinx.sdk.cmdline.application.CmdLineHelper.createBsp(CmdLineHelper.java:186)
at com.xilinx.sdk.cmdline.application.CmdLineProjectCreator.createBspProject(CmdLineProjectCreator.java:178)
at com.xilinx.sdk.cmdline.application.CmdLineProjectCreator.createProject(CmdLineProjectCreator.java:61)
at com.xilinx.sdk.cmdline.application.CmdLineProjectCreator.start(CmdLineProjectCreator.java:31)
at com.xilinx.sdk.cmdline.service.SdkTcfService.executeCommand(SdkTcfService.java:230)
at com.xilinx.sdk.cmdline.service.SdkTcfService.access$1(SdkTcfService.java:221)
at com.xilinx.sdk.cmdline.service.SdkTcfService$CommandServer.command(SdkTcfService.java:100)
at com.xilinx.sdk.cmdline.service.SdkTcfService$CommandServer.command(SdkTcfService.java:59)
at org.eclipse.tcf.core.AbstractChannel.handleInput(AbstractChannel.java:960)
at org.eclipse.tcf.core.AbstractChannel.access$0(AbstractChannel.java:918)
at org.eclipse.tcf.core.AbstractChannel$1$1.run(AbstractChannel.java:293)
at org.eclipse.tcf.EventQueue.run(EventQueue.java:95)
at java.lang.Thread.run(Thread.java:745)
Failed to create BSP project 'device_tree_bsp_0'
Error in startup script:
Failed to create BSP project device_tree_bsp_0
invoked from within
"::tcf::eval -progress {apply {{msg} {puts $msg}}} {tcf_send_command tcfchan#0 Xsdk createProject {o{Type s Name s HwProject s Proc s Os s}} e {{Type bsp Name device_tree_bsp_0 HwProject system_hw_platform_0 Proc ps7_cortexa9_0 Os device_tree}}}"
(procedure "::tcf::send_command" line 4)
invoked from within
"tcf send_command $chan Xsdk createProject "o{$fmt}" e [list $data]"
(procedure "::xsdb::sdk::create_bsp_project" line 37)
invoked from within
"sdk create_bsp_project -name device_tree_bsp_0 -hwproject system_hw_platform_0 -proc ps7_cortexa9_0 -os device_tree"
(file "out/sw/xsct.tcl" line 5)
make: *** [new_devtree2] Error 1

0 Kudos
Scholar sampatd
Scholar
9,877 Views
Registered: ‎09-05-2011

Re: VIVADO 2015.1 fails running with input XML script

I will check if  I can reproduce the issue using sdk commands 

 

Meanwhile, try if these hsi commands work instead:

 

sdk set_workspace $(WS_DEVTREE)
hsi::open_hw_design Path\\to\\system.xml
hsi::current_hw_design hsi::set_repo_path $(DEVTREE_REPO)
hsi::create_sw_design swdesign -proc ps7_cortexa9_0 -os device_tree
hsi::current_sw_design
hsi::generate_bsp -dir bsp_directory

 

 

0 Kudos
Explorer
Explorer
9,767 Views
Registered: ‎11-12-2007

Re: VIVADO 2015.1 fails running with input XML script

Thanks four your help. Here is tho output from the hsi commands:

 

 

****** Xilinx Software Commandline Tool (XSCT) v2015.1
  **** Build date : Apr 27 2015-19:19:07
    ** Copyright 1986-2015 Xilinx, Inc. All Rights Reserved.


Got $XILINX_SDK: /opt/Xilinx/SDK/2015.1
xsct%                                                                                     
xsct% sdk set_workspace out/sw/dt                                                         
xsct% hsi::open_hw_design out/hw/system.hdf                                               
system                                                                                    
xsct% hsi::current_hw_design                                                              
system
xsct% hsi::set_repo_path ../vivado_ip_repository/toolchain/device-tree-xlnx-xilinx-v2014.4
xsct% hsi::create_sw_design swdesign -proc ps7_cortexa9_0 -os device_tree                                  
swdesign
xsct% hsi::current_sw_design                                                                               
swdesign
xsct% hsi::generate_bsp -dir device_tree_bsp_0                                                             
ERROR: [Common 17-39] 'hsi::generate_bsp' failed due to earlier errors.                                    

xsct%    
0 Kudos
Scholar muravin
Scholar
9,760 Views
Registered: ‎11-21-2013

Re: VIVADO 2015.1 fails running with input XML script

Thanks all. I am going to try these later today.

 

In the meanwhile, note that the XML script related issue is real and there is a CR 862509 on this.

 

BR

Vlad

Vladislav Muravin
0 Kudos
Xilinx Employee
Xilinx Employee
9,753 Views
Registered: ‎01-22-2014

Re: VIVADO 2015.1 fails running with input XML script

SDK headless mode with xml script file is not supported anymore. Please use .tcl script and run in xsct.

0 Kudos
Scholar sampatd
Scholar
9,740 Views
Registered: ‎09-05-2011

Re: VIVADO 2015.1 fails running with input XML script

@timo-ge I had this working for a third party repository. Let me also check it for device tree.

can you try the command hsi::get_os to check if you have device tree listed as one of the OS?
0 Kudos
Explorer
Explorer
9,735 Views
Registered: ‎11-12-2007

Re: VIVADO 2015.1 fails running with input XML script

@sampatd hsi::get_os throws an error:

 

xsct% sdk set_workspace out/sw/dt 
xsct% hsi::open_hw_design out/hw/system.hdf
system
xsct% hsi::current_hw_design
system
xsct% hsi::set_repo_path ../vivado_ip_repository/toolchain/device-tree-xlnx-xilinx-v2014.4
xsct% hsi::get_os
ERROR: [Common 17-39] 'hsi::get_os' failed due to earlier errors.

xsct% hsi::create_sw_design swdesign -proc ps7_cortexa9_0 -os device_tree
swdesign
xsct% hsi::current_sw_design
swdesign
xsct% hsi::get_os
device_tree
xsct% hsi::generate_bsp -dir device_tree_bsp_0
ERROR: [Common 17-39] 'hsi::generate_bsp' failed due to earlier errors.

  

My repository which I add with set_repo_path ist the downloaded device-tree from Xilinx GIT.

 

I just found out that although I have an error on the console, it created a folder called device_tree_bsp_0

and It contains the skeleton.dtsi, system.mss and zynq-7000.dtsi.

Just the PL part of the device-tree is missing. I have some custom IP in my block design, maybe this is an issue?

 

 

0 Kudos
Scholar stephenm
Scholar
9,724 Views
Registered: ‎05-06-2012

Re: VIVADO 2015.1 fails running with input XML script

Hey Guys,

 

I have been testing this today in XSCT 2015.1:

 

proc sdk_test {hdf workspace os} {
 sdk set_workspace $workspace
 sdk set_user_repo_path ./repo
 sdk create_hw_project -name hw_0 -hwspec $hdf
 sdk create_bsp_project -name bsp_0 -hwproject hw_0 -proc ps7_cortexa9_0 -os $os
 sdk build_project -type bsp -name bsp_0
}

 

I sourced this, and run the proc

sdk_test design_1_wrapper workspace device-tree

or

sdk_test design_1_wrapper workspace freertos_zynq

 

My repo structure is:

repo/bsp/device-tree

                /freertos

0 Kudos
Scholar sampatd
Scholar
9,714 Views
Registered: ‎09-05-2011

Re: VIVADO 2015.1 fails running with input XML script

cd c:/forums
sdk set_workspace ./device_tree_workspace
sdk create_hw_project -name test -hwspec workspace\\ZC702_hw_platform\\system.hdf
hsi::open_hw_design workspace\\ZC702_hw_platform\\system.hdf
hsi::current_hw_design
hsi::set_repo_path device-tree-xlnx-xilinx-v2015.1

hsi::create_sw_design swdesign -proc ps7_cortexa9_0 -os device_tree
hsi::current_sw_design
hsi::generate_bsp -dir dt_2015_1_bsp

Works well with 2015.1 device tree

0 Kudos
Scholar stephenm
Scholar
9,708 Views
Registered: ‎05-06-2012

Re: VIVADO 2015.1 fails running with input XML script

Also, please see the AR below:

http://www.xilinx.com/support/answers/64200.html

0 Kudos
Scholar muravin
Scholar
9,398 Views
Registered: ‎11-21-2013

Re: VIVADO 2015.1 fails running with input XML script

Hi All,

 

First of all, thanks to Amarjit for supporting us on Webcase 1048995.

 

I don't believe however this issue is over, and I would like to ask Xilinx to please try to get this addressed in 2015.2, i.e. we still cannot build the design with SDK or XSCT in batch mode seamlessly. We still need to do this semi-manually.

 

The main reasons for this is that the garbage collector option in both compiler and linked was ON in 2014.4 but it is OFF in 2015.1

 

Also, there is no way to set the compiler and the linker options such as garbage collection or the optimization level -O3 thru either HSI, XSCT or SDK. Please address this in 2015.2; I don't believe that asking for control of the compiler/linker options thru TCL is asking for too much.

 

Thank you

Vlad

 

Vladislav Muravin
0 Kudos
Scholar stephenm
Scholar
9,383 Views
Registered: ‎05-06-2012

Re: VIVADO 2015.1 fails running with input XML script

This will not be addressed in 2015.2, maybe in 2015.3.

 

Users can work around this by changing the MAKE files directly.

 

I have created a script below, that will create an SDK worksapce which contains two apps; hello, and my_app. My app uses the code from a custom driver (this uses the import_sources feature). In my app I need to use the std=c99 compiler option. I created a proc to do this. This will find the make file, and modify this, by addingthe compiler option.

 

Note: I only done this for the mb compiler, so if you want to use this as a reference for any other compier then you will need to change this.

 

Note the script (script.tcl) has two main procs (sdk_workspace for 2015.1, and hsi_workspace for 2014.4) to run open the XSCT and source the script. To run, type sdk_workspace design_1_wrapper.hdf sdk_ws

0 Kudos
Scholar muravin
Scholar
7,374 Views
Registered: ‎11-21-2013

Re: VIVADO 2015.1 fails running with input XML script

Thanks Steve for the information, apprecaite it.

 

I tried to follow the HSI path, but with 2015.1 (note we are using Linux x64)

 

I get to the point of hsi::generate_app $options but I get the following error:

 

ERROR: [Hsi 55-1414] App empty_application is not Found in repositories
ERROR: [Hsi 55-1414] App empty_application is not Found in repositories
ERROR: [Hsi 55-1450] Error: running generate_bsp.
ERROR: [Hsi 55-1558] Software Design /system is not found

 

I think I did load correctly all the Xilinx SDK repositories with hsi::set_sdk_repo pointing to thge /lib/sw_apps_linux/

 

Can anyone please tell me why I am getting this error?

 

Thanks

Vlad

Vladislav Muravin
0 Kudos
Scholar muravin
Scholar
7,369 Views
Registered: ‎11-21-2013

Re: VIVADO 2015.1 fails running with input XML script

ok, I think I have figured the last one out, if I use only " hsi::set_repo_path -verbose $env(XILINX_SDK)/data/embeddedsw/lib ", this command loads all the necessary repositories (I was goig too deep in the hierarchy I suppose)

Vladislav Muravin
0 Kudos
Scholar muravin
Scholar
7,366 Views
Registered: ‎11-21-2013

Re: VIVADO 2015.1 fails running with input XML script

Steve et all,

 

I cannot make it work, sorry. I have a simple Microblaze project, no biggy. And we are on Linux.

 

I think the reason is that all the options set up in gui are no longer reflected in the makefile. For example, I wanted to add the following options to the make file's mb-gcc line:

1. -O3

2. -ffunction-sections -fdata-sections compiler flags

3. --gc-sections (garbage collector) linker flag

 

If I try using either sed (linux string editor) or even plain TCL or even manually changing the makefile, then running make still compiles with errors.

 

However, changing these options thru gui does not change the makefile at all, all changes are reflected in either .project or .cproject files. I find it of course very disappointing that simple things like that cannot be modified in a simple set_property command or something similar.

 

Regards

Vlad

Vladislav Muravin
0 Kudos