Activity

Thanks Jim, that solved my problem.

Regards,

Francois

Hi Francois,
Look at package OsvvmLibraries/Common/src/StreamTransactionPkg.vhd and see StreamRecType.
Note that each type in there is either a special type from OSVVM’s ResolutionPkg (see OsvvmLibraries/osvvm)
or by creating a custom resolution function, as was done for the enumerated type, StreamOperationType,
that was defined in the package.…[Read more]

Hi Jim,

I did create my own record:
type test_command_type is (AssertResetCmd, DeassertResetCmd, AssertEnableCmd, DeassertEnableCmd, RunCounterCmd, StopCounterCmd, ReadCounterCmd, DoneCmd);

type CounterRecType is
record
rdy : RdyType;
ack : AckType;
cmd : test_command_type;
counter : STD_LOGIC_VECTOR(7 downto…[Read more]

Hi Francois,
The VC in the OSVVM library use either osvvm_common.StreamTransactionPkg.StreamRecType (for send and get type transactions – used by UART, AxiStream, xMii) or osvvm_common.AddressBusTransactionPkg.AddressBusRecType (for read and write type transactions – used by Axi4Manager, Axi4Memory, DpRam, WishboneManager,…[Read more]

If the CoverReport process is removed, then the “Stim” process can end with std.env.stop – which is typically how OSVVM ends the test cases.

— Stimulus Generator
Stim: process
variable RandA : RandomPType;
variable RandB : RandomPType;
variable allDone : boolean := false;
variable nCycles : natural := 0;
begin…[Read more]

One final thing to try. If you like the Alert/AffirmIf printing, you might also like the log printing better than the vhdl Report statement. In the “Stim” process you could change these to logs:

log("Number of simulation cycles = " & to_string(nCycles));
log("Coverage holes: " & to_string(CountCovHoles(cp_A_B)));


Logs have levels.…[Read more]

This step is recommended, but not required. Do it after you get the above running.

To get the HTML based Functional Coverage reports, you need to use the singleton rather than the older, deprecated shared variable approach.

This requires updating your architecture declarations, “InitCoverage”, “Sample”, and “CoverageReport” processes as…[Read more]

This step is recommended, but not required. Do it after you get the above running.

While I SetTestName, SetLogEnable can be called concurrently, it is more normal to call them in the process that is controlling the overall test. Currently this is the “Stim” process but we will return to this:

Stim: process
variable RandA : RandomPType;…[Read more]