cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
jdarko
Observer
Observer
1,785 Views
Registered: ‎12-17-2018

Abnormal program termination (11) 2020.1

Jump to solution

When trying synthesis some entities for zynq ultrascale 104 we ran into this error:

Command: synth_design -part xczu7ev-ffvc1156-2-e -top zcu104_rv -mode out_of_context
Starting synth_design
Attempting to get a license for feature 'Synthesis' and/or device 'xczu7ev'
INFO: [Common 17-349] Got license for feature 'Synthesis' and/or device 'xczu7ev'
INFO: [Synth 8-7079] Multithreading enabled for synth_design using a maximum of 4 processes.
INFO: [Synth 8-7078] Launching helper process for spawning children vivado processes
INFO: [Synth 8-7075] Helper process launched with PID 3859
CRITICAL WARNING: [Synth 8-2490] overwriting previous definition of module DNA_PORT [/usr/local/src/opencpi/opencpi/projects/assets/imports/ocpi.core/exports/lib/hdl/util/zynq_ultra/DNA_PORT.v:22]
CRITICAL WARNING: [Synth 8-2490] overwriting previous definition of module FIFO2 [/usr/local/src/opencpi/opencpi/projects/assets/imports/ocpi.core/exports/lib/hdl/platform/zynq_ultra/FIFO2.v:41]
CRITICAL WARNING: [Synth 8-2490] overwriting previous definition of module FIFO1 [/usr/local/src/opencpi/opencpi/projects/assets/imports/ocpi.core/exports/lib/hdl/platform/zynq_ultra/FIFO1.v:42]
CRITICAL WARNING: [Synth 8-2490] overwriting previous definition of module SyncRegister [/usr/local/src/opencpi/opencpi/projects/assets/imports/ocpi.core/exports/lib/hdl/platform/zynq_ultra/SyncRegister.v:44]
CRITICAL WARNING: [Synth 8-2490] overwriting previous definition of module SyncHandshake [/usr/local/src/opencpi/opencpi/projects/assets/imports/ocpi.core/exports/lib/hdl/platform/zynq_ultra/SyncHandshake.v:41]
CRITICAL WARNING: [Synth 8-2490] overwriting previous definition of module SyncResetA [/usr/local/src/opencpi/opencpi/projects/assets/imports/ocpi.core/exports/lib/hdl/platform/zynq_ultra/SyncResetA.v:43]
CRITICAL WARNING: [Synth 8-2490] overwriting previous definition of module arSRLFIFOD [/usr/local/src/opencpi/opencpi/projects/assets/imports/ocpi.core/exports/lib/hdl/platform/zynq_ultra/arSRLFIFOD.v:32]
CRITICAL WARNING: [Synth 8-2490] overwriting previous definition of module MakeResetA [/usr/local/src/opencpi/opencpi/projects/assets/imports/ocpi.core/exports/lib/hdl/platform/zynq_ultra/MakeResetA.v:40]
---------------------------------------------------------------------------------
Starting Synthesize : Time (s): cpu = 00:00:03 ; elapsed = 00:00:07 . Memory (MB): peak = 2233.613 ; gain = 0.000 ; free physical = 6555 ; free virtual = 87497
---------------------------------------------------------------------------------
Abnormal program termination (11)
Please check '/usr/local/src/opencpi/opencpi/projects/assets/hdl/platforms/zcu104/target-zynq_ultra/hs_err_pid3842.log' for details
segfault in /opt/Xilinx/Vivado/2020.1/bin/unwrapped/lnx64.o/vivado -exec vivado -mode batch -source /usr/local/src/opencpi/opencpi/cdk/include/hdl/vivado-synth.tcl -nolog -journal vivado.jou -tclargs tcl_imports=zcu104_rv-imports.tcl artifact=zcu104_rv.edf hdl_mode=platform top_mod=zcu104_rv synth_part=xczu7ev-ffvc1156-2-e synth_opts=-part xczu7ev-ffvc1156-2-e -top zcu104_rv -mode out_of_context edif_opts=, exiting...
Parent process (pid 3842) has died. This helper process will now exit

Any ideas what might be wrong? The operating system we are using is centos 7. My previous post was deleted. Not sure why.

0 Kudos
1 Solution

Accepted Solutions
jdarko
Observer
Observer
1,270 Views
Registered: ‎12-17-2018

