cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
jensrenner
Contributor
Contributor
5,293 Views
Registered: ‎02-20-2014

Vivado 2017.1 - Abnormal program termination

Hello!

I installed Vivado 2017.1 on a 64-bit Debian GNU/Linux machine.

Vivado v2017.1 (64-bit)
SW Build 1846317 on Fri Apr 14 18:54:47 MDT 2017
IP Build 1846188 on Fri Apr 14 20:52:08 MDT 2017
jrenner@serena:~$ uname -a
Linux serena 4.10.10-towo.1-siduction-amd64 #1 SMP PREEMPT siduction 4.10-18 (2017-04-12) x86_64 GNU/Linux

During implementation at "Phase 9 Resynthesis", I am getting abnormal program terminations:

Phase 9 Resynthesis
Abnormal program termination (11)
Please check '/work/zynq/csa_zynq_full/csa_zynq_full.runs/impl_1/hs_err_pid25433.log' for details

These are the contents of the log file:

#
# An unexpected error has occurred (11)
#
Stack:
/lib/x86_64-linux-gnu/libc.so.6(+0x33030) [0x7f3f7074e030]
/lib/x86_64-linux-gnu/libc.so.6(strlen+0x26) [0x7f3f7079b496]
/lib/x86_64-linux-gnu/libc.so.6(+0x354c9) [0x7f3f707504c9]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_common.so(HUTEnv::setEnv(char const*, char const*)+0xe) [0$
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_place.so(HAOPAbcJobManager::HAOPAbcJobManager()+0x1390) [0$
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_place.so(HAOPAbcOpt::HAOPAbcOpt(std::__cxx11::basic_string$
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_place.so(HAOPFlow::resynthesis(std::__cxx11::basic_string<$
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_place.so(HAOPFlow::doabc(HDPLTask&, std::__cxx11::basic_st$
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_place.so(HAOPFlow::optDesignMod()+0x83f) [0x7f3f49509aaf]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_place.so(HAOPFlow::optimize()+0xf8) [0x7f3f49509f48]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_vivadotasks.so(+0x2fc399) [0x7f3f38bb7399]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_vivadotasks.so(+0x2ff0f6) [0x7f3f38bba0f6]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_common.so(+0x6d0e00) [0x7f3f71933e00]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(+0x334af) [0x7f3f6c3ae4af]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(+0x76875) [0x7f3f6c3f1875]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(+0x7e029) [0x7f3f6c3f9029]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(TclEvalObjEx+0x76) [0x7f3f6c3b0156]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_commontasks.so(+0x1a5d74) [0x7f3f67350d74]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(+0x334af) [0x7f3f6c3ae4af]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(+0x34b38) [0x7f3f6c3afb38]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(+0xad486) [0x7f3f6c428486]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(+0x346c5) [0x7f3f6c3af6c5]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(Tcl_EvalEx+0x13) [0x7f3f6c3b00a3]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(Tcl_FSEvalFileEx+0x1da) [0x7f3f6c414c5a]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_commontasks.so(+0x1c360d) [0x7f3f6736e60d]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_common.so(+0x6d0e00) [0x7f3f71933e00]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(+0x334af) [0x7f3f6c3ae4af]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(Tcl_EvalObjv+0x32) [0x7f3f6c3ae5e2]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(TclEvalObjEx+0x322) [0x7f3f6c3b0402]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_commontasks.so(+0x1e661f) [0x7f3f6739161f]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_commontasks.so(+0x1e7e0e) [0x7f3f67392e0e]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_common.so(+0x6d0e00) [0x7f3f71933e00]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(+0x334af) [0x7f3f6c3ae4af]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(Tcl_EvalObjv+0x32) [0x7f3f6c3ae5e2]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(TclEvalObjEx+0x322) [0x7f3f6c3b0402]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_commonmain.so(+0x73a4) [0x7f3f7105a3a4]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/libtcl8.5.so(Tcl_Main+0x1d0) [0x7f3f6c41b210]
/opt/Xilinx/Vivado/2017.1/lib/lnx64.o/librdi_common.so(+0x71663b) [0x7f3f7197963b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7494) [0x7f3f70502494]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f3f7080393f]

Is there anything I can do (except waiting for the next release)?

 

Kind regards

 

Jens.

0 Kudos
5 Replies
austin
Scholar
Scholar
5,287 Views
Registered: ‎02-27-2008

j,

 

You may contact your local Xilinx authorized distributor sales office for assistance.  And, perhaps someone will also reply here,

Austin Lesea
Principal Engineer
Xilinx San Jose
0 Kudos
vijayak
Xilinx Employee
Xilinx Employee
5,221 Views
Registered: ‎10-24-2013

hi @jensrenner

Is it possible to post the project archive here? Once the issue is reproduced at our end, we can take factory help to debug the issue further.

Thanks,Vijay
--------------------------------------------------------------------------------------------
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
bato990
Observer
Observer
5,030 Views
Registered: ‎10-09-2014

I have the same problems with vivado 2016.3 and vivado 2016.4 and vivado 2017.1.

In all situations Vivado termination or hang or exception occurs without any report or description

I will explain some type.

 

1- Incorrect coding.

In a vhdl file with I write a code that i have an assignment of 3 bus width string to 7 bus width string array.

example:

generic (
ChState0 : in string (1 to 7) := "I_ORI0 ";
ChState1 : in string (1 to 7) := "ID ";
ChState2 : in string (1 to 7) := "Q_ORQ0 ";
ChState3 : in string (1 to 7) := "QD ";
ChState4 : in string (1 to 7) := "I_ORI1 ";
ChState5 : in string (1 to 7) := "ID ";
ChState6 : in string (1 to 7) := "Q_ORQ1 ";
ChState7 : in string (1 to 7) := "QD ";

....


type string_array3 is array(natural range <>) of string (1 to 3);
constant ChState : string_array3 ( 7 downto 0) := (ChState7,ChState6,ChState5,ChState4,ChState3,ChState2, ChState1, ChState0);


Running this code with Vivado 2016.3, 2016.4 and 2017.1 result (windows 10):

Abnormal program termination (EXCEPTION_ACCESS_VIOLATION)
Please check 'D:/.../synth_1/hs_err_pid10176.log' for details

by fixing the code as below problem was solved.

example:

generic (
ChState0 : in string (1 to 7) := "I_ORI0 ";
ChState1 : in string (1 to 7) := "ID ";
ChState2 : in string (1 to 7) := "Q_ORQ0 ";
ChState3 : in string (1 to 7) := "QD ";
ChState4 : in string (1 to 7) := "I_ORI1 ";
ChState5 : in string (1 to 7) := "ID ";
ChState6 : in string (1 to 7) := "Q_ORQ1 ";
ChState7 : in string (1 to 7) := "QD ";

....


type string_array7 is array(natural range <>) of string (1 to 7);
constant ChState : string_array7 ( 7 downto 0) := (ChState7,ChState6,ChState5,ChState4,ChState3,ChState2, ChState1, ChState0);


2- Tools problem
I have same problem with a project in the Vivado 2016.3 (windows 10) at routing step.
I disabled Run report ultrafast methodology as below.
Tools menu/Project settings../Implementation/ disable "Run report ultrafast methodology after routing".

Problem was solved.

 

3- Tools Problem.
I have same problem with a project in the Vivado 2016.4 (windows 10).

I changed project Implementation strategy to "Flow_RuntimeOptimized".
The problem was fixed!!!!!
It not desired solution.

 

 

0 Kudos
evgenis1
Advisor
Advisor
4,545 Views
Registered: ‎12-03-2007

I had the same error while upgrading 2016.4 Vivado design to 2017.1. It was during synthesis of one of the standard IP cores. None of the above suggestions helped, so I opened service request.

 

Thanks,

Evgeni

Tags (1)
0 Kudos
lucabora22
Visitor
Visitor
4,449 Views
Registered: ‎03-19-2015

Hi everyone,

i got the same problem after migrating from Vivado 2015.4 (where everything was fine) to Vivado 2017.1.

In particular at the opt_design phase during the implementation of a XTMR design.

For other projects I was able to carry out the implementation. 

I tried the solution posted here but didn't work for me. How can i fix it?

I attach the .log and .dmp files generated.

Thanks

Luca

0 Kudos