Custom Tcl constraints for floorplanning, placement, and timing of the kernels will need to be reviewed in the context of the new target platform (.xsa). For example, if a kernel needs to be moved to a different SLR in the new target platform, the placement constraints for that kernel will also need to be modified.
In general, timing is expected to be comparable between different target platforms that are based on the 9P Virtex UltraScale device. Any custom Tcl constraints for timing closure will need to be evaluated and might need to be modified for the new platform.
Custom constraints can be passed to the
Vivado®
tools using the [advanced]
directives of the v++ configuration file specified by
the --config option. Refer to Managing Vivado Synthesis and Implementation Results more information.