Activity

I have released these updates as part of 2025.4

Hi David,
Your pictures did not post for some reason. So I will give a more general perspective.

When a CoverageID is created, a corresponding AlertLogID is also created. If the ID, created with NewID, it is used for tracking errors – such as when an error bin is encountered. This ID is also used to determine what level an error signals…[Read more]

Thanks Jim!

Unfortunately I am unable to fetch from GitHub. I would very much appreciate a release to osvvm.org.

I did try to comment out the lines you mentioned in VendorScripts_siemens.tcl and re-ran the built in regressions. Everything worked fine. I will start the process of adopting the newest release as soon as it is posted to…[Read more]

Hi Jake,
The fixes for both of these issues are now on the OSVVM Dev branch. If you are allowed to fetch OSVVM from GitHub you can get the dev branch by doing:

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

Otherwise let me know and I can push it to main and do a release to osvvm.org.

Jim

Thanks Jim for the quick response! I really appreciate it.

As far as VHDL2019 support in Questa version 2025.1_1, I ran the regression tests using OSVVM version and get a slew of errors similar to the following when RandomPkg2019.vhd is compiled:

# ** Error: ../OsvvmLibraries/osvvm/RandomPkg2019.vhd(122): (vcom-1440) Language feature Class…

[Read more]

Hi Jake,
> I am using OSVVM version 2024.07 and the Siemens Questa version 2025.1_1 simulator.
>
> I am looking to moving to the most recent version of OSVVM as soon as possible, but sadly the aforementioned
> version of Questa doesn’t support all the VHDL2019 features that OSVVM leverages.

This mainly controls whether to use the R…[Read more]

Thanks, Jim. I have been playing with OSVVM with a couple of simulators that happen to use StartUp.tcl. I should have double checked the script user guide.

I’ll primarily be using XSIM for self-study and working through some toy examples where I want to include Xilinx’s IP. It has certainly been less of a hassle using the OSVVM AXI VC compared…[Read more]

All of the OSVVM VC have test cases for each feature. For AxiStream, they are in the directory AXI4/AxiStream/TestCases.
The set these they way you are thinking, see TbStream_AxiTiming1.vhd and TbStream_AxiTiming2.vhd. You can also use random delays, see TbStream_SendGetRandom1.vhd and TbStream_SendGetRandom2.vhd

Below is what I see running XSIM using $OsvvmLibraries/RunAllTests.pro. There are 8 failures in the RunAllTests.pro. They all have to do with passing integer and time values through the transaction record. With time it never works. With integer, it seems to work some of the time. For integer it may be possible to trace the why, for time it…[Read more]