Vivado Design Flow - Vivado Design Flow - 2026.1 English - UG909

Vivado Design Suite User Guide: Dynamic Function eXchange (UG909)

Document ID
UG909
Release Date
2026-07-01
Version
2026.1 English

Within Vivado, this combined support is essentially the union of both solutions. Segmented Configuration splits the programming instructions into two files: Boot.PDI and PLD.PDI. DFX creates partial programming images that are subsets of the PLD.PDI. The result is a flexible programming environment similar to tandem with field updates or nested DFX, which AMD UltraScale+™ devices support. In the following simplified figure, the region enclosed in the red box represents the boot domain, and the remaining features represent the PLD domain.

Figure 1. Boot Domain and PLD Domain

Segmented configuration splits the initial device programming between the PS and PL domains. The PL Reload feature lets you load different versions of the PLD for a given boot PDI. Different PLD images are typically generated from different Vivado projects and linked by a common NoC solution for consistency.

Figure 2. Segmented Configuration with PL Reload

With DFX, after the Boot and PLD images that represent the complete static design are loaded, you can deliver a partial PDI on the fly to change functionality in the PL domain. You can create different partial PDIs with the DFX design flow in Vivado.

Figure 3. Static and Partial PDI

When you combine PL Reload and DFX, you can modify the DFX static design to create different floorplans for different design requirements. To deliver a partial PDI for a given floorplan or static PL design, you must first load the appropriate PLD image.

Figure 4. Multiple Floorplans with Partial PDI