Activity

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]

OK, so here is how I am able to run specific test.

First I goto a suitable location where QuestaSim can save its generated files. In this case I did

cd {E:My_DesignsFPGAOsvvmLibraries}

Then I ran the following commands:

source ./Scripts/StartUp.tcl
include ./osvvm/osvvm.pro
include ./Common/Common.pro
include ./AXI4/AXI4.pro

library…[Read more]

First lets look at RunDemoTests.pro

TestSuite Axi4Full
library osvvm_TbAxi4

if {$::osvvm::ToolNameVersion ne “XSIM-2023.2”} {
include ./testbench

# Make TestCases the frame of reference
set ::osvvm::CurrentWorkingDirectory [file join $::osvvm::CurrentWorkingDirectory TestCases]
RunTest TbAxi4_DemoMemoryReadWrite1.vhd
RunTest…[Read more]

Jim I agree with you that once a test passes, it will never ever be run interactively and only in regression. I agree that the only time a test is run interactively is when a test is being developed or it fails and a closer look at waves is required.

The simple answer to the question is that to know what tests exist, we look at the test plan or…[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]

Thanks Jim. I know you are busy but still taking time out to write here.

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…[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]

VUnit has concept of “actor”

constant my_receiver : actor_t := new_actor(“my receiver”);

This is used in message passing. So the “transaction interface” I guess contains the information that we are interested to pass e.g for MM write it would be address and data and transfer type (single vs burst) and maybe something about delay in clock cycles…[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]