Visible to Intel only — GUID: mmg1642601696208
Ixiasoft
Visible to Intel only — GUID: mmg1642601696208
Ixiasoft
2.2. Video Packets
TUSER[0] is decoded in the first valid cycle of the packet. The start of a new video field is indicated when TUSER[0] is high in this cycle.
Video packets carry pixel data. Both full and lite variants of the protocol use video packets. Video packets may be 1 or more beats in length.
In the example, TUSER is 4 bits wide, as the 30 bits of pixel data occupy 4 bytes of TDATA. In the first beat of the transfer, TUSER indicates a new field of video by asserting TUSER[0] high and TUSER[1] low to indicate a video packet. Other TUSER bits, e.g. TUSER[3:2], can take any value, but IPs compliant with the Intel FPGA streaming protocol do not have to propagate these values and it is recommended that these are held low. TLAST indicates the last pixel in each line.
TUSER[0] indicates the start of a new video field, but you cannot tell which video packet is the last line of the field. The full variant of the protocol allows the detection of the end of the current video field by the arrival of an end of field packet. The lite variant has no signaling for the end of the current field, but TUSER[0] indicates the first pixel of the next field.
Lite variants have no metapackets so TUSER[1] is always low for progressive video. The video packet for the first line of each frame is indicated by TUSER[0].
Full variants add image information and end of field packets to describe the frame properties and mark the end of each frame.
Section Content
TDATA Pixel Packing
RGB Pixel Packing
YCbCr 444 Pixel Packing
YCbCr 422 Pixel Packing
YCbCr 420 Pixel Packing
Four-Channel Video Pixel Packing
Packing with Multiple Pixels in Parallel
Multiple Pixels in Parallel and Empty Pixels
YCbCr 422 Video with Multiple Pixels in Parallel
Packing RGB444 onto an RGB888 Interface
Packing with Less than 8 bits per Symbol Natively
Interlaced Fields