cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
rtfinch
Adventurer
Adventurer
2,705 Views
Registered: ‎01-06-2016

Vivado exits abruptly

Jump to solution

I'm assuming this is an installation issue of some sort. On Windows 10 64 bit. Vivado 17.4 exits abruptly just after loading the project with no error messages. Vivado was just installed this is on a new workstation. Vivado was installed into the d: drive.

I tried checking the windows event viewer for message and there were none.

The IDE screen appears for about a half second then the app exits.

 

How can I tell what is going on ?

 

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
rtfinch
Adventurer
Adventurer
3,231 Views
Registered: ‎01-06-2016

I tried starting it again and it seems to be working now. I ran a synthesis. The only thing I did differently was to click on the TCL console tab on the splash screen in order to watch the start-up.

Thank-you for your assistance.

 

View solution in original post

0 Kudos
6 Replies
2,673 Views
Registered: ‎01-22-2015

Please see <this post> for possible explanation and solution.

 

Mark

0 Kudos
howardp
Xilinx Employee
Xilinx Employee
2,669 Views
Registered: ‎07-22-2008

Most likely, the install itself completed successfully or you would have received an error message.

There is usually a system or compatibility issue that causes crashes when the install completed fine otherwise.

 

The Dump file shows the following.

Unable to load image D:\Xilinx\Vivado\2017.4\lib\win64.o\librdi_filemgmt.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for librdi_filemgmt.dll
*** ERROR: Module load completed but symbols could not be loaded for librdi_filemgmt.dll

 

Do you happen to have a patch for AR68506 (or any other patch) pointed to with the MYVIVADO variable?  The reason I mention this patch is because it has the DLL listed in the DMP file and it was created for Vivado 2016.4.  It should work well for 2016.4 but would cause a crash for any other version of Vivado.  If you do, either unset the MYVIVADO variable when using versions other than 2016.4 or install the patch under the patches directory in the 2016.4 install directory.

0 Kudos
rtfinch
Adventurer
Adventurer
2,662 Views
Registered: ‎01-06-2016

Yes, there were no error or warning messages during install. It looks like it installed correctly.

This install was to a relatively fresh machine (new pc) but I did copy over some of the documents and data directories.

There are no other versions of Vivado on the machine.

This is no environment variable MYVIVADO set (I tried an echo from the command prompt).

 

With regards to the other AR. In this case Vivado gets past the splash screen and into the IDE. I can see the little circle begin spinning in the project files window, then it just exits.

 

0 Kudos
rtfinch
Adventurer
Adventurer
3,232 Views
Registered: ‎01-06-2016

I tried starting it again and it seems to be working now. I ran a synthesis. The only thing I did differently was to click on the TCL console tab on the splash screen in order to watch the start-up.

Thank-you for your assistance.

 

View solution in original post

0 Kudos
rtfinch
Adventurer
Adventurer
2,562 Views
Registered: ‎01-06-2016

I've not tried Vivado for a couple of weeks and now there's the same problem. But this time clicking on the TCL console tab didn't work.

 

From the .dmp file:

The thread tried to read from or write to a virtual address for which it does not have the appropriate access.

 

 

0 Kudos
rtfinch
Adventurer
Adventurer
2,503 Views
Registered: ‎01-06-2016

I tried downloading and installing Vivado 18.1 and the same thing occurs.

 

"The thread tried to read from or write to a virtual address for which it does not have the appropriate access."

 

The .str file contains

