From pixelcontrol
R2026bLibraries:
Vision HDL Toolbox /
I/O Interfaces
Description
The From pixelcontrol block accepts the pixelcontrol bus protocol used by
Vision HDL Toolbox™ blocks and converts to AXI4-Stream control signals. Use this block and the
To
pixelcontrol block when your model contains Vision HDL Toolbox blocks and algorithms that use AXI interfaces.
This diagram shows the dataflow using these conversion blocks. The To
pixelcontrol block converts input AXI4-Stream signals to the
pixelcontrol protocol. If you send more than one pixel, or more than
one component per pixel, in each AXI4-Stream transfer, you must unpack the
data output and create a
numPixels-by-numComponents matrix for the
pixel input to the Vision HDL Toolbox algorithm. At the output of the Vision HDL Toolbox algorithm, you can pass a scalar pixel value to the From
pixelcontrol block, or repack
numPixels-by-numComponents values into the
data input.
![]()
The waveform shows a 2-line-by-3-pixel frame arriving at the input in
pixelcontrol bus protocol and the output in AXI4-Stream protocol.
Each data value represents a single pixel. The block converts the input
pixelcontrol start-of-line (hStart), end-of-line
(hEnd), start-of-frame (vStart), and end-of-frame
(vEnd) signals to AXI4-Stream packets where each packet represents
one video line. The TLAST signal indicates the end of each video line.
The block buffers one line before making any AXI4-Stream transfers, so that the output line
has continuous valid pixels. The block maintains inactive cycles between
lines and frames, according to the specified Video format.
For more information on the pixelcontrol protocol, see Streaming Pixel Interface.
For more information on the requirements for inactive cycles in the
pixelcontrol protocol, see Configure Blanking Intervals.
![]()
Ports
Input
Output
Parameters
Extended Capabilities
Version History
Introduced in R2026b