Vivado Crashing on startup

[Anonymous]

I have just installed the 14.4 webpack with vivado. The ISE boots and appears to work but when I run vivado I get the following error and the GUI closes. Any help would be appreciated. I can post the error report referenced is attached.

F:\Xilinx\14.4\ISE_DS>vivado

****** Vivado v2012.4 (64-bit)
**** Build 222254 by xbuild on Tue Dec 18 05:21:09 MST 2012
** Copyright 1986-1999, 2001-2012 Xilinx, Inc. All Rights Reserved.

WARNING: [Vivado 15-2] No 'Implementation' license found.
INFO: [Device 21-36] Loading parts and site information from F:/Xilinx/14.4/ISE_
DS/PlanAhead/data/parts/arch.xml
Parsing RTL primitives file [F:/Xilinx/14.4/ISE_DS/PlanAhead/data/parts/xilinx/r
tl/prims/rtl_prims.xml]
Finished parsing RTL primitives file [F:/Xilinx/14.4/ISE_DS/PlanAhead/data/parts
/xilinx/rtl/prims/rtl_prims.xml]
start_gui
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007fcf39b1355, pid=5240, t
id=2452
#
# JRE version: 7.0_07-b11
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.3-b01 mixed mode windows-amd64
compressed oops)
# Problematic frame:
# C [msvcrt.dll+0x1355] free_dbg+0x5
#
# Failed to write core dump. Minidumps are not enabled by default on client vers
ions of Windows
#
# An error report file with more information is saved as:
# F:\Xilinx\14.4\ISE_DS\hs_err_pid5240.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

F:\Xilinx\14.4\ISE_DS>

[ankury]

Hi,

Please check the Java version With the ISE Design Suite 14.1 release, Plan Ahead/ Vivado tool will be installed with and use Java 1.7.0

ankury

[x_arrange]

Have the same problem on Windows 7 with Vivado 2013.4.

Tried Java 1.7.0 and 1.8.0.

By the way, JRE comes with Vivado at Vivado\2013.4\tps\win32\jre so Vivado uses its own, not that installed in system.

[vijayak]

Hi,
Please check the health of the downloaded software.

You may try the following to check the installation status.

To check if the file was downloaded correctly, MD5 checksum value of downloaded file should match with MD5 sum value from where file was downloaded (Xilinx website-->support-->download).
MD5sum can be downloaded from http://www.fastsum.com/

After feeding your .tar file to FastSum tool, it will display Checksum\state value of file.

Compare the checksum\state column value with the value provided at download page on Xilinx.
If there is mismatch, it means that the downloaded files are not complete or corrupted.

You must again download Vivado from Xilinx website. http://www.xilinx.com/support/download/index.htm

If MD5 checksum value matches with downloaded file then Use 7zip software to unzip since 7-zip was used for zipping the software.
It can be downloaded from http://www.7-zip.org/ (Please keep the hierarchy intact when unzipping)

It is recommended to turn off anti-virus when unzipping or extracting downloaded file.

[x_arrange]

Hi, Vijay

MD5 is equal - nothing wrong with tar and extracted files.

Thanks

[vuppala]

Hi,

Try opening Vivado using the following command:

C:\Xilinx\14.4\ISE_DS> vivado -jvm Xmx20148m

If the above command didn't help, run xinfo (Start --> All Programs --> Xilinx Design Tools --> ISE Design Suite 14.4 --> Accessories --> Xinfo System Checker) and attach it here.

Thanks

[x_arrange]

Hi

I hope you meant -Xmx2048m. I can only dream about 20Gb on laptop :)

I have Windows 7 32-bit with 3Gb RAM.

My java (1.8.0) was unable to allocate 2Gb. Maximum that it could allocate is ~1100Mb.

Could it be reason for Vivado crash?

Thanks

[x_arrange]

I performed some research - looks like for Windows 7 32-bit it's impossible to allocate 2Gb for Java

By the way here is my xinfo.txt

[vuppala]

Hi,

Run the Visual C++ redistribution executables located at:
<installpath>\tps\win32\vcredist_x86.exe (e.g., C:\Xilinx\Vivado\2012.4\tps\win32\vcredist_x86.exe)

Thanks

[tomasz.janicki.tj]

That also has helped me on Win10 using Vivado, I had to choose Repair.