IPSR-VIDEO Altera, IPSR-VIDEO Datasheet - Page 129

• Manufacturer Part Number: IPSR-VIDEO
• Description: RENEWAL Of IPS-VIDEO
• Manufacturer: Altera
• Series: IP Suitesr

Specifications of IPSR-VIDEO

• Software Application: IP CORE, SUITES
• Supported Families: Arria GX, Cyclone II, HardCopy II, Stratix II
• Features: Common Avalon Streaming (Avalon-St) Interface And Avalon-St Video Protocol
• Core Architecture: FPGA
• Core Sub-architecture: Arria, Cyclone, Stratix
• Rohs Compliant: NA
• Lead Free Status / RoHS Status: na

Chapter 5: Functional Descriptions
Frame Reader
Table 5–20. Frame Buffer Avalon-ST Video Protocol Parameters
Frame Reader
January 2011 Altera Corporation
Frame Width
Frame Height
Interlaced /
Progressive
Bits per Color Sample
Color Pattern
Parameter
Handling of Avalon-ST Video Control Packets
The Frame Buffer MegaCore function stores non-image data packets in memory as
described in
packets are never repeated and they are not dropped as long as the memory space is
sufficient. Control packets are not stored in memory. Input control packets are
processed and discarded by the writer component and output control packets are
regenerated by the reader component.
When a frame is dropped by the writer, the non-image data packets that preceded it
are kept and sent with the next frame that is not dropped. When a frame is repeated
by the reader, it is repeated without the packets that preceded it.
The behavior of the Frame Buffer MegaCore function is not determined by the field
dimensions announced in Avalon-ST Video control packets and relies exclusively on
the startofpacket and endofpacket signals to delimit the frame boundaries. The
Frame Buffer can consequently handle and propagate mislabelled frames. This feature
can be used in a system where dropping frame is not an acceptable option. The
latency introduced during the buffering could provide enough time to correct the
invalid control packet.
Buffering and propagation of image data packets incompatible with preceding control
packets is an undesired behavior in most systems. Dropping invalid frames is often a
convenient and acceptable way of dealing with glitches from the video input and the
Frame Buffer can be parameterized to drop all mislabelled fields or frames at compile
time. Enabling flow-controlled frame repetition and turning on this option can
guarantee that the reader component keeps on repeating the last valid received frame,
that is, freezes the output, when the input drops.
The Frame Buffer MegaCore function can process streams of pixel data of the type
shown in
The Frame Reader reads video frames stored in external memory and outputs them
using the Avalon-ST Video protocol.
The Frame Reader has an Avalon-MM read master port that reads data from an
external memory. The Frame Reader has an Avalon-ST source on which it streams
video data using the Avalon-ST Video protocol. The Frame Reader also has an Avalon
slave port, which provides the MegaCore function with configuration data.
Run time controlled. Maximum value selected in the parameter editor.
Run time controlled. Maximum value selected in the parameter editor.
Progressive, although interlaced data can be accepted in some cases.
Number of bits per color sample selected in the parameter editor.
Any combination of one, two, three, or four channels in each of sequence or
parallel. For example, for three channels in sequence where , , and can be any
color plane:
Table 5–20 on page
“Buffering of Non-Image Data Packets in Memory” on page
5–49.
Value
Video and Image Processing Suite User Guide
4–21. User
α
β
γ
5–49