/*

Xilinx Vivado v2018.1 (64-bit) [Major: 2018, Minor: 1]
SW Build: 2188600 on Wed Apr  4 18:40:38 MDT 2018
IP Build: 2185939 on Wed Apr  4 20:55:05 MDT 2018

Process ID: 7232
License: Customer

Current time:  Sun Apr 15 19:18:01 EDT 2018
Time zone:  Eastern Standard Time (America/New_York)

OS: Windows 10
OS Version: 10.0
OS Architecture: amd64
Available processors (cores): 8

Screen size: 1344x840
Screen resolution (DPI): 96
Available screens: 1
Available disk space: 52 GB
Default font: family=Dialog,name=Dialog,style=plain,size=12

Java version:  1.8.0_112 64-bit
Java home:  D:/Xilinx/Vivado/2018.1/tps/win64/jre
Java executable location:  D:/Xilinx/Vivado/2018.1/tps/win64/jre/bin/java.exe
Java initial memory (-Xms):  128 MB
Java maximum memory (-Xmx):  2 GB


User name:  Robert
User home directory: C:/Users/Robert
User working directory: C:/Users/Robert/AppData/Roaming/Xilinx/Vivado
User country:  CA
User language:  en
User locale:  en_CA

RDI_BASEROOT: D:/Xilinx/Vivado
HDI_APPROOT: D:/Xilinx/Vivado/2018.1
RDI_DATADIR: D:/Xilinx/Vivado/2018.1/data
RDI_BINDIR: D:/Xilinx/Vivado/2018.1/bin

Vivado preferences file location: C:/Users/Robert/AppData/Roaming/Xilinx/Vivado/2018.1/vivado.xml
Vivado preferences directory: C:/Users/Robert/AppData/Roaming/Xilinx/Vivado/2018.1/
Vivado layouts directory: C:/Users/Robert/AppData/Roaming/Xilinx/Vivado/2018.1/layouts
PlanAhead jar file location:  D:/Xilinx/Vivado/2018.1/lib/classes/planAhead.jar
Vivado log file location:  C:/Users/Robert/AppData/Roaming/Xilinx/Vivado/vivado.log
Vivado journal file location:  C:/Users/Robert/AppData/Roaming/Xilinx/Vivado/vivado.jou
Engine tmp dir:  C:/Users/Robert/AppData/Roaming/Xilinx/Vivado/.Xil/Vivado-7232-Ateana5

GUI allocated memory: 140 MB
GUI max memory:  3,052 MB
Engine allocated memory: 524 MB

Copyright 1986-2018 Xilinx, Inc. All Rights Reserved.

*/

// TclEventType: START_GUI
// Tcl Message: start_gui
// [GUI Memory]: 42 MB (+41251kb) [00:00:05]
// [Engine Memory]: 508 MB (+381340kb) [00:00:05]
selectList(PAResourceQtoS.SyntheticaGettingStartedView_RECENT_PROJECTS, "D:/Cores4/FT833/FT833/FT833.xpr", 0); // q (O, ch)
// bv (ch):  Open Project : addNotify
// Opening Vivado Project: D:/Cores4/FT833/FT833/FT833.xpr. Version: Vivado v2018.1
// TclEventType: DEBUG_PROBE_SET_CHANGE
// TclEventType: MSGMGR_MOVEMSG
// TclEventType: FILE_SET_NEW
// TclEventType: RUN_CURRENT
// TclEventType: PROJECT_NEW
// Tcl Message: open_project D:/Cores4/FT833/FT833/FT833.xpr
// Tcl Message: Scanning sources... Finished scanning sources
// Tcl Message: INFO: [IP_Flow 19-234] Refreshing IP repositories INFO: [IP_Flow 19-1704] No user IP repositories specified
// Tcl Message: INFO: [IP_Flow 19-2313] Loaded Vivado IP repository 'D:/Xilinx/Vivado/2018.1/data/ip'.
// TclEventType: PROJECT_NEW
// [GUI Memory]: 50 MB (+6866kb) [00:00:08]
// [Engine Memory]: 615 MB (+85460kb) [00:00:08]
// [GUI Memory]: 65 MB (+12617kb) [00:00:08]
// [GUI Memory]: 69 MB (+799kb) [00:00:09]
// HMemoryUtils.trashcanNow. Engine heap size: 620 MB. GUI used memory: 36 MB. Current time: 4/15/18 7:18:04 PM EDT

0 Kudos