About Physical Constraints - 2023.2 English

Vivado Design Suite User Guide: Using Constraints (UG903)

Document ID
UG903
Release Date
2023-11-01
Version
2023.2 English

The AMD Vivado™ Integrated Design Environment (IDE) enables design objects to be physically constrained by setting values of object properties. Examples include:

  • I/O constraints such as location and I/O standard
  • Placement constraints such as cell locations
  • Routing constraints such as fixed routing
  • Configuration constraints such as the configuration mode

Similar to timing constraints, physical constraints must be saved in an XDC file or a Tcl script so that they can be loaded with the netlist when you open a design. After the design is loaded in memory, you can interactively enter new constraints using the Tcl Console, or by using one the Vivado Design Suite IDE editing tools.

Most physical constraints are defined by means of properties on an object:

set_property <property> <value> <object list>

The exception is for area constraints which use Pblock commands.