The data fields are packed into the m_axis_data_tuser vector in the following order (starting from the LSB):
1. (optional) XK_INDEX plus padding
2. (optional) BLK_EXP plus padding for channel 0
3. (optional) BLK_EXP plus padding for channel 1 etc.
4. (optional) OVFLO for channel 0
5. (optional) OVFLO for channel 1 etc.
6. Padding to make TUSER 8-bit aligned. Only needed when OVFLO is present
Note that the core cannot be configured to have both BLK_EXP and OVFLO .
|
X-Ref Target - Figure 3-8 
|
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.