Showing results for 
Show  only  | Search instead for 
Did you mean: 
Registered: ‎08-25-2016

Vivado 2016.1 SDK launch problem

Hi All,
After successfully running the GPIO example from the Digilemt website, I'm trying to do the "Getting started with Microblaze" example from the Digilent website.

Everything runs fine, until I get to the point where the HelloWorld project is created in the SDK. I consistently get the error message: "Project cannot be created" "Reason: Internal Error:" "Failed to closesw "/home/<user>/Arty/Arty_GSMB/Arty_GSMB.sdk/helloworld_bsp/system.mss"" "Reason: Cannot close sw design '/home/<user>/Arty/<ProjectDir>/Arty_GSMB.sdk/helloworld_bsp/system.mss'. Design is not opened in the current session."

I'm using Vivado 2016.2 on Ubuntu 14 LTS, but I get the same response on Ubuntu 16 LTS.


I tried the example with root privileges, but still the same response.

I've searched the Internet for this problem, but came up blank, until now.
Can anyone shed some light on this problem?


Tags (4)
0 Kudos
8 Replies
Xilinx Employee
Xilinx Employee
Registered: ‎08-01-2008

1. check installation guide it will help you to understand hardware requirement
2. It may be your project corrupted you can try with new project
3. It may be issue with your project path location . keep the path short and avoid special character in project path
4. try some other example project

5. You may try with vivado 2016.2 which is latest version of tool
Thanks and Regards
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.
0 Kudos
Xilinx Employee
Xilinx Employee
Registered: ‎08-02-2007



just to rule out if this is specific to your environment, would that be possible to share the .hdf of your example design?



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.
0 Kudos
Registered: ‎08-25-2016

Thank you for your suggestions:


1. As I am able to run the GPIO example, I don't think it has to do with hw requirements. The example that I have problems with comes from the Digilent website,and is for the Arty board. And it is before I even start to download things to the board. The problem begins when I try to create a project in the SDK.

2. I have tried this project half a dozen times, on different computers, and I always get the same response.

3. That half a dozen trials include some with short, simple names.

4. See my answer to 1. The GPIO example works fine. But yes, I'll try the MicroBlaze server example next.



0 Kudos
Registered: ‎08-25-2016

Thanks for looking into this problem.


Both ~/Arty/Arty_GSMB/Arty_GSMB.sdk/system_wrapper_hw_platform_0/system.hdf and ~/Arty/Arty_GSMB/Arty_GSMB.sdk/system_wrapper.hdf are attached.


Hope this helps...

0 Kudos
Registered: ‎09-05-2016

I have seen this problem as well in Vivado 2016.2, running under Ubuntu 14.04.5 LTS.

In SDK.log I see what might be a related error message


20:22:13 INFO  : Launching XSDB server: xsdb -n -interactive /home/jao/Documents/Digilent/Arty/Projects/getting_started_microblaze/getting_started_m\


20:22:16 INFO  : XSDB server has started successfully.

20:22:20 INFO  : Processing command line option -hwspec /home/jao/Documents/Digilent/Arty/Projects/getting_started_microblaze/getting_started_microb\


20:25:26 ERROR : (XSDB Server)ERROR: [Hsi 55-1545] Problem running tcl command ::sw_standalone_v5_5::post_generate : couldn't execute "mb-ar": no su\

ch file or directory

    while executing

"exec $archiver -d $libgloss_a _interrupt_handler.o"

    (procedure "::sw_standalone_v5_5::post_generate" line 18)

    invoked from within

"::sw_standalone_v5_5::post_generate standalone"


20:25:26 ERROR : (XSDB Server)ERROR: [Hsi 55-1443] Error(s) while running TCL procedure post_generate()


20:25:26 ERROR : (XSDB Server)ERROR: [Hsi 55-1450] Error: running generate_bsp.


20:25:27 ERROR : Failed to closesw "/home/jao/Documents/Digilent/Arty/Projects/getting_started_microblaze/getting_started_microblaze.sdk/Hello_world\


Reason: Cannot close sw design '/home/jao/Documents/Digilent/Arty/Projects/getting_started_microblaze/getting_started_microblaze.sdk/Hello_world_bsp\


0 Kudos
Registered: ‎09-05-2016

In my case the key to the problem is

couldn't execute "mb-ar": no such file or directory


The error message is misleading: the file exists, but it is a 32-bit ELF executable and the default 14.04 LTS for amd64 desktop does not include 32-bit shared libraries, and in fact the dynamic linker ldd can't even recognize the file as executable.


To diagnose

$ locate mb-ar


$ file /opt/Xilinx/SDK/2016.2/gnu/microblaze/lin/bin/mb-ar
/opt/Xilinx/SDK/2016.2/gnu/microblaze/lin/bin/mb-ar: symbolic link to `microblaze-xilinx-elf-ar'


$ readlink -f /opt/Xilinx/SDK/2016.2/gnu/microblaze/lin/bin/mb-ar



$ file /opt/Xilinx/SDK/2016.2/gnu/microblaze/lin/bin/microblaze-xilinx-elf-ar
/opt/Xilinx/SDK/2016.2/gnu/microblaze/lin/bin/microblaze-xilinx-elf-ar: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped


This proves the file exists, and indeed is a 32-bit executable.


$ /opt/Xilinx/SDK/2016.2/gnu/microblaze/lin/bin/microblaze-xilinx-elf-ar --version

bash: no such file or directory 


You will get advice from Google search results to install a whole parallel architecture i386 but this is overkill. But to get started, you need ldd to be able to report the dependencies, which can be achieved by


$ sudo apt-get install libc6-i386


Now, see what libraries are required


$ ldd -d /opt/Xilinx/SDK/2016.2/gnu/microblaze/lin/bin/microblaze-xilinx-elf-ar => (0xf7760000) => not found => /lib32/ (0xf759c000)
/lib/ (0x56610000) happens to be provided by lib32z1:


$ sudo apt-get install lib32z1


$ ldd -d /opt/Xilinx/SDK/2016.2/gnu/microblaze/lin/bin/microblaze-xilinx-elf-ar => (0xf77bb000) => /usr/lib32/ (0xf7788000) => /lib32/ (0xf75dd000)
/lib/ (0x56559000)


Now it should be able to run

$ /opt/Xilinx/SDK/2016.2/gnu/microblaze/lin/bin/microblaze-xilinx-elf-ar --version
GNU ar (crosstool-NG 1.20.0)
Copyright 2012 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) any later version.
This program has absolutely no warranty.


And the SDK scripts should sucessfully complete.

Registered: ‎09-05-2016

In order to do useful work, however, you will additionally need to get mb-gcc to run (using a troubleshooting process like my previous reply)


$ ldd -d /opt/Xilinx/SDK/2016.2/gnu/microblaze/lin/bin/microblaze-xilinx-elf-gcc => (0xf7787000) => not found => /lib32/ (0xf7728000) => not found => /lib32/ (0xf757d000)
/lib/ (0x56583000)


This can be satisfied using


$ sudo apt-get install lib32stdc++6

Registered: ‎05-13-2017

For novices (like myself), the relevant libraries using yum (on CentOS) are:

  • sudo yum install zlib.i686
  • sudo yum install libstdc++.i686

Hope it helps as a reference. Thank you, jaoswald, for the heavy lifting.