Skip to content

Vivado

Commands

set_msg_config

AMD Manual

set_msg_config provides a way to:

  • Promote or downgrade the severity of messages that Vivado can emit.
  • Disable the limit on number of messages emitted.

Tip

set_msg_config can't be used in a .xdc file. You must use a .tcl file.

Changing message severity

# Promote various warnings to errors
set_msg_config -id {[Synth 8-327]}      -new_severity ERROR;  # Inferring a latch
set_msg_config -id {[Synth 8-6859]}     -new_severity ERROR;  # Multiple drivers
set_msg_config -id {[Timing 38-282]}    -new_severity ERROR;  # Timing failure
set_msg_config -id {[Vivado 12-4739]}   -new_severity ERROR;  # No valid object found

Note

Promoting to ERROR should also cause Vivado to terminate the process.

Using TCL files instead of XDCs

.tcl files need to be added as "sources" not "constraints".

Warning

If you are using the replace feature to change a .xdc to .tcl, you need to manually (or with a script) change the file type from XDC to TCL in the properties. This is not autodetected.

Warning

Modifying .tcl files does not appear to trigger rebuilds, even if the file is marked appropriately as "For Synthesis/Implementation".

Hardware Platforms

Hardware platforms in vivado are zip files with the extension .xsa (Xilinx Support Archive).

They are used to export a design from vivado for other parts of the Xilinx ecosystem to consume.

Note

Historically, these were called Hardware Definition Files (.hdf).

XSA was introduced around 2019.2.

Creating a hardware platform

Once an FPGA bitstream has been built using vivado:

write_hw_platform -fixed -include_bit -force \
    -file $xsa_file_path