Design Planning Considerations for the Platform-Based Design Flow - Design Planning Considerations for the Platform-Based Design Flow - 2026.1 English - UG1387

Versal Adaptive SoC Hardware, IP, and Platform Development Methodology Guide (UG1387)

Document ID
UG1387
Release Date
2026-07-22
Version
2026.1 English

With Versal adaptive SoC platform-based design flow, partition your design between the hardware platform and a subsystem. The hardware platform is created in the Vivado tools, and the subsystem is created and added into the platform by the AMD Vitis™ environment.

To succeed with this design flow, you must identify the sections to include in the platform. You must also identify the sections to incorporate via the Vitis environment. The platform is expected to contain common shared resources. The Vitis environment likely incorporates the specialized components of the design.

Common examples of IP contained in the platform include:

  • CIPS/PS Wizard
  • NoC interconnect
  • Clocking
  • Reset
  • Interrupt controllers

The Vitis environment accepts several types of design sources, including the following:

  • Packaged BD
  • Packaged RTL
  • HLS C code
  • AI Engine kernel code
Note: The graph file defines the connectivity between AI Engine kernels and between AI Engine kernels and the platform.

The following figure shows an example of the platform-based design flow.

Figure 1. Platform-Based Design Flow