FPGA & SoM modules
Flexible AMD Zynq™ UltraScale+™, AMD Versal™, RFSoC, Agilex V and PolarFire modules.
Five architectural features to evaluate when moving from AMD Zynq UltraScale+ to selected AMD Versal AI Edge Series Gen 2 devices. Understand where hard IP, AI Engines, programmable logic and Arm processors fit—and what must be measured before choosing a device.
Understand how dedicated ISP tiles can move supported RAW sensor conditioning out of programmable logic. Check input patterns, pixel packing, bit depth, throughput and output formats before assigning demosaicing, correction and colour processing to the hardened path. Keep custom interfaces, timestamping and unsupported corrections in PL.
The guide explains how to budget parallel output streams and compare LUT, DSP and BRAM use, power and end-to-end latency with your existing ZU+ pipeline. This feature matters when your application includes compatible sensor data; it is not a requirement for every embedded system.
Explore the separate vector-compute array, tile-local memories and streaming interconnects. Partition acquisition and deterministic transforms in PL, supported inference or vector kernels in AI Engines, and application control on Arm processors. Operator support, tensor tiling and supported numerical formats determine what can actually be mapped.
Learn why local-memory reuse and DDR spills can dominate sustained throughput. Compare accuracy, latency, batch size, concurrent workloads and board power with the same ZU+ baseline. Peak TOPS alone cannot establish an application-level improvement.
Build a traffic budget for every producer, consumer and buffer: payload rate, read/write passes, burst behaviour, memory destination and latency class. The dedicated NoC connects processors, accelerators, PL and memory controllers; route selection and quality-of-service settings affect service under contention.
The guide uses a concrete bandwidth calculation to show how a modest input rate becomes a much larger DDR load after repeated passes. Learn when streaming and on-chip retention help, and how to measure usable bandwidth, tail latency and dropped data with all concurrent masters active.
Separate Linux application services from bounded real-time control. Define the APU/RPU split, interrupt handling, shared-buffer ownership and interprocessor communication. Check coherent versus noncoherent DMA paths explicitly; an accelerator accessing shared memory does not automatically guarantee cache coherency.
Understand how local memories and R52 operating modes influence scheduling and independent-core availability. Compare CPU headroom and worst-case deadline response with equivalent software, peripheral traffic and thermal conditions on ZU+.
Evaluate hardened AVC/H.264 and HEVC/H.265 encoding and decoding as part of the complete data path. Verify device-specific pixel formats, bit depth, aggregate throughput, rate control and latency alongside colour conversion, buffers and packetisation.
The guide explicitly accounts for ZU+ EV devices that already contain a hardened VCU. Attribute any benefit to supported formats, simultaneous workloads, power or system consolidation, rather than assuming a generic compression gain. Keep time-critical metadata independent of the encoded stream.
Each section includes how to use the feature, what benefit to target, implementation steps, design-review questions and measurements against an AMD Zynq UltraScale+ baseline. Availability varies by device; the five features are not shared by every AMD Versal family.