Activity

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]

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]

The problem is, with Ubuntu 24.04, I think we can install the latest GHDL with snap store, but I have pop!_os 22.04 which is like Ubuntu 22.04. Here I have to install GHDL from github. I installed 5.0.1 GHDL. But I have all sorts of problems (with dependencies as I am doing it manually) where I couldn’t initialise and create the first work object…[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]

Hi. I think you might have an old GHDL version.

`
$ rlwrap -c tclsh
$ source ../OsvvmLibraries/Scripts/StartUp.tcl
OSVVM Script Version: 2025.02
Simulator Version: GHDL-5.0.0-dev
`

Hi, I see that you have some successful simulations with GHDL. may I ask which version of GHDL is compatible with OSVVM 2025.2? I am having the build error when I used GHDL 3.0.0 version. the normal libraries are being built with “rlwrap tclsh”, but when i want to build my adder_tb, it is not being build, and has errors. what am I doing wrong? I…[Read more]

You need OSVVM 2025.02 (or newer) and XSIM 2024.2

I have migrated to 2025.4, and things are working well for me so far. Thanks Jim!

-Jake