Reply To: Using GLBL with OSVVM

[Jim Lewis]

Which version of Questa are you using?

Historically Questa offered either a vsim or a vopt/vsim flow. Up until 2025, OSVVM only supported the vsim flow, but supports both vsim and vopt/vsim flow.

The startup VendorScripts_Siemens.tcl supports the vsim flow. VendorScripts_Questa.tcl supports the vopt/vsim flow.

To choose which one you get, you need to set the OSVVM_TOOL environment variable to either Siemens or Questa. By default, if Questa is 2025.2 or newer, StartUp.tcl selects the vopt/vsim flow. Older versions of Questa select the vsim flow.

One caution is that on Windows the vopt/vsim flow creates a library that is around 10X larger – which for OSVVM regressions is 30 to 40 GB.

If you compile glbl.v using a script separate from OSVVM, Questa will not know about the library. As a result, in OSVVM, you need to tell Questa about the library by doing:

LinkLibrary xilinx_glbl C:/temp/xilinx/VHDL_LIBS/xilinx_glbl

If you are compiling glbl.v with osvvm, the library statement does this:
library xilinx_glbl

As a result of the above, Questa will put a mapping for the library in its modelsim.ini/questa.ini file. If you delete the modelsim.ini/questa.ini, then you will need to repeat the above.

When you do not do the above, you can alternately specify the library in the -L common_tb