Activity

Hi Jim,

Thanks for the response. I did look at this section 7.3 before I sent out my request. My question is how exactly do you specify these values in the Send transaction?. Do you append the TKeep/TStrb value(WW | UU) to the Data field in Send transaction?. Looked at Param field. Param deals with TID, TDEST and TUSER and TLAST. Is there an…[Read more]

Hi Senthil
See OsvvmLibraries/Documentation/AxiStream_user_guide.pdf:

7.3 Setting and Checking TKeep and TStrb
On the AxiStream interface, a TStrb value that corresponds to a data value of ‘1’ indicates the value
contains valid data. A value of ‘0’ indicates it is a filler value. A TKeep value of ‘1’ indicates the value is
either valid data or a…[Read more]

Hi Jim,

Thank you for the quick response. I’m working with a custom VC. You’re right, the problem was that BurstFifo wasn’t initialized in the VC. I added the following at the beginning of the VC’s transaction handler process, and it worked.

RX_IF.BurstFifo <= NewID("RxBurstFifo", ModelID, Search => PRIVATE_NAME) ;


I appreciate the tip on…[Read more]

Hi Minteng,
When an ID has a value of -2**31 (-2147483648), it has not been initialized yet.
OSVVM VC, such as AxiStream, initialize the TransRec.BurstFifo signal at time 0 ns delta cycle 1,
so it is not valid until time 0 ns delta cycle 2.

Are you working with an OSVVM VC or one of your own? If it is an OSVVM VC, time is either 0 ns
or the…[Read more]

Hi Jim,
I tested the same test case with Questasim, and I’m not seeing the same issues.

Regards,
Remy

Hi Jim,
I updated the AXI FULL OSVVM testbench available here.


architecture TestHarness of TbAxi4 is
constant AXI_ADDR_WIDTH : integer := 16 ;
constant AXI_DATA_WIDTH : integer := 256 ;
constant AXI_STRB_WIDTH : integer := AXI_DATA_WIDTH/8 ;


I modified the width of AXI DATA and AXI ADDR, and adapted the test cases to include the new…[Read more]

Hi Remy,
Can you share exactly what you updated? Is it a particular OSVVM testbench or one of your own.

The test cases that do bursts as words will not work as they likely have dependencies on a specific size interface. The test cases that do bursts as bytes are expected to work though.

Best Regards,
Jim