Activity

I believe that the GetAxiStreamOptions could just be used with DEFAULT_ID, DEFAULT_DEST, DEFAULT_USER. However, I am not sure why this is not done anywhere in any testbench that comes with OSVVM.

4. The AXI stream receiver gets the ID, DEST and USER from the transmitter VC. When it gets the data, we can access what the transmitter sent it. What then is the meaning of SetAxiStreamOptions for the receiver? It should only have GetAxiStreamOptions just like it has Get and no Send command. It is a receiver after all.

The USER can be assigned as follows:
SetAxiStreamOptions(StreamTxRec, DEFAULT_USER, User);

Or, within the send and sendburst commands:
Send(StreamTxRec, X”AAAA_AAAA”, ID1 & DEST1 & USER1 & ‘0’, TRUE) ;
SendBurst(StreamTxRec, 8, ID2 & DEST2 & USER2 & ‘1’) ;

The check can be done like this:
Check(StreamRxRec, X”BBBB_BBBB”, ID1 & DEST1 & USER1 &…[Read more]

> What is the meaning of writing something like this: GenBin(2,10,2)

If this is the only GenBin for a given coverage model, this does not change anything.

Note the coverage model that I edited into the previous discussion for the AxiStreamTransmitter. If I instead did:
AddBins (BurstCov.BurstDelayCov, 80, GenBin(2,8,2)) ; -- 80% Small…[Read more]

What is the meaning of writing something like this: GenBin(2,10,2) where the number of bins is more than one, as far as the DelayCoverage Model is concerned?

> Q1. When the GenBin has 3 numbers, why does it always end with 1? This means that we are creating a single bin that has the specified range? This means that any integer can occur in that range with equal probability?

The third parameter indicates how many bins to split a range into. As you observed, this puts it all in one bin. It is indeed…[Read more]

There was. It was removed as it did not work in one of the vendors. I will need to add it back.

I guess converting it into record is the correct way forward in that case, since that is how it works with the memory mapped AXI4 VC.

So is there any example that uses the AxiStreamGenericSignalsPkg at the moment?

Hi Hassan
The AXI interface has a number of optional signals. How to handle these is the interesting proposition. Their width can be configured. The current VC leaves them unconstrained. This means they have to be connected, even if unused and connected to a 0 width std_logic_vector(0 downto 1).

That said, can their impact be minimized.…[Read more]

One more thing. I created the dummy signals but the forgot to update this line:

constant AXI_PARAM_WIDTH : integer := TID_MAX_WIDTH + TDEST_MAX_WIDTH + TUSER_MAX_WIDTH + 1 ;

I had to add the TID_MAX_WIDTH + TDEST_MAX_WIDTH + TUSER_MAX_WIDTH back into them. Certainly the setup feels rather fidly.

I have used these 3 attributes in a process but it seems that Quartus synthesis does not support any of them at all. It just gives error “predefined attribute … is not supported”

p_assert_generics: process
begin

report p_assert_generics’simple_name severity warning;
report p_assert_generics’instance_name severity warning;…[Read more]