The Tcl command pr_verify confirms compatibility
for both Segmented Configuration PL reload and DFX use cases. The command now supports
the combined use case.
The command compares both Segmented Configuration and DFX rules by default when
both features are enabled. In a single Vivado DFX project
that uses parent and child runs, this behavior does not change. In a single parent
impl_1 run, the locked DFX static design requires
the boot partition for Segmented Configuration to remain unchanged. As a result, the PL
reload checks pass.
The -segcfg_only switch supports comparisons across different projects
for the PL Reload use case. When the PL implementations differ, the static PL domain
also differs. In this case, the DFX checks fail. This switch instructs
pr_verify to compare the two designs only for PL Reload
compatibility.
For PL Reload, you must run pr_verify manually because no project mode
includes built-in compatibility checking. Follow the PL Reload flow to associate
projects by sharing boot-domain IP and the NoC solution file
(.ncr).
For PL reload, list the golden configuration first, and then list the new design
configuration. The golden version must contain the superset of PS/PL connectivity. The
boot.pdi from the golden version is the image that the primary boot
device loads.
pr_verify -initial parent_routed.dcp -additional child_routed.dcpThis example checks DFX compatibility.
pr_verify -segcfg_only -initial golden_routed.dcp -additional secondary_routed.dcpThis example checks Segmented Configuration compatibility.