Placement by the Quartus II software may vary with design and device. The following figures show examples of transceiver channel and PCIe Hard IP block locations, supported x1, x2, and x4 bonding configurations, and channel placement guidelines. The Quartus II software automatically places the CMU PLL in a channel different from that of the data channels.
Note: This section shows the supported PCIe channel placement if you use both the top and bottom PCIe Hard IP blocks in the device separately.
The following guidelines apply to all channel placements:
- The CMU PLL requires its own channel and must be placed on channel 1 or channel 4
- The PCIe channels must be contiguous within the transceiver bank
- Lane 0 of the PCIe must be placed on channel 0 or channel 5
In the following figures, channels shaded in blue provide the high-speed serial clock. Channels shaded in gray are data channels.
Figure 69. 12 Transceiver Channels and 2 PCIe HIP Blocks with PCIe x2 and x4 Channel Placement
Figure 70. 12 Transceiver Channels and 2 PCIe HIP Blocks with PCIe x1 Channel Placement
Figure 71. 9 Transceiver Channels and 2 PCIe HIP Blocks with PCIe x2 and x4 Channel Placement The grayed out PCIe Hard IP block is not used in this example
Figure 72. 9 Transceiver Channels and 2 PCIe HIP Blocks with PCIe x1 Channel Placement
Figure 73. 6 Transceiver Channels and 1 PCIe HIP Blocks with PCIe x2 and x4 Channel PlacementThe grayed out PCIe Hard IP block is not used in this example.
Figure 74. 6 Transceiver Channels and 2 PCIe HIP with PCIe x1 Channel PlacementThe grayed out PCIe Hard IP block is not used in this example.
Figure 75. 3 Transceiver Channels and 1 PCIe HIP Blocks with PCIe x1 Channel Placement
For PCIe Gen1 and Gen2, there are restrictions on the achievable x1 and x4 bonding configurations if you intend to use both top and bottom Hard IP blocks in the device.
Table 47. Hard IP Configurations for PCIe Gen1 and Gen2The following table lists the configurations allowed for each Cyclone V device when you use both PCIe Hard IP blocks on the top and bottom transceiver banks. Support will vary by the number of transceiver channels in a device.
Top PCIe Hard IP |
Bottom PCIe Hard IP |
5CGXC4, 5CGXC5, 5CGTD5, 5CSXC5, 5CSTD5 |
5CGXC7, 5CGTD7, 5CSXC6, 5CSTD6 |
5CGXC9, 5CGTD9 |
x1 |
x1 |
Yes |
Yes |
Yes |
x2 |
No |
Yes |
Yes |
x4 |
No |
Yes |
Yes |
x2 |
x1 |
No |
No |
Yes |
x2 |
No |
No |
Yes |
x4 |
No |
No |
Yes |
x4 |
x1 |
No |
No |
Yes |
x2 |
No |
No |
Yes |
x4 |
No |
No |
Yes |
Note: Not all devices listed in the above table have two Hard IP blocks. Refer to the Cyclone V FPGA and SoC FPGA product list for more details.
For full duplex transceiver channels, the following table lists the maximum number of data channels that can be enabled to ensure the channels meet the PCIe Gen2 Transmit Jitter Specification. Follow this recommendation when planning channel placement for PCIe Gen2 using Cyclone V GT or Cyclone V ST device variants.
Table 48. Recommended Channel Placement for Full Duplex Transceiver Channels for PCIe Gen2 CMU channels are not counted as data channels.
Device |
Maximum Channels Utilization |
5CGTD7F672, 5CGTD7F896, 5CGTD9F672, 5CSTD5F896, 5CSTD6F896 |
6 |
5CGTD9F896, 5CGTD9F1152 |
8 |