08-11-2020 03:09 PM
I am using Vivado 2019.1 with Modelsim 2020.3 on Windows 10.
When I select Modelsim as my simulator and run the "launch_simulation" TCL command I get an error stating certain files cannot be read. Upon opening the compile.do script (that Vivado generates) I noticed file paths that were completely incorrect (e.g. extra "../" or circular references to folders). I found a workaround by running the "export_simulation" TCL command using absolute paths. After running the provided .sh file in the newly generated modelsim folder (that Vivado created) the simulation works perfectly.
Is there a step that I am missing? Is there a way to enforce absolute paths without running the "export_simulation" TCL command?
08-11-2020 10:07 PM
Please refer to launch_simulation -help. You can specify -absolute_path option to generate absolute paths for the source files in the generated script files.
-absolute_path - (Optional) Specify this option to define the source and
include paths used in the simulation scripts as absolute paths. By default,
all paths are written as relative to the simulation run directory. Relative
paths include an "origin_dir" variable that is set in the simulation script
to the current run directory, but you can edit the $origin_dir variable to
point to a path of your choice when relocating the design and simulation
08-31-2020 10:19 AM
08-31-2020 07:00 PM
I can reproduce the issue with launch_simulation -absolute_path. I'll file a bug report to dev team.
For now, you can either edit the compile.do to correct the path to questa_lib, or rename the directory name to modelsim_lib.