Setting up Block Automation - 2.0 English

Versal Adaptive SoC GT Controller for DisplayPort and SDI LogiCORE IP Product Guide (PG398)

Document ID
Release Date
2.0 English
Follow these steps to set up block automation:
  1. Click Run Block Automation, as shown in the following figure. Block automation connects the GT Controller Bridge to TX and RX data paths of the Subsystem IP and GT Quad. (A new GT Wizard quad base is launched if it cannot pack the Parent IP with existing GT Quad resources).

  2. Use the Run Block Automation dialog box to specify the basic options that the GT Controller Bridge needs. (Auto is selected by default).

    • Select Auto if you want the Block Automation to choose the optimal usage of the GT Quad resources. The tool's decision is based on its knowledge of available clocking resources and REFCLK and PLL sharing rules.
    • Select Start_With_New_Quad if you want the Block Automation to instantiate the New GT Quad and make the data path, clocks, and reset connections.
      Note: On a fresh IP integrator canvas, both Auto and Start_With_New_Quad options behave similarly.
    • Select Customized_Connections if you want to see all available valid lanes already in the system. You can connect the GT Controller Bridge IP's GT interfaces to any lanes of the GT Quad base IP by selecting the appropriate GT Quad and Lane selection options in the GUI.
      Note: In the Customized_Connections option, a new GT Quad base IP is not instantiated automatically if lanes are unavailable. You must manually add the GT quad base IP in the canvas before clicking Customized_Connections. For example, on an empty canvas, you must manually instantiate both the GT Controller Bridge IP and the GT Quad base IP for Customized_Connections to take effect. Customized_Connections GUI options are shown in following figure:

  3. Click OK. The Block Automation feature then automatically creates a basic system as shown in the figure below. This example shows a basic system that consists of a UHDSDI TX/RX Subsystem IP, a Versal GT controller Bridge IP for SDI, the clock buffer, and the GT Quad for Versal adaptive SoC devices. Both clocks get connected to a clock source. (Because the design does not connect to any external I/O at this point, the IP integrator provides the Connection Automation feature as shown by the highlighted area in the figure).

  4. (Optional) Click Run Connection Automation to get assistance in hooking interfaces and/or ports to external I/O ports. The following figure shows a list of the ports/interfaces that can use the Connection Automation feature.

  5. Click OK. Both the clocks as shown in step 3 above are then connected to a clock source.
  • Rate Grouping and PICXO are not supported in Block Automation.
  • Duplex mode instantiates both TX and RX subsystem IPs while running the Block Automation but the GT Controller Bridge IP works as Simplex RX and Simplex TX.
Important: Once Block Automation is run, the connection to the ports connected by the Block Automation process should not be changed. If the connections are changed, then the Block Automation process is considered null and void.