Nested DFX Design Considerations - 2024.1 English

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

Document ID
Release Date
2024.1 English

Nested Dynamic Function eXchange designs must follow the same rules and recommendations as standard Dynamic Function eXchange designs. Treat the parent RP (and above) as the static design. All design requirements for DFX are the same from the perspective of the reconfigurable boundary.

The Nested DFX solution does not allow more than one RP in a design to be subdivided until the first RP has a placed and routed implementation. Focus attention on a specific RP to create lower-level results. You can launch implementation runs in parallel after the design structure and floorplan is established.