Jim Lewis

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]

From the Scripts_user_guide.pdf:
To run OSVVM scripts in XSIM, start Vivado and then run the StartXSIM using:
source <path-to-OsvvmLibraries>/OsvvmLibraries/Scripts/StartXSIM.tcl

This will then set the simulator to XSIM and instead of analyzing MemoryGenericPkg.vhd, it will do:
analyze deprecated/MemoryGenericPkg_xilinx.vhd

All of the…[Read more]

These above write bin values were not generated by the code you posted. See annotations in the code.

Hi ALex,
I added the two suggestions I made previously to the code. Choose one of them.
I also changed the WaitForClock(clk, 2) to WaitForClock(InterruptRec, 2).
Usually I do not put clock in TestCtrl. The reason being is if you have lots of
different clocks in your system, it is easy to use the wrong one.

`
rx_process : process is…[Read more]

Hi Alex,
I see a delta cycle issue. Call ICover using Cnt rather than rx_cnt_s.
Or alternately do a wait for 0 ns ; before the call to ICover.

Best Reegards,
Jim

Hi Alex,
Please use a separate topic for separate issues.

I don’t see anything obvious in your code. Have you tried single step?

Jim

I have not seen Siemens HDL Designer Pro flow, so I cannot comment on how to use it. Like most things there may be a way.

Avalon MM is progressing slowly.

Hi Mickie
What version of Questa are you using?

With 2024.2 I turned on VHDL-2019. The features work fine, but in 2025.1 Questa decided to throw warnings for this feature.

If it is not 2025.1, then it is probably too old like 10.4 or 10.5.

I have been running regressions with 2024.3_1.

Best Regards
Jim

> Is there a possibilty to use any of the Modelsim/Questa simulator features for the OSVVM functional coverage reporting?

Not at this time. We looked at exporting an XML to UCIS, but they do not support the UCIS standard in this area. There is a C interface, but UCIS is based on crossing existing item/point coverage models using to create a…[Read more]

Hi Alex,
What is your motivating factor to use VUnit? Is there some capability there that you would like to see in OSVVM? Are you just using VUnit as a test runner or are you also using some of the VHDL code that is part of VUnit?

Currently OSVVM HTML reports are collaboration of OSVVM scripting and OSVVM VHDL code. The Test Case reports are…[Read more]

Hi Ajeetha,
I had started a reply right away and thought I had finished, but apparently forgot to submit it.

TCover in OSVVM is does transition coverage. You will need to name your something different.

It is ok to use the existing data structure for TCover to record the last value. I think your check is off a little as yours currently will…[Read more]