Video and Vision Processing Suite IP User Guide

ID 683329
Date 3/30/2025
Public

Visible to Intel only — GUID: rxw1640105567174

Ixiasoft

Document Table of Contents
1. About the Video and Vision Processing Suite 2. Getting Started with the Video and Vision Processing IPs 3. Video and Vision Processing IPs Functional Description 4. Video and Vision Processing IP Interfaces 5. Video and Vision Processing IP Registers 6. Video and Vision Processing IPs Software Programming Model 7. Protocol Converter IP 8. 1D LUT IP 9. 3D LUT IP 10. Adaptive Noise Reduction IP 11. Advanced Test Pattern Generator IP 12. AXI-Stream Broadcaster IP 13. Bits per Color Sample Adapter IP 14. Black Level Correction IP 15. Black Level Statistics IP 16. Chroma Key IP 17. Chroma Resampler IP 18. Clipper IP 19. Clocked Video Input IP 20. Clocked Video to Full-Raster Converter IP 21. Clocked Video Output IP 22. Color Plane Manager IP 23. Color Space Converter IP 24. Defective Pixel Correction IP 25. Deinterlacer IP 26. Demosaic IP 27. FIR Filter IP 28. Frame Cleaner IP 29. Full-Raster to Clocked Video Converter IP 30. Full-Raster to Streaming Converter IP 31. Genlock Controller IP 32. Generic Crosspoint IP 33. Genlock Signal Router IP 34. Guard Bands IP 35. Histogram Statistics IP 36. Interlacer IP 37. Mixer IP 38. Pixels in Parallel Converter IP 39. Scaler IP 40. Stream Cleaner IP 41. Switch IP 42. Text Box IP 43. Tone Mapping Operator IP 44. Test Pattern Generator IP 45. Unsharp Mask IP 46. Video and Vision Monitor Intel FPGA IP 47. Video Frame Buffer IP 48. Video Frame Reader Intel FPGA IP 49. Video Frame Writer Intel FPGA IP 50. Video Streaming FIFO IP 51. Video Timing Generator IP 52. Vignette Correction IP 53. Warp IP 54. White Balance Correction IP 55. White Balance Statistics IP 56. Design Security 57. Document Revision History for Video and Vision Processing Suite User Guide

5.1. Video and Vision Processing IP Control Examples

Consider which control method best suits your application. Configure the IP according to one of the following methods.
Figure 8.  Full variant with no memory-mapped control interface, fixed operationThe figure shows a video pipeline with a video ingress system (for example, HDMI, Displayport, PCIe) and two IPs, the second IP is the Clipper.

In this system, the full variant clipper IP is parameterized to perform a fixed clip of 1080p HD video clipped down to 720p HD video and has no memory-mapped control interface. The clipper parameters always clip to a height and width of 1280x720 pixels. No further control is necessary as information about the incoming video fields is carried in image information control packets (refer to the Intel FPGA streaming video protocol specification). So, if the input resolution changed to 720p, the clipper reads that information from the image information packets and performs no additional clipping.

The figure shows the video protocol packets from the video ingress subsystem. The packets stream into IP1, which doesn’t change the dimensions of the video. It sends the same image information packets and the same number of data packets into the clipper IP.

The figure shows an image information packet with the video field information for a progressive frame of 1920x1080 pixels. Each video packet carries one line of 1920 pixels.

The image information packet from the clipper contains the new field dimensions of 1280x720 and the clipper only outputs 720 video packets, each of 1280 pixels.

Figure 9. Full variant with memory-mapped control interfaceThe figure shows the same system but with a full variant clipper and with a memory-mapped run-time control interface. A processor in the system connects to the clipper via an Avalon memory-mapped interface.

Most systems need to control IPs so that you can apply different amounts of clipping, scaling or mixing. In this system, the full variant of the clipper IP now includes a memory-mapped control interface. The clipper IP includes a register map and the processor can read the clipper's parameter information and set clipping offsets for any clipping style that you want. When the processor writes any changes to clipping requirements, a final write to the COMMIT register (or receiving a commit auxiliary control packet) ensures they apply when the IP receives the next image information packet to mark the start of the next field.

The processor can also read the dimensions of the incoming video and the count of incoming fields if you turn on Debug features.

Intel recommends this method of control, which is the simplest and most flexible.

Figure 10. Lite variants with mandatory memory-mapped control interfaceThe figure shows the system with the lite variant clipper and a memory-mapped control interface. A processor connects to both the video ingress system and the clipper via Avalon memory-mapped interfaces.

In this example, the lite variant clipper IP is parameterized with the mandatory memory-mapped control interface. In lite variant IPs, the processor writes the field’s properties to the clipper’s IMAGE_INFO registers. The streaming interface just contains video data. Otherwise, control operates as for full variant IPs with memory-mapped control. The processor also writes desired clipping dimensions to the clipper’s register map.