Visible to Intel only — GUID: dad1642432530459
Ixiasoft
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
Visible to Intel only — GUID: dad1642432530459
Ixiasoft
3.2. Rules for IPs
To support the Intel FPGA streaming protocol, IP must meet the following guidelines:
- IPs must be compliant to the AXI4-S protocol.
- IPs must support the full, lite or both modes of the protocol.
- IPs can only support the modes of the protocols as described in the Intel FPGA Streaming Video Protocol Specification.
- If receiving an end-of-field packet with a set broken bit, IPs must also output end-of-field packets with the broken bit set, unless the IP fixes the field.
- Full variant IPs must propagate unsupported auxiliary packets unmodified and with packet ordering unchanged.
- Full variant IPs must process all image information and end-of-field packets and extract and use that video field information.
- Full variant IPs must propagate any commit, timestamp, and any other auxiliary control packets, unless the auxiliary control packet’s ultimate destination is that IP.
- Full variant IPs must set the broken bit in the outgoing end-of-field packet for any relevant fields. For example, fields break when you request a clipper IP clips all video fields down to a width of 1000 pixels, but incoming fields are of width 900 pixels.
- Lite variant IPs exhibit undefined behavior if receiving full variant packets.
Protocol Errors
This protocol mandates no specific behaviors for IPs using the Intel FPGA streaming video protocol for handling malformed packets or protocol errors on incoming interfaces.
Related Information