External Memory Interfaces Intel® Cyclone® 10 GX FPGA IP Design Example User Guide

ID 683096
Date 3/29/2021
Public

1.7. Pin Placement for Intel® Cyclone® 10 GX EMIF IP

This topic provides guidelines for pin placement.

Overview

Intel® Cyclone® 10 GX FPGAs have the following structure:
  • Each device contains 2 I/O columns.
  • Each I/O column contains up to 4 I/O banks.
  • Each I/O bank contains 4 lanes.
  • Each lane contains 12 general-purpose I/O (GPIO) pins.

General Pin Guidelines

The following points provide general pin guidelines:

  • Ensure that the pins for a given external memory interface reside within a single I/O column.
  • Interfaces that span multiple banks must meet the following requirements:
    • The banks must be adjacent to one another. For information on adjacent banks, refer to the Intel Cyclone 10 GX External Memory Interfaces IP User Guide.
    • The address and command bank must reside in a center bank to minimize latency. If the memory interface uses an even number of banks, the address and command bank may reside in either of the two center banks.
  • Unused pins can be used as general-purpose I/O pins.
  • All address and command and associated pins must reside within a single bank.
  • Address and command and data pins can share a bank under the following conditions:
    • Address and command and data pins cannot share an I/O lane.
    • Only an unused I/O lane in the address and command bank can be used for data pins.
Table 4.  General Pin Constraints
Signal Type Constraint
Data Strobe All signals belonging to a DQ group must reside in the same I/O lane.
Data Related DQ pins must reside in the same I/O lane. DM/DBI pins must be paired off with a DQ pin for proper operation. For protocols that do not support bidirectional data lines, read signals should be grouped separately from write signals.
Address and Command Address and Command pins must reside in predefined locations within an I/O bank.

Pin Assignments

If you applied a development kit preset during IP generation, all pin assignments for the development kit are automatically generated and can be verified in the .qsf file that is generated with the design example.