Activity

The Axi4Manager has a TransactionDispatcher, which receives transactions from the Test Sequencer (TestCtrl) and dispatches these out to interface handlers (such as WriteAddressHandler). The interface handlers connect to the DUT and represent independently running pieces of the VC. The communication between the TransactionDispatcher and…[Read more]

I understand that all of these are basically FIFOs. The term “scoreboard” need not confuse oneself.

The AXI4Manager source code contains these lines in the architecture declaration part:

signal WriteAddressFifo : osvvm.ScoreboardPkg_slv.ScoreboardIDType ;
signal WriteDataFifo : osvvm.ScoreboardPkg_slv.ScoreboardIDType ;

signal ReadAddressFifo : osvvm.ScoreboardPkg_slv.ScoreboardIDType ;
signal…[Read more]

It seems that so many IDs are needed to create a hierarchical output for difference aspects of the BFM in the test result report.

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]

Hey, I appreciate the insight and I actually worked my way to this action after noticing that the simulate command called vsim. I guess one more question to make sure I’m understanding these scripts correctly.

Currently, I know the following script will allow my to run my test and see the results:

SetCoverageSimulateEnable true

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

What is the primary benefit of this thread since the synthesis tool vendors will take maybe a decador or more to add simple new features for the language.

We need an effort to upgrade the flow that is used with VHDL. We need something like LLVM for VHDL. The netlist fitter can be handled by the tools. But tool for synthesis and compilation for…[Read more]

Actually, I found the RunTest code in OsvvmProjectScripts.tcl, and the best way to add additional options for this would be following Example_LocalScriptsDefaults.tcl I assume?

The AXI4Manager source code contains these lines in the architecture declaration part:

signal WriteAddressFifo : osvvm.ScoreboardPkg_slv.ScoreboardIDType ;
signal WriteDataFifo : osvvm.ScoreboardPkg_slv.ScoreboardIDType ;

signal ReadAddressFifo : osvvm.ScoreboardPkg_slv.ScoreboardIDType ;
signal…[Read more]