When Bridge IP is added to IP integrator canvas, a green ribbon appears at the
top. It has a link for Block Automation, which automates some of the datapath, clocking,
and reset connections. After configuring the Bridge IP and clicking Block Automation,
the Block Automation GUI opens up. By selecting Auto, you let the Block Automation 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. By selecting Start_With_New_Quad, the Block Automation instantiates the New GT Quad
and makes the data path, clocks, and reset connections. On a fresh IP integrator canvas,
both Auto and
Start_With_New_Quad options behave
similarly. It instantiates multiple gt_quad_base based
on the number of lanes configured in gt_bridge_ip and
makes data path, clocks and, reset connections.
By selecting Customized_Connections, GUI expands showing all available valid lanes already in the system. You can connect the 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. You must note that, in the Customized_Connections option, the new GT Quad base IP is not instantiated automatically if lanes are not available. You have to manually add the GT quad base IP in the canvas before clicking Customized_Connections. For example, in an empty canvas, you have to manually instantiate both the Bridge IP and the GT Quad base IP for Customized_Connections to take effect. Most of the GT parent IPs would have migrated to support this. Refer respective GT parent IP PGs for further details on the usage of this advanced feature. Customized_Connections GUI options are shown in the following figure.
