Can't build BSP in headless 2014.2

Question

I have a BSP project that I want to import and generate/build headless in 2014.2.
I imported it and the hw platform with no issues by doing:
C:\Xilinx\SDK\2014.2\eclipse\win64.o\eclipsec.exe -vm C:\Xilinx\SDK\2014.2\tps\win64\jre\bin  -nosplash -application org.eclipse.cdt.managedbuilder.core.headlessbuild -import hw_platform -import standalone_bsp -data . -vmargs -Dorg.eclipse.cdt.core.console=org.eclipse.cdt.core.systemConsole
I've then tried using both:
C:\Xilinx\SDK\2014.2\eclipse\win64.o\eclipsec.exe -vm C:\Xilinx\SDK\2014.2\tps\win64\jre\bin -nosplash -application com.xilinx.sdk.sw.BspBuilder standalone_bsp -data . -vmargs -Dorg.eclipse.cdt.core.console=org.eclipse.cdt.core.systemConsole
and:
C:\Xilinx\SDK\2014.2\eclipse\win64.o\eclipsec.exe -vm C:\Xilinx\SDK\2014.2\tps\win64\jre\bin  -nosplash -application org.eclipse.cdt.managedbuilder.core.headlessbuild -build all -data . -vmargs -Dorg.eclipse.cdt.core.console=org.eclipse.cdt.core.systemConsole
The former crashes with no error messages and no significant log output. The latter simply does nothing. The hw platform is an Artix7 microblaze system created in Vivado 2014.2. The .metadata/.log is attached.

Answer 1

Hi,
The new Xilinx software command-line tool is headless and based on Tcl which is available in the SDK installation. This tool provides the Tcl interactive shell and you can use all of the supported commands.
The Xilinx software command-line tool is a scriptable command line interface to run SDK commands, XSDB commands and HSI commands. XSCT can be launched from the Start menu under Xilinx Design Tools > SDK 2015.1.
The following user flow describes how you can use the SDK batch mode.
1.      Start sdk batch mode using the command:
         xsct
2.      Set the workspace (where you want to create SDK projects) using the command:
         sdk set_workspace <Workspace Path>
3.      If you have any local repositories, set the user repository path using the command:
         sdk set_user_repo_path <Repository Path>
4.      Create a hardware project using the command:
         sdk create_hw_project -name <hw project> -hwspec <.hdf/.xml path>
5.      Create a BSP for the hardware project using the command:
     sdk create_bsp_project -name <bsp project name> -hwproject <hw project> -proc <processor> -os <OS Name>
6.      Create an application project using the command:
        sdk create_app_project -name <Application Name> -hwproject <hw Project> -proc <processor> -os <Os Name> -lang <Language> -app <Application Template> -bsp <Bsp Project>
7.      Build the projects using the command:
        sdk build_project
8.      Clean the projects using the command:
         sdk clean_project
You can run your Tcl script file using the xsct -source test.tcl command.
Example test.tcl
#!/usr/bin/tclsh
sdk set_workspace /tmp/test1
sdk create_hw_project -name hw_0 -hwspec system.hdf
sdk create_bsp_project -name bsp_0 -hwproject hw_0 -proc microblaze_0 -os standalone
sdk create_app_project -name helloworld -hwproject hw_0 -proc microblaze_0 -os standalone -lang C -app {Hello World} -bsp bsp_0
sdk build_project -type bsp bsp_0
sdk build_project -type app helloworld
sdk clean_project -type bsp bsp_0
sdk clean_project -type all
sdk build_project -type all
exit
To support the XSCT feature a complete tutorial answer record #64200 is available.
Please refer to http://www.xilinx.com/support/answers/64200.html to get complete solution.
Regards
Praveen
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.