The data fields are packed into the
m_axis_data_tuser
vector in the following order (starting from the
LSB):
- (optional)
XK_INDEX
plus padding - (optional)
BLK_EXP
plus padding for channel 0 - (optional)
BLK_EXP
plus padding for channel 1 etc. - (optional)
OVFLO
for channel 0 - (optional)
OVFLO
for channel 1 etc. - Padding to make TUSER 8-bit aligned. Only needed when
OVFLO
is present
The core cannot be configured to have both BLK_EXP and
OVFLO
.
Figure 1. Data Output Channel TUSER (m_axis_data_tuser) Format
Optional fields are shown as dotted. As all fields are optional, it is possible to configure the core such that TUSER would have no fields. In this case it is automatically removed from the core interface.