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!

Showing results for 
Search instead for 
Did you mean: 
Observer mikejohnson
Registered: ‎11-11-2008

Stand alone xsim relaunch from scripts

I've been attempting to replace my script driven Modelsim environment with xsim.

Calling xvlog / xvhdl with generated project files works well while editing code.

The scripts will also call xelab and xsim to bring up the GUI (which is remarkably slow to invoke).


One the simulator has run, a code change might be required.


The scripts can call xvlog/xvhdl again, but unlike Modelsim a restart will not pick up the changes.

Ahha, so I need to call xelab as well. :

Simulator compilation completed in 6.98 seconds.
VHDL files 62, Verilog files 4.
Invoking: xelab a_loader_tb -timescale 1ns/1ps -debug typical -s a_loader_tb
Vivado Simulator 2019.2
Copyright 1986-1999, 2001-2019 Xilinx, Inc. All Rights Reserved.
Running: C:/Xilinx/Vivado/2019.2/bin/unwrapped/win64.o/xelab.exe a_loader_tb -timescale 1ns/1p
Multi-threading is on. Using 2 slave threads.
Starting static elaboration
Completed static elaboration
Starting simulation data flow analysis
Completed simulation data flow analysis
ERROR: [XSIM 43-3356] Could not open file xsim.dir/a_loader_tb/xsim.type for writing.
ERROR: [XSIM 43-3915] Encountered a fatal error. Cannot continue. Exiting...


So while the GUI is running, it's locked the database even though the simulation has stopped.

Do you have any suggests to inprove the turnaround time while debugging ?

Otherwise I need to save the waveform config. Close the simulator and rerun the whole process.

This is extrememly painful compared to any 3rd party simulator.





0 Kudos