Activity

Hey Lars,

I must have missed this when initially going through the github docs but this configuration based implementation is what I was looking for so very much appreciated!

I have pushed an update to the documentation on GitHub to clarify this issue. If you navigate from OsvvmLibraries navigate from the dev branch. If you navigate directory to Documenation repository – it is the most recent push.

A direct link to it is here: https://github.com/OSVVM/Documentation/blob/main/Axi4_VC_user_guide.pdf

Hi Alpha,
The Axi4Memory supports the full capability of the AXI4 bus from the DUT side interface – including a multi-beat burst. This allows the DUT to interact with any addressable location in the memory. Be careful to keep your address space reasonable as the Axi4Memory creates a data structure and sizes above 2**40 are not currently…[Read more]

Hi Brad,

VUnit has support for running OSVVM style of testbenches. You’ll find the information here: http://vunit.github.io/blog/2023_08_26_vhdl_configurations.html. I also recommend looking into open-source
GHDL and NVC. Once you’ve started multi-threaded simulations, there is no going back and you will most likely want
to use all your processing cores.

Interesting, I admit that while I’ve gotten familiar with a lot of what OSVVM offers, test suites are something I usually set for each DUT and just include all tests within that single suite.

I will look into doing this today to do some hands on testing but am I reading this right in that this multiple test suite configuration would allow for…[Read more]

Hi Brad,
Currently if you run things from VUnit, you loose all the OSVVM reporting. This is a direction we are currently investigating, but will either need to uplevel our tcl expertise or outside help.

How many different simulation sets do you intend to run? What I do normally is group my tests into test suites that test individual…[Read more]