Using the Messages Window - 2023.2 English

Vivado Design Suite User Guide: Design Analysis and Closure Techniques (UG906)

Document ID
UG906
Release Date
2023-10-19
Version
2023.2 English

There are two types of messages:

  • Messages stored on disk
  • Messages stored in memory

The Vivado Integrated Design Environment (IDE) groups messages in the Messages window by the action that created the message. Use the settings buttons on the toolbar menu to group the messages by message ID or file.

Figure 1. Messages Window

Some messages include hyperlinks to a file or a design element to help in debugging. Click the link to view the source.

Tip: Use the popup menu to copy messages to paste into another window or document.

Each message is labeled with a message ID and a message severity.

  • Message ID: The message ID identifies different messages, allowing them to be grouped and sorted.
  • Message Severity: The message severity describes the nature of the information presented.

Some messages require your attention and resolution before the design can be elaborated, synthesized, or implemented. Some messages are informational only. Informational messages provide details about the design or process, but require no user action.

Table 1. Message Severities
Severity Message
Status Communicates general status of the design processing.
Info General status of the process and feedback regarding design processing.
Warning Design results may be sub-optimal because constraints or specifications may not be applied as intended.
Critical Warning Certain user input or constraints will not be applied, or are outside the best practices, which usually leads to an error later on in the flow. Examine their sources and constraints. Changes are highly recommended.
Error An issue that renders design results unusable and cannot be resolved without user intervention. The design flow stops.

For an example, see the following figure. In this example, a primary clock constraint refers to a port that cannot be found in the design (first warning), so the clock is not created (first critical warning) and any other constraints that refer to this clock fail as well.

Figure 2. Reviewing Errors and Critical Warning