Activity

Thanks for the insight.

VUnit is an exisiting framework which is part of the current CI pipeline setup I use. Currently most of the testbenches use VUNIT HDL as well as the automation test runner features for CI.

As mentioned, looking to benefit from the OSVVM features especially VCs, functional coverage and reporting to enable a comprehensive…[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]

Thanks Jim, that helped. Now I have a running VUNIT testbench with the AXI4Lite VC. I would like to further extend this with the reporting features. I did browse through the scripting docu and the examples about the reporting. I am able to generate the YAML files. But the HTML reports are missing. Since I run a VUNIT testbench is there anything…[Read more]

OSVVM supports 2 processes for interrupt handling. See https://github.com/OSVVM/Documentation/blob/main/InterruptHandler_user_guide.pdf for details.

It uses 2 separate records. Control flow automatically switches to the interrupt handling process when an interrupt is pending. As described in the user guide it requires a specific interrupt…[Read more]

I use the Axi4Lite Manager as a master to access an AXI slave in the DUT. I need a solution to access the AXI slave from both the processes whcih I an currently not able to because of the multiple detect error. The AXI slave does have a memory as well as register map for configuration. And the interrupt comes from the slave indicating an arriving…[Read more]

Can you describe what you are doing.

While you can release the record there are other approaches.

For interrupt handling, OSVVM has an interrupt handler. See the common (MIT) repository in OsvvmLibraries.

You can also directly access OSVVM memories – no transaction record required

Out teaching OSVVM this week so it is harder to give…[Read more]