cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Adventurer
Adventurer
1,130 Views
Registered: ‎04-22-2015

Vivado TCL "An unexpected error has occurred (11)"

Hello,

Today I started Vivado with

vivado -mode tcl

And simply ran:

launch_runs impl_1 -to_step write_bitstream -jobs 2

Trying to watch the progress I did a 'tail -f runme.log'

...
Phase 2.5 Update Timing
Abnormal program termination (11)
Please check '/home/m2/share/xilinx/axi_xu5_ads131a04/axi_xu5_ads131a04/axi_xu5_ads131a04.runs/impl_1/hs_err_pid5023.log' for details

I don't think it's going to do anything else, but from the tcl console it's hard to tell that it failed:

****** Vivado v2019.1 (64-bit)
  **** SW Build 2552052 on Fri May 24 14:47:09 MDT 2019
  **** IP Build 2548770 on Fri May 24 18:01:18 MDT 2019
    ** Copyright 1986-2019 Xilinx, Inc. All Rights Reserved.

Vivado% pwd
/home/m2/share/xilinx
Vivado% 
Vivado% ls
WARNING: [Common 17-259] Unknown Tcl command 'ls' sending command to the OS shell for execution. It is recommended to use 'exec' to send the command to the OS shell.
axi_xu5_ads131a04  axi_xu5_adssim  ip_repo  testbench_ads131a04  vivado_3017.backup.jou  vivado_3017.backup.log  vivado_3266.backup.jou  vivado_3266.backup.log  vivado.jou  vivado.log
Vivado% pwd
/home/m2/share/xilinx
Vivado% exec ls
axi_xu5_ads131a04
axi_xu5_adssim
ip_repo
testbench_ads131a04
vivado_3017.backup.jou
vivado_3017.backup.log
vivado_3266.backup.jou
vivado_3266.backup.log
vivado.jou
vivado.log
Vivado% cd ax
axi_xu5_ads131a04/ axi_xu5_adssim/ 
Vivado% cd axi_xu5_ads131a04/
Vivado% exec ls
axi_xu5_ads131a04
axi_xu5_ads131a04_svn
axi_xu5_ads131a04.tcl
readme
Vivado% cd ax
axi_xu5_ads131a04/ axi_xu5_ads131a04.tcl axi_xu5_ads131a04_svn/ 
Vivado% cd axi_xu5_ads131a04
Vivado% ls
WARNING: [Common 17-259] Unknown Tcl command 'ls' sending command to the OS shell for execution. It is recommended to use 'exec' to send the command to the OS shell.
axi_xu5_ads131a04.cache  axi_xu5_ads131a04.hw  axi_xu5_ads131a04.ip_user_files  axi_xu5_ads131a04.runs  axi_xu5_ads131a04.sim  axi_xu5_ads131a04.xpr
Vivado% open_project axi_xu5_ads131a04.xpr
Scanning sources...
Finished scanning sources
INFO: [IP_Flow 19-234] Refreshing IP repositories
INFO: [IP_Flow 19-1700] Loaded user IP repository '/home/m2/share/xilinx/ip_repo'.
INFO: [IP_Flow 19-2313] Loaded Vivado IP repository '/home/m2/share/vivado/Vivado/2019.1/data/ip'.
open_project: Time (s): cpu = 00:00:05 ; elapsed = 00:00:08 . Memory (MB): peak = 1392.859 ; gain = 2.016 ; free physical = 3442 ; free virtual = 22953
axi_xu5_ads131a04
Vivado% launch_runs impl_1 -to_step write_bitstream -jobs 2
[Fri Sep 20 15:54:19 2019] Launched synth_1...
Run output will be captured here: /home/m2/share/xilinx/axi_xu5_ads131a04/axi_xu5_ads131a04/axi_xu5_ads131a04.runs/synth_1/runme.log
[Fri Sep 20 15:54:19 2019] Launched impl_1...
Run output will be captured here: /home/m2/share/xilinx/axi_xu5_ads131a04/axi_xu5_ads131a04/axi_xu5_ads131a04.runs/impl_1/runme.log
launch_runs: Time (s): cpu = 00:00:06 ; elapsed = 00:00:06 . Memory (MB): peak = 1409.109 ; gain = 16.250 ; free physical = 3404 ; free virtual = 22939
Vivado% 
Vivado% get_property PROGRESS [get_runs impl_1]
0%
Vivado% get_property PROGRESS [get_runs impl_1]
0%
Vivado% STATUS [get_runs impl_1]
invalid command name "STATUS"
Vivado% get_property PROGRESS [get_runs impl_1]
50%
Vivado% get_property PROGRESS [get_runs impl_1]
50%
Vivado% get_property PROGRESS [get_runs impl_1]
50%
Vivado% get_property PROGRESS [get_runs impl_1]
50%
Vivado% get_property PROGRESS [get_runs impl_1]
50%
Vivado% get_property PROGRESS [get_runs impl_1]
75%
Vivado% get_property PROGRESS [get_runs impl_1]
75%
Vivado% get_property PROGRESS [get_runs impl_1]
75%
Vivado% get_property PROGRESS [get_runs impl_1]
75%
Vivado% get_property PROGRESS [get_runs impl_1]
75%
Vivado% get_property PROGRESS [get_runs impl_1]
75%
Vivado% get_property PROGRESS [get_runs impl_1]
75%
Vivado% get_property PROGRESS [get_runs impl_1]
75%
Vivado% get_property PROGRESS [get_runs impl_1]
75%
Vivado% 
Vivado% get_property PROGRESS [get_runs impl_1]
75%
Vivado% get_property PROGRESS [get_runs impl_1]
75%
Vivado% get_property PROGRESS [get_runs impl_1]
75%
Vivado% 

This is on a Ubuntu 18.04.2 system.

-Paul

0 Kudos
3 Replies
Highlighted
Adventurer
Adventurer
1,119 Views
Registered: ‎04-22-2015

OK, ran again cleaning everything out and going all the way back to creating the project

Vivado% source axi_xu5_ads131a04.tcl

And everything built OK.

I did have the project open in the GUI before running from the command line, and had even canceled the generate bitstream (I was just looking for the tcl command). That may have something to do with it. In any case it doesn't seem like the behavior that is wanted.

-Paul

0 Kudos
Highlighted
Moderator
Moderator
1,052 Views
Registered: ‎03-16-2017

Hi @pthomas ,

This is a crash message. 

So, are you facing it again now? or it is resolved by cleaning everything?

Regards,
hemangd

Don't forget to give kudos and mark it as accepted solution if your issue gets resolved.
0 Kudos
Highlighted
Advisor
Advisor
855 Views
Registered: ‎02-12-2013

Hello, I get this same message and similar log dump during simulation restarts.  I am using the latest 2019.2 Vitus release on Ubuntu 18.04.1 LTS.

It feels like a memory leak somewhere in the Vivado code stack as it turns up for a lot of people in implementation too. I can usually get about a dozen simulator restarts before the whole Vivado GUI crashes.

I assume you guys run all kinds of code analysis tools so good luck finding the cause of this.

----------------------------------------
DSP in hardware and software
-----------------------------------------
0 Kudos