07-08-2013 03:31 AM
I am using vivado in the ubuntu os, when i am typing vivado in the shell it shows
****** Vivado v2013.1
**** Build 248050 by xbuild on Wed Mar 27 17:13:27 MDT 2013
** Copyright 1986-1999, 2001-2013 Xilinx, Inc. All Rights Reserved.
WARNING: [Vivado 15-19] WARNING: No 'Implementation' license found. This message may be safely ignored if a Vivado WebPACK or device-locked license, common for board kits, will be used during implementation.
INFO: [Device 21-36] Loading parts and site information from /Xilinx_Vivado/Vivado/2013.1/data/parts/arch.xml
Parsing RTL primitives file [/Xilinx_Vivado/Vivado/2013.1/data/parts/xilinx/rtl/prims/rtl_prims.xml]
Finished parsing RTL primitives file [/Xilinx_Vivado/Vivado/2013.1/data/parts/xilinx/rtl/prims/rtl_prims.xml]
INFO: [Common 17-362] Using Tcl App repository from '/Xilinx_Vivado/Vivado/2013.1/data/XilinxTclStore'.
INFO: [Common 17-364] Updating Tcl app persistent manifest '/home/chandu/.Xilinx/Vivado/tclapp/manifest.tcl'
Abnormal program termination (11)
Please check '/home/chandu/Desktop/hs_err_pid11044.log' for details
the log file contains
07-25-2013 09:01 AM
I just started receiving this identical error also. I'm also on ubuntu (12.10) I have not had any issues until today (and am not aware of any system updates that would have caused it.). I'm stumped.
steve@...:/data/.../vivado$ vivado ****** Vivado v2013.1 (64-bit) **** Build 248050 by xbuild on Wed Mar 27 17:11:51 MDT 2013 ** Copyright 1986-1999, 2001-2013 Xilinx, Inc. All Rights Reserved. INFO: [Common 17-81] Feature available: Implementation INFO: [Common 17-81] Feature available: Synthesis INFO: [Device 21-36] Loading parts and site information from /opt/Xilinx/Vivado/2013.1/data/parts/arch.xml Parsing RTL primitives file [/opt/Xilinx/Vivado/2013.1/data/parts/xilinx/rtl/prims/rtl_prims.xml] Finished parsing RTL primitives file [/opt/Xilinx/Vivado/2013.1/data/parts/xilinx/rtl/prims/rtl_prims.xml] INFO: [Common 17-362] Using Tcl App repository from '/opt/Xilinx/Vivado/2013.1/data/XilinxTclStore'. INFO: [Common 17-364] Updating Tcl app persistent manifest '/home/steve/.Xilinx/Vivado/tclapp/manifest.tcl' start_gui Abnormal program termination (11) Please check '/data/.../vivado/hs_err_pid2904.log' for details
And the log file:
steve@...:/data/.../vivado$ cat /data/.../vivado/hs_err_pid2904.log # # An unexpected error has occurred (11) # Stack: /opt/Xilinx/Vivado/2013.1/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x744459) [0x7f0ed6e11459] /opt/Xilinx/Vivado/2013.1/tps/lnx64/jre/lib/amd64/server/libjvm.so(JVM_handle_linux_signal+0xa7) [0x7f0ed6e15cc7] /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0) [0x7f0ef9ca3cb0] /opt/Xilinx/Vivado/2013.1/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x50c5b9) [0x7f0ed6bd95b9] /opt/Xilinx/Vivado/2013.1/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x7af7b5) [0x7f0ed6e7c7b5] /opt/Xilinx/Vivado/2013.1/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x6698d3) [0x7f0ed6d368d3] /opt/Xilinx/Vivado/2013.1/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x66a1b5) [0x7f0ed6d371b5] /opt/Xilinx/Vivado/2013.1/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x66a7e2) [0x7f0ed6d377e2] /opt/Xilinx/Vivado/2013.1/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x66a920) [0x7f0ed6d37920] /opt/Xilinx/Vivado/2013.1/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x66ab36) [0x7f0ed6d37b36] /opt/Xilinx/Vivado/2013.1/tps/lnx64/jre/lib/amd64/server/libjvm.so(+0x54afb5) [0x7f0ed6c17fb5] [0x7f0ecfe8b0c8]
I'll keep searching, but any help from the community is appreciated.
07-25-2013 09:29 AM
This issue persisted after two reboots.
1. However, setting 'xhost+' in the terminal may or may not have helped, but after issuing the command, vivado is now running.
2. Also what might be of use - this first happened after I used the 'Mangae IP' option to generate IP (instead of opening a design.)
One or both the above are likely only coincedence, but may help someone.
01-20-2014 02:27 AM
I've suddenly experienced this problem too.
In my case the issue was caused by an interrupted internet connection.
vivado when started tries to connect www.xilinc.com.
It does so in the background, probably in another thread.
After several seconds, when I was already working with the gui,
this background process received a unix signal,
(probably when the socket call failed after timeout)
and caused instant abnormal termination.
It took me quite some time and luck until I recognized
what was causing the failure because there was
nowhere some reasonable error message hinting me
in the right direction.
Another issue which causes abnormal termination of
vivado, is when you are working with a "locale" which uses
the comma char instead of the decimal point to express
printed floating point numbers.
For example I'm using LANG=de_DE.UTF-8 (germany).
This can be worked around when setting the environment variable
With this issue, the abnormal termination again doesn't happen
instantly. I usually can reliably trigger it when using the schematic_viewer
in vivado, or when invoking certain IP code generators.
And again the termination at first seems random,
and gives no clue about its cause.
02-12-2014 11:26 PM
03-17-2014 06:34 PM
I'm also facing this problem. And my OS is supported by vivado.
Could you tell me how to solve it ?
OS: Red Hat Enterprise Workstation 5 64-bit
05-03-2014 07:46 AM
I'm also having the same problem. This is definitely the Vivado issue. It happens under Win 7 and Fedora on the same project set.
Vivado 2014.1 crashes everytime I open the project and here's what I get (hs_err_pidXXXX.log file):
# A fatal error has been detected by the Java Runtime Environment:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007feeb58eab5, pid=4392, tid=2280
# JRE version: Java(TM) SE Runtime Environment (7.0_40-b43) (build 1.7.0_40-b43)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.0-b56 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [librdi_common.dll+0xceab5]
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
# If you would like to submit a bug report, please visit:
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
I attach all my logs here. Any hints from developers on what is going on?