Jim Lewis

If the CoverReport process is removed, then the “Stim” process can end with std.env.stop – which is typically how OSVVM ends the test cases.

— Stimulus Generator
Stim: process
variable RandA : RandomPType;
variable RandB : RandomPType;
variable allDone : boolean := false;
variable nCycles : natural := 0;
begin…[Read more]

One final thing to try. If you like the Alert/AffirmIf printing, you might also like the log printing better than the vhdl Report statement. In the “Stim” process you could change these to logs:

log("Number of simulation cycles = " & to_string(nCycles));
log("Coverage holes: " & to_string(CountCovHoles(cp_A_B)));


Logs have levels.…[Read more]

This step is recommended, but not required. Do it after you get the above running.

To get the HTML based Functional Coverage reports, you need to use the singleton rather than the older, deprecated shared variable approach.

This requires updating your architecture declarations, “InitCoverage”, “Sample”, and “CoverageReport” processes as…[Read more]

This step is recommended, but not required. Do it after you get the above running.

While I SetTestName, SetLogEnable can be called concurrently, it is more normal to call them in the process that is controlling the overall test. Currently this is the “Stim” process but we will return to this:

Stim: process
variable RandA : RandomPType;…[Read more]

Thanks for posting your whole testbench as it makes the issue clear.

You are calling EndOfTestReports concurrently. So it runs at time 0 ns. You do not want it to run until your test case has finished. Same goes for WriteAlertYaml and WriteAlertSummaryYaml. However, you do not need to call these or ReportAlerts as they are all called by…[Read more]

Hi Charlie,
What I suspect you are doing is that in the checker model you have created your requirements as follows:
Req1ID <= NewReqID("Req1", 1, ...) ;
Req2ID <= NewReqID("Req2", 1, ...) ;

When the build finishes with one or more tests that use this checker module is that the requirements are merged into the final report. However, that…[Read more]

Hi Isaac,
I think Patrick’s solution will be the defacto solution for integration with VUnit. Particularly since he is working on generating reports too – really cool.

Before I talked to Patrick today, I worked on the script I mentioned above. For each OSVVM library, it will create a list of files associated with the library. Note the…[Read more]

Hi Isaac,
From time to time, the OSVVM compile scripts are updated. It is hard to maintain more than one approach. The reason we developed the OSVVM scripts is to provide a better reporting mechanism. In addition the the ordinary JUnit reports, OSVVM does a more comprehensive Build summary. We also do test case summaries, functional…[Read more]

Hopefully I answered this in: https://osvvm.org/forums/topic/issues-with-ghdl-when-compiling-osvvm-packages

Are you running a current version of GHDL? Our github actions run with GHDL every day. See: https://github.com/OSVVM/OsvvmLibraries/actions

Did you use the directions in OsvvmLibraries/Documentation/Scripts_user_guide.pdf?

Here they are:
GHDL in Windows
~~~~~~~~~~~~~~~~

Initialize the OSVVM Script environment by doing:

winpty tclsh…[Read more]

You need XSIM if you are using Xilinx’s encrypted IP. However XSIM is very slow.

GHDL and nvc both support OSVVM well – however they need a third party waveform viewer such as SURFER.

OSVVM is updated several times each year. Even if a simulator includes an OSVVM release, it may be out of date.

OSVVM is fast to compile the project.…[Read more]

You need OSVVM 2025.02 (or newer) and XSIM 2024.2

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]

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

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]

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]