2.2.1. TDATA Pixel Packing
2.2.2. RGB Pixel Packing
2.2.3. YCbCr 444 Pixel Packing
2.2.4. YCbCr 422 Pixel Packing
2.2.5. YCbCr 420 Pixel Packing
2.2.6. Four-Channel Video Pixel Packing
2.2.7. Packing with Multiple Pixels in Parallel
2.2.8. Multiple Pixels in Parallel and Empty Pixels
2.2.9. YCbCr 422 Video with Multiple Pixels in Parallel
2.2.10. Packing RGB444 onto an RGB888 Interface
2.2.11. Packing with Less than 8 bits per Symbol Natively
2.2.12. Interlaced Fields
2.1. Metapackets (Full Variants)
Metapackets usually carry control information. Use metapackets in the full variant of the Intel FPGA streaming video protocol but not in the lite variant. Metapacket lengths are between 1 to 4 beats (clock cycles).
Figure 6. Intel FPGA streaming metapacket (full variant only)The figure shows a packet where TUSER[1] is high in beat 0, which shows this packet is a metapacket.
TUSER[1] is decoded during the first valid beat of the packet (beat 0 in the figure) and a high value indicates the start of a new metapacket. TUSER[0] and TUSER[1] should be low for the remainder of the packet.
TUSER[1:0] | Meaning |
---|---|
00 | Video packet (from either an interlaced (F0 or F1) field or progressive frame). |
01 | Video packet (start of either an interlaced (F0 or F1) field or progressive frame). |
10 | Metapacket. |
11 | Reserved. |
Metapackets carry their information in the low 16 bits of TDATA. The protocol does not require any additional TDATA bits. The protocol defines different metapacket types, each with a 5 bit packet identifier carried in the 5 LSBs of the first beat of the packet.
Figure 7. Metapacket format
The protocol classifies metapackets into image information, end of field, auxiliary control and user-defined auxiliary control packets.
Packet identifier | Packet type |
---|---|
0 | Image information |
1 | End of field |
Auxiliary control packets | |
2 | Timestamp |
3 | Register update |
4 | Commit |
5-15 | Reserved |
User-defined auxiliary control packets | |
16 - 31 | General-purpose user |
Related Information