Document ID
APT-DS-CXP-DEV-0001
Revision
1.0
IP version
2.2.0
Release date
November 2026
Chapter 6: Resources and Ordering

6.2Resource utilization

The pixel formats you switch on set most of the size difference between builds. The table below is an estimate of the pixel path block alone, so you can see what a format costs; read it as one build against another. A Vivado utilization report for your build, including the transmit path, the protocol handling and the FIFOs, comes with the evaluation.

Table 6-2.What a format switch costs: estimate of the pixel path block alone at 4 pixels of 16 bits per beat, UltraScale+. Read it as the size of one build against another; it is not a Vivado utilization report.
Formats builtHost LUTHost FFDevice LUTDevice FFDevice BRAM
Mono / Bayer, 8-bit only127869891
Mono / Bayer, 8, 10 and 12-bit406275413289
Mono / Bayer, every depth (default)841510792489
adds YCbCr 4:2:21,051707883625
adds YCbCr 4:2:2 and 4:2:01,0897089337012
adds RGB1,194836921690
adds RGB and YCbCr 4:4:41,2638361,160690
everything (25 formats)1,3891,0341,2079022
  • Bit depths are the larger lever: each depth in Bit depths on the link is a gearbox of its own. A product that only runs 8 to 12-bit saves about half of the pixel path.
  • RGB and YCbCr 4:4:4 share one layout block, YCbCr 4:2:2 and 4:2:0 the other; switching off one of a pair saves little.
  • The video input FIFO is tdata + 2 bits wide: one BRAM36 at 512 beats of the default 64-bit bus, three for the 192-bit bus. YCbCr 4:2:0 adds the chroma line store, two BRAM36 at 4,096 pixels.