02-25-2019 08:43 AM
While getting started with using Vivado 2018.2 with ModelSim PE 10.6c I noticed that the compilation step would hang if ModelSim encountered a compiler error on the sources required for the selected Vivado simulation set. In Vivado, it's easy enough to hit "Cancel" on the Simulation launch dialog. However, it would be nice if the simulation launch would close with an error as is tested for in the generated "compile.bat". Similarly, running "exec compile.bat" in the running ModelSim window to test a change without resetting the ModelSim UI state hangs the process if the script run encounters a compile error. The simulation set's "*_compile.do" can't be used in the active ModelSim instance because it ends in "quit -force", which defeats the purpose of trying to keep it open.
Is there a way to improve the Viviado interface usability on this error case?
Can the background recompile without closing ModelSim be completed reliabily for ease of debugging?
02-28-2019 08:08 PM
UG900, Table 3-1 lists some parameters that look to address your concern.
set_param simulator.quitOnSimulationComplete 0
set_param simulator.modelsimNoQuitOnError 0
Then re-launch simulation.
However, as far as I know the param "simulator.quitOnSimulationComplete" works in Linux but not in Windows. This is under investigation and will be fixed in future release.
03-01-2019 11:37 AM