Activity

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]

Hi Jim,
Thanks a lot for taking the time to help out. Your advice fixed the issue — really appreciate your attention and effort.

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]