Visible to Intel only — GUID: kvm1654684204982
Ixiasoft
7.3.3. Complex Straddled Channels
Typically, in complex configurations and closely packed transceivers, the PHY Arbiter and the TX and RX PHYs split the reconfiguration interface so that each transceiver channel has its own conduit, as shown in the following figure:
This is useful in more complex designs where TX and RX do not align – i.e., TX 0 does not correspond to RX 0. This might be a result of tightly packing RX and TX channels. You can see such an example in the following figure, where separate reconfiguration interfaces and multiple arbiters are required and the channel numbers are not one-to-one. Note the following key points on this setup:
- Arbiter1 has one channel but handles TX0[3] and RX1[0]
- Arbiter2 has two channels: Arbiter2 channel 0 connects TX1 channel 0 and RX1 channel 1
- Arbiter3 is two channels but TX-only
The physical location constraints (i.e., pins) must also correspond to this. In addition, the XCVR_RECONFIG_GROUP constraints must be set in the projects .qsf file or in the assignment editor.
set_instance_assignment -name XCVR_RECONFIG_GROUP 5 -to rx1 [2]
set_instance_assignment -name XCVR_RECONFIG_GROUP 5 -to tx1 [1]
set_instance_assignment -name XCVR_RECONFIG_GROUP 4 -to rx1 [1]
set_instance_assignment -name XCVR_RECONFIG_GROUP 4 -to tx1 [0]
set_instance_assignment -name XCVR_RECONFIG_GROUP 3 -to rx1 [0]
set_instance_assignment -name XCVR_RECONFIG_GROUP 3 -to tx0 [3]
set_instance_assignment -name XCVR_RECONFIG_GROUP 2 -to rx0 [2]
set_instance_assignment -name XCVR_RECONFIG_GROUP 2 -to tx0 [2]
set_instance_assignment -name XCVR_RECONFIG_GROUP 1 -to rx0 [1]
set_instance_assignment -name XCVR_RECONFIG_GROUP 1 -to tx0 [1]
set_instance_assignment -name XCVR_RECONFIG_GROUP 0 -to rx0 [0]
set_instance_assignment -name XCVR_RECONFIG_GROUP 0 -to tx0 [0]