Block automation is the methodology in IP integrator which is used to connect the JESD204C core to a Versal Adaptive SoC Transceiver. This is the only supported flow to correctly generate and configure the transceiver. Block automation is also required 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.
When a core has been selected to have Block Automation applied, then the Block Automation control option of Auto, Start_With_New_Quad, or Customized Connections for that core is available.
If Auto is selected, the Block Automation will sequentially place the selected cores in the first available GT Quad locations that are suitable. If no existing Versal Adaptive SoC Transceiver GT Quad is available or suitable, then a new GT Quad will be created. Block Automation will try to pack TX and RX cores (and other IP) into as few GT resources as possible. TX and RX cores will 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, then Block Automation will sequentially place the selected cores in new Versal Adaptive SoC Transceiver GT Quad IPs.
If Customized Connections is selected, then the Block Automation will allow you to choose the specific GT locations to use for each lane on the cores. This option will 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.