Jim Lewis

Hi Jon,
Which OSVVM VC are you using?

For AXI4 Manager, it writes a U to memory in locations when WSTRB is 0. The U will not be stored in memory. For reading, there is no indication the data is valid or not. Hence, if your burst FIFO is organized as words, you will need to exclude those bits from comparing to X”020100–“. The ‘-‘ is…[Read more]

Be sure to try setting the generic defaults via the component (if used) or entity (if component not used).

In VendorScripts_Questa (if version is 2025 or newer) or VendorScripts_Siemens, the generic switch is set by the following:
# -------------------------------------------------
proc vendor_generic {Name Value} {

return "-g${Name}=${Value}"
}

According to the Questa command reference,
-g <Name>=<Value> …
(optional) Assigns a value to all s…[Read more]

Hi Jerome,
I suspect that I agree.

It seems to be in:
* xMiiMacTransmitter.vhd (as you reported)
* xMiiPhyRxTransmitter.vhd
* xMiiPhyTxReceiver.vhd

Do you concur that all of these should be updated?

They pass all my tests – but only because they all have the same issue.

I have updated these and pushed them to the dev branch of OSVVM.

Best…[Read more]

Hi Dave,
Is get_component_name a function that has an optional boolean parameter and returns type string?
It would help to see its definition, however, I will make some guesses.

I have seen this issue before when the optional parameter is type integer, but never with type boolean.
With type integer, in this context, it is correct if…[Read more]

Hi Jon,
What is the value of TValid during that time? If you do a get and TValid is true, the VC will receive data.

To avoid these sort of things, I usually hold off calling Get until the DUT is out of reset.

Best Regards,
Jim

Hi Matthias,
XSIM seems to be a moving target. In 2024.2 similar things happened. Some of what worked in 2023.2 no longer worked. I was able to change things so they worked again – and many things that did not work previously started to work.

Best Regards,
Jim

Hi Jon
Is the generic at the top level of the testbench or is it at a lower level?

Best Regards,
Jim

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