Activity

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]

the GHDL version was 5.0.1, but good news, the OSVVM packages compiled with NVC. And also the basic VHDL code ran and the random function is really powerful when implemented. Really appreciate the work in OSVVM!

Oh, I forgot to mention how to run it for different vendor tools…

The instantiation of the OsvvmProFileProcessor takes an optional argument of type OsvvmVariables

osvvmVariables = OsvvmVariables(
vhdlVersion = VHDLVersion.VHDL2008,
toolVendor = "Aldec"
toolName = "RivieraPRO"
toolVersion = "2024.10"
)
processor =…[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,

a few weeks ago, I release pyEDAA.OSVVM as part of the bigger EDA² Python package family. It provides a OSVVM *.pro file processor as well as data models and parsers for OSVVM’s YAML (and XML) file formats.

Repository: https://github.com/edaa-org/pyEDAA.OSVVM
Documentation: https://edaa-org.github.io/pyEDAA.OSVVM

from pathlib…[Read more]

Can you please provide the output of

ghdl –version

Hi Jim,

thanks a lot for the quick reply and, of course, for all the work you put into the OSVVM.

If I understand you correctly, I could either a) build the OSVVM libraries with the built-in scripts, and then link to those libraries in my workflow, or b) take a look at the scripts, specially VendorScripts_Siemens.tcl, and reverse-engineer 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]