The transceiver common primitive is required and instantiated for core configurations where QPLL0 or QPLL1 clocking resources are used. Although it is a transceiver primitive, its logical location can be specified during IP customization. Like a helper block, it can be located either within the core or in the example design.
By providing this flexibility, it might be possible to share a single transceiver common between multiple Wizard IP core instances when the following conditions are met:
• You attempt to place the physical transceiver resources of those core instances into a single transceiver Quad, and
• The transceiver common configuration is identical or otherwise safe to share between the two core instances.
Transceiver common sharing between core instances is an advanced use mode and should only be performed when restrictions and limitations are fully understood. See the UltraScale Architecture GTH Transceivers User Guide (UG576) [Ref 1] or UltraScale Architecture GTY Transceivers User Guide (UG578) [Ref 2] for details on the use of the transceiver common primitive.
This Figure
illustrates the case where one or more transceiver common primitives are enabled and located within the core instance, when user-specified. In this case, the
QPLL#OUTCLK
and
QPLL#OUTREFCLK
ports of the transceiver common primitives internally drive the
QPLL#CLK
and
QPLL#REFCLK
ports of the associated transceiver channel primitives, as required (where # is 0 or 1 for
QPLL0
or
QPLL1
, respectively). However, those same signals are also provided as outputs on the core interface as
qpll#outclk_out
and
qpll#outrefclk_out
.
This Figure
illustrates the case where one or more transceiver common primitives are enabled but located within the example design when user-specified. In this case, the
QPLL#OUTCLK
and
QPLL#OUTREFCLK
ports of the transceiver common primitives drive the
qpll#clk_in
and
qpll#refclk_in
input ports on the core interface, which in turn are connected to the
QPLL#CLK
and
QPLL#REFCLK
ports of the associated transceiver channel primitives.
When integrating multiple core instances into your system, the two types of customizations described earlier can be combined to share the transceiver common resources that are present within the instance that contains them. This Figure illustrates how the output ports on the core instance that contains the transceiver common resources can be easily connected to the associated input ports on the core instance which does not. Essentially, the two instances are connected when integrating the cores, excluding the example design wrappers.
See AR#65228 for information on how to share a COMMON block using GTH transceivers.