Jim Lewis

Hi Brad,
Short answer: yes you must run either simulate or RunTest to get the coverage reports

Behind the scenes when simulate finishes it saves the code coverage data base. When a test suite finishes, the code coverage from each test case is merged together. When the build finishes, it merges together the coverage from each test suite and…[Read more]

Hi Hassan
OSVVM VC creates an AlertLogID for different classes of checkers. It is helps tracking the sources of errors – hence accelerates debug. In your own VC, you can get by with just a ModelID.

Params is another singleton data structure that holds settings for the VC. It is setup like a generalized union of values.

Best Regards,
Jim

Hi Brad,
First thing to determine is what switches you need set to vcom and vsim.

If you look at the log or html log, you can determine what OSVVM is currently doing – or you can read the OsvvmProjectScripts.tcl (older releases) or OsvvmScriptsCore.tcl (renamed in 2024.05 to support future refactoring).

You can use SetExtendedAnalyzeOptions…[Read more]

Yes. The long term plan is to add more extensive protocol violation checks it Axi4Monitor. I think a number of them are about checking that an AXI4 manager always composes a complete transaction. I am not sure the value of them if you are developing an Axi4Subordinate (formerly known as slave).

Don’t despair too much at least for Xilinx I think it will be coming. They have implemented the VHDL-2019 feature called interfaces – which is a record + mode view. A mode view specifies the IO direction of each element the record. With this, they will need to support it through all of their tools, such as Platform and Block Designer. I…[Read more]

I am not sure how Xilinx deals with this, however, for any composite port, VHDL allows you to map composites (records or arrays) element by element, below done as a formal:
`————————————————————
Manager_1 : Axi4Manager
————————————————————
port map (
–…[Read more]

AXI3 should be supported by the AXi4 VC. I looked at either AHB or APB – they could be quick to implement. The harder part is verifying the VC.

Currently high priority on my list is Avalon MM and Avalon Stream.

> Does OsvvmLibraries contain test plan that describes what specific tests exist?

I have not published one. I have it in my notebook. It would be a good idea to publish it.

> These TCL commands TestSuite, RunTest and SkipTest appear to be defined in the OsvvmProjectScripts.tcl. There are other commands like build, analyze, include for which…[Read more]

> Does OsvvmLibraries contain test plan that describes what specific tests exist?

I have not published one. I have it in my notebook. It would be a good idea to publish it.

> These TCL commands TestSuite, RunTest and SkipTest appear to be defined in the OsvvmProjectScripts.tcl. There are other commands like build, analyze, include for which…[Read more]

Getting back to your question again, if the test cases are compiled, OSVVM can do

LinkLibraryDirectory ; # Make libraries in the OSVVM library directory visible - not necessary after a build
ListLibraries ; # Lists the libraries OSVVM knows about.
vdir -lib <libraryName> ; # Questa/ModelSim & RivieraPRO/ActiveHDL
library…[Read more]

As an addendum to my last comment …
Note there are shortcuts when calling the scripts via include/build. So the following are equivalent:
build $OsvvmLibraries/OsvvmLibraries.pro
build $OsvvmLibraries/OsvvmLibraries ; # Automatically adds .pro extension
build $OsvvmLibraries ; # looks for OsvvmLibraries.pro or…[Read more]

> With VUnit I can pass a switch to the run.py and get list of tests and then run a specific test. I can choose whether to run it in in GUI mode or batch mode. How can I do that with OSVVM AXI4 tests?

> I can see that with OSVVM, each test is a different architecture of the same entity. But can OSVVM list tests like we do with VUnit and then run…[Read more]

The scripting provided as part of OSVVM is hierarchical. If we take a look at $OsvvmLibraries/OsvvmLibraries.pro, we will see:
include ./osvvm/osvvm.pro
include ./Common/Common.pro

if {[DirectoryExists UART]} {
include ./UART/UART.pro
}
if {[DirectoryExists AXI4]} {
include ./AXI4/AXI4.pro
}
if {[DirectoryExists DpRam]} {
include…[Read more]

OSVVM connects the transaction interface (a signal of a record type) directly connects the test sequencer (our examples use the name TestCtrl) to the verification component – each have ports of the same type – AddressBusRecType for MM/address bus type interfaces. All the information is passed in the record data structure – with dedicated fields…[Read more]

Yes. OSVVM calls this capability our Model Independent Transaction Library. It defines a transaction API and a transaction interface. The transaction interface is a record that is intended to be a superset of the information a transaction will need. The transaction API handles everything a transaction needs to do to send a transaction and…[Read more]

Hi Jake,
Sorry. In my last post I thought maybe there was a 2024.03 for Siemens.

I am testing on Windows. My contact at Siemens says there are issues with running OSVVM in Visualizer version 2024.01. So at least for Windows we are waiting for the next release of Visualizer. I understand that these issues are not a problem on the Linux…[Read more]

Short answer is yes. OSVVM VC (including AXI4) use items from the other OSVVM libraries, so you will need to compile those.
To build OSVVM, I recommend using the the OSVVM-Scripts. Then in VUnit you can map the OSVVM libraries.

OSVVM VC report errors against the OSVVM AlertLogPkg. You will either want to use the OSVVM AlertLogPkg in your…[Read more]

> 1. Do the OSVVM VC for these AMBA busses support all parts of the specification for these busses?
That is certainly the intent.

> 2. What is the difference between the OSVVM VC for these busses and the ones from UVVM?
I will only talk about the OSVVM VC as I don’t pay attention to the UVVM VC.

All OSVVM VC use the OSVVM Model Independent…[Read more]