Reply To: Using GLBL with OSVVM

[Jim Lewis]

If you make this call:
SetSecondSimulationTopLevel glbl

Then OSVVM would do:
vsim -c -t ps -lib common_tb TbStream_SendGetBurst1_opt glbl -suppress 8683 -suppress 8684

That said, since a library is not specified for glbl, Questa will assume it to be in common_tb. So as a result, Questa may add the common_tb.glbl in their interpretation of it.

From the README.rst or Script_user_guide.pdf,
– SetSecondSimulationTopLevel library.TestName
– Sets the name of a second library unit to use during simulation.
– Called before simulate.

I expect that Xilinx will want you to put glbl into a specific library. As a result, you need to call SetSecondSimulationTopLevel as:
SetSecondSimulationTopLevel Xilinx_Specified_Library.glbl

Note, just in case, the Xilinx_Specified_Library should never be named “work”. Naming a physical library “work” is a cruel thing some simulator vendors suggest. The name “work” in VHDL always refers to the “working library” which is the named library into which you are currently compiling (here it is: common_tb).

If you created the Xilinx_Specified_Library outside of OSVVM, you will need to link the library with:
– LinkLibrary library [path]
– Create a mapping to a library that is in the library directory specified by path.
– If path is not specified, use the library directory specified by SetLibraryDirectory.