User manual

Table Of Contents
Zynq-7000 AP SoC Technical Reference Manual www.xilinx.com 143
UG585 (v1.11) September 27, 2016
Chapter 5: Interconnect
attempted. Therefore, no GPV access should be attempted if not all of the clocks for the PS-PL AXI
interfaces are connected and operating.
5.7 Loopback
Sometimes it can be advantageous to provide a loopback path from the PS to PL and back. A
loopback path means that there will be an AXI connection between a PS master and PS slave through
the PL, so that designs can manipulate AXI transaction address and/or data in the PL before the data
reaches the intended target in the PS. Such a loopback path typically includes a combinatorial shim
that translates the destination address from an address in the PL to an address in the PS.
It is not considered a loopback path if the AXI transaction from the PS is terminated in the PL, a
separate AXI transaction is created from the PL to the PS, and there is no interlocking dependency
between the two transactions.
In the AP SoC, the only allowed loopback path is from the GM ports to the HP ports within a set of
constraints. Note that HP0 and HP1 share an internal switch, and HP2 and HP3 shares an internal
switch. When there is a loopback path from the GM port to an HP port, there can be no other masters
than the loopback on the HP port being used, as well as the other HP port sharing its internal switch.
For an example, if there is a loopback path from GM1 port to HP1 port, then there can be no other
masters on both HP0 and HP1 ports. Similarly, if there is a loopback path from GM0 port to HP2 port,
then there can be no other masters on both HP2 and HP3 ports. See Figure 5-6.