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: 
Highlighted
911 Views
Registered: ‎08-20-2018

SDK 2014.4 crashes

Hi all!

 

I am following this tutorial in order to set-up my new ZedBoard with Ubuntu 16.04 and Vivado 14.4. When I create a new application based in Hello World, I select Run As -> Launch on Hardware (GDB). After a few seconds, SDK crashes without print 'Hello World' in the terminal console.

 

I get this message:

 

(Xilinx SDK:1757): IBUS-WARNING **: The owner of /home/cristina/.config/ibus/bus is not root!
Experimental:  JNI_OnLoad called.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007ff1a546a24d, pid=1757, tid=140675835631360
#
# JRE version: Java(TM) SE Runtime Environment (8.0_05-b13) (build 1.8.0_05-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.5-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [librxtxSerial.so+0x724d]  read_byte_array+0x3d
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/cristina/hs_err_pid1757.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.
#

 

Before launching the program I deleted .config/ibus.

 

Log error file:

 

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007ff1a546a24d, pid=1757, tid=140675835631360
#
# JRE version: Java(TM) SE Runtime Environment (8.0_05-b13) (build 1.8.0_05-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.5-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [librxtxSerial.so+0x724d]  read_byte_array+0x3d
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# 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.
#

 

Any help would be appreciated!

 

Thx!

0 Kudos
4 Replies
Moderator
Moderator
886 Views
Registered: ‎10-06-2016

Re: SDK 2014.4 crashes

Hi @cluna.aistechspace,

 

No sure what is going wrong but seems that might be related to the Terminal feature within the SDK. Did you try to debug the application without using the integrated terminal? (use TeraTerm, Kitty or so for checking the serial output).

 

BTW, is there any particular reason of using such an old tool? Xilinx is already in 2018.2 release and there have been quite a lot of improvements in the way.

 

Regards

Ibai


Ibai
Don’t forget to reply, kudo, and accept as solution.
0 Kudos
876 Views
Registered: ‎08-20-2018

Re: SDK 2014.4 crashes

I'm following the ZedBoard tutorial. I'm using this version of Xilinx because it's the one licensed with the ZedBoard.

I'm new using that board and I'm doing what I can. SDK 14.4 crashes many times for different reasons and I'm going nuts :(

0 Kudos
868 Views
Registered: ‎08-20-2018

Re: SDK 2014.4 crashes

Using CuteCom instead SDK's terminal works! But I'm still thinking that SDK's terminal should work too

0 Kudos
Moderator
Moderator
864 Views
Registered: ‎10-06-2016

Re: SDK 2014.4 crashes

Hi @cluna.aistechspace

 

So that confirms that the issue is in the Terminal feature of the Eclipse environemnt. There is no any known issue in 2014.4 release notes that points to this feature be broken but might be related somehow to your host machine as well. As pointed previously this SDK release so I would either recommend to use external terminal or update the SDK.

 

Regards

Ibai


Ibai
Don’t forget to reply, kudo, and accept as solution.
0 Kudos