-
Notifications
You must be signed in to change notification settings - Fork 104
Description
Hi,
cocotbext-axi = 0.1.24
I'm having trouble understanding how to drive AxiStreamFrame to get the TUSER behaviour i'm after. I have a 64bit TDATA and 64bit TUSER so I have a TUSER byte per TDATA byte.
When sending a frame of two 64bit data beats, I wanted to have different values for TUSER. Here is the debug log of the AxiStreamFrame source:
200.00ns INFO ..otb.axis_dwidth_converter.s_axis TX frame: AxiStreamFrame(tdata=bytearray(b'\x01dq\x9f\xb5k\xd3NI\xb6o\x8d\xaaR\xecQ'), tkeep=None, tid=None, tdest=None, tuser=[6718263372833897734, 11359403004288960693], sim_time_start=200001, sim_time_end=None)
As you can see, I have a TUSER list of 2 x 64bit values. But in the simulation i'm seeing this (i've added the s_axis_tuser channel twice, once in hex format and once in decimal so it's easy to compare with the debug log above):
It appears only the last element of the list is being presented on the TUSER channel. How would I drive this to get difference TUSER values on each data beat?
Thanks.
