Video and Vision Processing Suite Intel® FPGA IP User Guide

ID 683329
Date 2/15/2022

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents

17.1. About the Pixels in Parallel Converter IP

The Intel FPGA streaming video protocol allows multiple pixels to be transmitted in a single clock cycle (beat). The number of pixels the interface transmits per beat (pixels in parallel) is a fixed property of the interface. The IP converts from one value of pixels in parallel at the input interface to a higher or lower number of pixels in parallel at the output interface. The IP supports any number of pixels in parallel between 1 and 8 for both the input and output interface and supports all possible conversions.

To help manage data rates, the IP includes the option for a FIFO buffer on the datapath. For conversions that lower the pixels in parallel, the IP locates the FIFO buffer at the input interface, before the conversion logic. For conversions that increase the pixels in parallel, the IP locates the FIFO buffer at the output interface, after the conversion logic. A parameter selects either single clock or dual clock mode for the FIFO buffer. If you select dual clock mode, the input and output interfaces can run on different clock domains.

To correctly implement the pixels in parallel conversion in all cases, the IP must know how many pixels are in each video line. Without this information the IP does not know how many of the pixels in parallel are valid on the final beat of each video line packet. If you configure the IP for use with the full variant of the Intel FPGA streaming video protocol, you can obtain this information directly from the image information packets contained within the video stream. The IP has is no requirement for a register map or for the control agent interface to access it. If you configure for the lite variant of the protocol, the video stream has no image information so you must supply the line length through the register map, via the control agent interface. Selecting to use the lite variant of the protocol automatically enables the control agent interface.