Block automation is the methodology in IP integrator which is used to connect the JESD204C core to a Legacy GT Wizard Transceiver. This is the only supported flow to correctly generate and configure the Legacy Transceiver. To use the new GT Wizard subsystem IP, see GT Wizard Subsystem (For Versal Adaptive SoC only). Block automation is also used to enable transceiver sharing with other JESD cores (TX and RX) and other IPs. The following figure shows the Run Block Automation link in the IP integrator window.
The following figure shows the Block Automation dialog box. In this case, two JESD204C IP cores have been placed onto the IP integrator canvas. The dialog box gives you the option to select one or both cores for the application of Block Automation. There is also the option of Auto, Start_With_New_Quad, or Customized Connections.
If Auto is selected, Block Automation sequentially places the selected cores in the first available suitable GT Quad location. If no existing Versal Adaptive SoC Transceiver GT Quad is available or suitable, then a new GT Quad is created. Block Automation attempts to pack TX and RX cores (and other IP) into as few GT resources as possible. TX and RX cores share PLL resources when they have common settings (line rate, ref clock, and PLL) or use different resources when they do not. This is shown in Example 2.
If Start_With_New_Quad is selected, Block Automation sequentially places the selected cores in new Versal Adaptive SoC Transceiver GT Quad IPs.
If Customized Connections is selected, Block Automation allows you to choose the specific GT locations to use for each IP core lane. This option does not add new GT Quads to the IP integrator canvas, so it requires the GT Quads to be added to the IP integrator canvas prior to running Block Automation. This option gives the maximum flexibility around the wiring of JESD lanes to GT quad locations.