Intel® Arria® 10 Transceiver PHY User Guide

Download
ID 683617
Date 3/28/2022
Public
Document Table of Contents

6.14. Dynamic Reconfiguration Interface Merging Across Multiple IP Blocks

Dynamic reconfiguration interfaces may need to be shared between multiple IP blocks to maximize transceiver channel utilization. The Native PHY provides the ability to create channels that are either simplex or duplex instances. However, each physical transceiver channel in Arria® 10 devices is fully duplex.

You can share the reconfiguration interfaces across different IP blocks by manually making a QSF assignment. There are two cases where a dynamic reconfiguration interface might need to be shared between multiple IP blocks:

  • Independent instances of simplex receivers and transmitters in the same physical location
  • Separate CMU PLL and TX channel in the same physical location

The following example shows one Native PHY IP instance of a TX-only channel and another instance of an RX-only channel.

Figure 280. Independent Instances of Simplex TX/RX in the Same Physical Location

The following example shows one Native PHY IP instance of a TX-only channel and an instance of a CMU PLL.

Figure 281. Separate CMU PLL and TX Channel in the Same Physical Location

Rules for Merging Reconfiguration Interfaces Across Multiple IP Cores

To merge reconfiguration interfaces across multiple IP blocks, you must follow these rules:

  1. The control signals for the reconfiguration interfaces of the IP blocks must be driven by the same source. The reconfig_clk, reconfig_reset, reconfig_write, reconfig_read, reconfig_address, and reconfig_writedata ports of the two interfaces to be merged must be driven from the same source.
  2. You must make a QSF assignment to manually specify which two reconfiguration interfaces are to be merged.
    1. Use the XCVR_RECONFIG_GROUP assignment.
    2. Set the To field of the assignment to either the reconfiguration interfaces of the instances to be merged or to the pin names. The reconfiguration interface has the string twentynm_hssi_avmm_if_inst.
    3. Assign the two instances to be merged to the same reconfiguration group.

You cannot merge multiple reconfiguration interfaces when NPDME, optional reconfiguration logic, or embedded reconfiguration streamer are enabled in the Native PHY IP core. 63

You cannot merge the TX and RX channels when the Shared reconfiguration interface parameter is enabled in the Native PHY IP core Parameter Editor. You can merge channels only if the reconfiguration interfaces are independent.

Refer to the following two examples to merge reconfiguration interfaces.

Using reconfiguration interface names

This example shows how to merge a transmit-only Native PHY instance with a receive-only instance using the reconfiguration interface names. These instances are assigned to reconfiguration group 0.

For Native PHY 0—transmit-only instance:

set_instance_assignment -name XCVR_RECONFIG_GROUP 0 -to topdesign:topdesign_inst|<TX only instance name>*twentynm_hssi_avmm_if_inst*

For Native PHY 1—receive-only instance to be merged with Native PHY 0:

set_instance_assignment -name XCVR_RECONFIG_GROUP 0 -to topdesign:topdesign_inst|<RX only instance name>*twentynm_hssi_avmm_if_inst*

Using pin names

This example shows how to merge a transmit-only Native PHY instance with a receive-only instance using pin names. These instances are assigned to reconfiguration group 1.

For Native PHY 0—transmit-only instance:

set_instance_assignment -name XCVR_RECONFIG_GROUP 1 -to tx[0]

For Native PHY 1—receive-only instance to be merged with Native PHY 0:

set_instance_assignment -name XCVR_RECONFIG_GROUP 1 -to rx[0]
63 Please refer to Calibration section on how to calibrate when those features are not available.

Did you find the information on this page useful?

Characters remaining:

Feedback Message