put these files in the same directory with the following batch file (if you are using linux you'll have to translate to a bash or whatever script)
tb_ringOscillator.vhd
tb_ringOscillator_time_impl.sdf
tb_ringOscillator_time_impl.v
Code:
set xv_path=F:\\Xilinx\\Vivado\\2016.2\\bin
call %xv_path%/xvlog -m64 --relax tb_ringOscillator_time_impl.v
call %xv_path%/xvhdl -m64 tb_ringOscillator.vhd
call %xv_path%/xelab -m64 --debug typical --relax --mt 2 --maxdelay -timescale 1ps/1ps -L xil_defaultlib -L simprims_ver -L secureip --snapshot tb_ringOscillator_time_impl -transport_int_delays -pulse_r 15 -pulse_int_r 10 -pulse_e 15 -pulse_int_e 10 tb_ringOscillator glbl
call %xv_path%/xsim -gui tb_ringOscillator_time_impl
This will run perfectly fine, the Vivado tools don't seem to know how to setup a proper timing simulation. After every one of the -pulse_xxx stuff their xelab command had a ps after it. that is why the simulation would not run as it was looking for a module named ps.
IMO it's always better to write your own script, I only use the GUI once to generate the prj files (tell the simulation to only generate scripts) that contain all the files to compile to run the sim. Once I have that I never open the GUI project to run sims.
View attachment 139128
- - - Updated - - -
Lucky for you I was waiting for a long compile to finish