After some discussion with @apetley the crash could be happening due trying to access a library that doesn’t exist. We renamed a library that we were using a module from and forgot to rename the library in the vhd file. It seems earlier versions of Vivado, such as 2017.1 didn't, crash because it looked elsewhere (or rather everywhere) for the module we were trying to use which we happened to have a duplicate of elsewhere. So the fix was to add the appropriate namespace for the library (to something that exists).

View solution in original post

0 Kudos
13 Replies
apetley
Xilinx Employee
Xilinx Employee
1,765 Views
Registered: ‎06-14-2018

Hi @jdarko ,

Could you please provide more details such as contents of hs_err_pid3842.log.

Also is crash is reproducible, a testcase would be good to get it fixed.

Thanks,

Ajay

 

0 Kudos
jdarko
Observer
Observer
1,746 Views
Registered: ‎12-17-2018

Hi @apetley,

Attached is the log.

The entity it failed on synthesizing instantiates the zynq ultra processing system.

The crash is reproducible. We can look into seeing if we could create a testcase. 

Thanks.

 

Jerry

0 Kudos
apetley
Xilinx Employee
Xilinx Employee
1,728 Views
Registered: ‎06-14-2018

Hi @jdarko ,

Thanks for log.

A testcase will be a great help to get this fix.

Until then just to understand more, could you please let know if

  1. Design is mix language design Verilog or SV and VHDL (probably 2008)
  2. Top is VHDL module

Thanks,

Ajay

jdarko
Observer
Observer
1,712 Views
Registered: ‎12-17-2018

@apetley 

The design is mixed language; verilog and vhdl. The top module is vhdl. We have a top module zcu104.vhd that uses some of our own libraries that have both verilog and vhdl modules. The zcu104.vhd instantiates a module called zynq_ultra_ps.vhd. The zynq_ultra_ps.vhd also uses some of our own libraries and it instantiates the Xilinx zynq_ultra_ps_e processing system IP which is verilog.

I'll talk about it amongst my coworkers about how we can get the test case to you.

0 Kudos
lesjokolat
Observer
Observer
1,690 Views
Registered: ‎03-20-2020

hi 2 things.

 

try adding -stack 2000 to your startup script.

Also if this continues I have seen where 2 types of ram bricks in pc running can cause the system to suddenly crash.

jdarko
Observer
Observer
1,666 Views
Registered: ‎12-17-2018

Hi @lesjokolat ,

Whato tool command would -stack 2000 apply too? Is this a TCL option? Added to some Vivado script/file?

 

- Jerry

0 Kudos
lesjokolat
Observer
Observer
1,661 Views
Registered: ‎03-20-2020

in terminal when I start vivado

after

source settings64.sh

vivado -stack 2000

or to help javascript:

vivado -jvm Xmx12000m

 

where 2nd nunber is megabytes of ram you can assign

jdarko
Observer
Observer
1,604 Views
Registered: ‎12-17-2018

Thanks.

0 Kudos
jdarko
Observer
Observer
1,505 Views
Registered: ‎12-17-2018

@apetley 

We confirmed this failure also occurs using centos 8 as an OS.

 

@lesjokolat 

We tried the stack -2000 but it didn't work.

0 Kudos
lesjokolat
Observer
Observer
1,492 Views
Registered: ‎03-20-2020

@jdarko 

 

I also experienced this occurring when a pc was running disparate ram brick types. Is this a local machine if so check the ram in it is all same brand/type and not different speeds.

0 Kudos
jdarko
Observer
Observer
1,450 Views
Registered: ‎12-17-2018

@lesjokolat 

I was told that they are not mixing different types of ram types.

0 Kudos
jdarko
Observer
Observer
1,271 Views
Registered: ‎12-17-2018

After some discussion with @apetley the crash could be happening due trying to access a library that doesn’t exist. We renamed a library that we were using a module from and forgot to rename the library in the vhd file. It seems earlier versions of Vivado, such as 2017.1 didn't, crash because it looked elsewhere (or rather everywhere) for the module we were trying to use which we happened to have a duplicate of elsewhere. So the fix was to add the appropriate namespace for the library (to something that exists).

View solution in original post

0 Kudos
anusheel
Moderator
Moderator
1,232 Views
Registered: ‎07-21-2014

@jdarko 

As the issue is now resolved can you please mark the relevant answer as an accepted solution in the interest of other users?

Thanks
Anusheel 

0 Kudos