Jim Lewis

Using a test reporter is the intended method to get this information in CI

Hi Amine,
If you are still in Tcl, there are a number of variables you can check with the build status. Currently these are not documented, but they should be. Lets start here:

* ::osvvm::ReportBuildName – Name of Build
* ::osvvm::BuildStatus – PASSED / FAILED
* ::osvvm::TestCasesPassed
* ::osvvm::TestCasesFailed
*…[Read more]

Hi Amine,
CI will be running modelsim from the bash command line. And you can use:
vsim -c -do "exit -code [catch {source $OsvvmLibraries/Scripts/StartUp.tcl ; LinkLibraryDirectory ; build RunTest.pro}]

The “exit -code” is required to get the return status. What I return error on depends on what reporter I am using.

If I am using a JUnit…[Read more]

By failed, do you mean test case failed or the build process errored out for some reason? OSVVM has are controls for both of these.

From the OSVVM Settings User Guide, you will find that they are controlled by variables:

variable FailOnBuildErrors "true" ;# simulator command had errors
variable FailOnReportErrors "false" ;#…[Read more]

Hi Veit,
Thanks for the issue reports. I have updated the names so they match. That said, since the test runner compiles and then runs the test case, the test case execution was still correct. I still hate it when the names do not match though.

You can also file issue reports like this on the VC’s issue page, such as for this…[Read more]

Hi Jon,
Thanks for sticking with this one. Knowing which version of Questa you had made told me I needed to search harder in VendorScripts_Questa.tcl. I found the issue. It is fixed on Dev.

If you do not want to update to the Dev branch, you can edit the line in VendorScripts_Questa.tcl that says:
set SimulateOptions [concat $::VsimArgs…[Read more]

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…[Read more]

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…[Read more]

Hi Senthil,
This is now fixed on the dev branch of OsvvmLibraries on GitHub. You can get the dev branch by doing:

git clone --recursive --branch dev https://github.com/osvvm/OsvvmLibraries

Best Regards,
Jim

It is Simon doing the heavy lifting.

Hi Eamon,
Simon posted the blog post that hopefully answers your question. See: https://osvvm.org/archives/2830

Best Regards,
Jim

Hi Eamon,
Simon posted the blog post that hopefully answers your question. See: https://osvvm.org/archives/2830

Best Regards,
Jim

Hi Eamon,
I have asked Simon to post a response to this. Unfortunately the website is having some issues with Simon being able to post a response to it. Hopefully it will be resolved shortly.

Many apologies. We usually get these type of things answered within a day or two of the post.

Best Regards,
Jim

Hi Senthil,
I will have this fixed shortly on the dev branch.

Best Regards,
Jim

Hi Senthil
OutputHomeDirectory is not the correct variable to be setting.
Please use OutputBaseDirectory.

I have tested it with settings as follows. In both of these the results are in the $CurrentSimulationDirectory.
variable OutputBaseDirectory “”
variable OutputBaseDirectory “osvvm”

I have not tested it with other than these…[Read more]

Hi Jon,
I recommend getting all of OsvvmLibraries. Then from the Script_user_guide.pdf, to start XSIM, do the following:

1.3.9 Xilinx XSIM
Using OSVVM in Xilinx XSIM is under development. So far, Xilinx seems to be able to
compile OSVVM utility library, however, we have not had any of our internal test cases
pass.
To run OSVVM scripts in XSIM,…

[Read more]

Hi Senthil,
Settings have been changed through time. What I say here pertains to the current release, 2025.06a. Typically I try to keep changes backward compatible.

You will find how to for OSVVM’s tcl and vhdl settings documented in OsvvmSettings_user_guide.pdf in OsvvmLibraries/Documentation. With respect to finding the settings files, it…[Read more]

Hi Senthil,
The next thing to know is that every feature in OSVVM VC is tested. That is why our test suite has so many test cases. Test cases for AxiStream are in the directory, OsvvmLibraries/AXI4/AxiStream/TestCases. A search for UU finds that test cases that test this capability:

TbStream_ByteHandling1.vhd – tests using X”UU” and X”WW” in…[Read more]