Visible to Intel only — GUID: zcs1676547236534
Ixiasoft
1. About the PHY Lite for Parallel Interfaces IP
2. PHY Lite for Parallel Interfaces Intel® FPGA IP (phylite_ph2) for Intel Agilex® 7 M-Series Devices
3. PHY Lite for Parallel Interfaces Intel® FPGA IP (altera_phylite_s20) for Intel Agilex® 7 F-Series and I-Series Devices
4. PHY Lite for Parallel Interfaces Intel® FPGA IP for Intel® Stratix® 10 Devices
5. PHY Lite for Parallel Interfaces Intel® FPGA IP for Intel® Arria® 10 and Intel® Cyclone® 10 GX Devices
6. PHY Lite for Parallel Interfaces Intel® FPGA IP User Guide Document Archives
7. Document Revision History for the PHY Lite for Parallel Interfaces Intel® FPGA IP User Guide
3.2.1. Intel Agilex® 7 F-Series and I-Series I/O Sub-bank Interconnects
3.2.2. Intel Agilex® 7 F-Series and I-Series Input DQS/Strobe Tree
3.2.3. PHY Lite for Parallel Interfaces Intel® FPGA IP for Intel Agilex® 7 F-Series and I-Series Devices Top Level Interfaces
3.2.4. Dynamic Reconfiguration
3.2.5. I/O Timing
4.5.6.4.1. Timing Closure: Dynamic Reconfiguration
4.5.6.4.2. Timing Closure: Input Strobe Setup and Hold Delay Constraints
4.5.6.4.3. Timing Closure: Output Strobe Setup and Hold Delay Constraints
4.5.6.4.4. Timing Closure: Non Edge-Aligned Input Data
4.5.6.4.5. I/O Timing Violation
4.5.6.4.6. Internal FPGA Path Timing Violation
5.5.6.4.1. Timing Closure: Dynamic Reconfiguration
5.5.6.4.2. Timing Closure: Input Strobe Setup and Hold Delay Constraints
5.5.6.4.3. Timing Closure: Output Strobe Setup and Hold Delay Constraints
5.5.6.4.4. Timing Closure: Non Edge-Aligned Input Data
5.5.6.4.5. I/O Timing Violation
5.5.6.4.6. Internal FPGA Path Timing Violation
Visible to Intel only — GUID: zcs1676547236534
Ixiasoft
2.4.1.2. Pin Placement Restrictions
Follow these guidelines to place the PHY Lite for Parallel Interfaces Intel® FPGA IP group pins:
- Assign each lane to only one group. Each group is either mapped to one lane (x8 mode) or two lanes (x16 mode). When using x16 DQS tree, the first lane should be an even lane.
- If using termination with calibration, reserve pin 38 or 62 for RZQ. RZQ is a 240 ohm resistor that you attach it to a specific pin as an impedance reference to calibrate driving and termination impedances to avoid signal reflection. One RZQ group can support up to two different output terminations and one input termination. RZQ pin cannot be used as data pin.
- No input or bidirectional pins can be placed in the same lane as RZQ.
- Place differential data on two adjacent pins. The first pin should be an even pin. The following shows two differential data pins placed on pins 2 and 12, and occupying 4 pins in total. This example uses an x16 DQS tree since the data pins span over two lanes.
- Differential refclk is not supported in the same lane as PHY Lite IP for the LVSTL I/O standard.
- PHY Lite IP instances in different I/O banks must be connected to different Calibration IPs.
- PHY Lite IP instances in the same I/O bank will be connected to the same Calibration IP, but different Instance ID must be assigned in the IP Parameter Editor to differentiate the base address of the instances (Rev B only).
- In the input-only pins with I/O standard, SSTL-12 or HSTL-12, toggle rddata_en to benefit from On-Die Termination (ODT) rotation. If RX is enabled 100% of the time (if rddata_en is not toggled), only 32 data pins are allowed.
Rotation happens when rddata_en goes low. However, if the receiving data in bursts and the burst sizes are not equal, the maximum imbalance should be 40% to 60% to get credit for the first row in this table.
To support 100% Activity Factor (AF), toggle rddata_en at least 80% of the time with a maximum imbalance of 40% to 60%.
Figure 10. Differential Data Pin Placement
Figure 11. On-Die Termination (ODT) Rotation
Case | Maximum Input Pins |
---|---|
90%<AF≤100% | 32 |
80%<AF≤90% | 38 |
70%<AF≤80% | 48 |
60%<AF≤70% | 58 |
0%<AF≤60% | 96 |