Visible to Intel only — GUID: hco1416490865242
Ixiasoft
Visible to Intel only — GUID: hco1416490865242
Ixiasoft
8.3.1.6.1. General Guidelines
If you are using the hard memory controller, you should employ the relative pin locations defined in the <variation_name>/altera_emif_arch_nf_version number/<synth|sim>/<variation_name>_altera_emif_arch_nf_version number_<unique ID>_readme.txt file, which is generated with your IP.
- The number of I/O pins in an I/O bank and the availability of I/O banks varies across device packages. Each memory interface requires at least one I/O bank with 48 I/O pins for the address and command pins. I/O banks with less than 48 I/O pins can support data pins only. For details about the I/O banks available for each device package and the locations of consecutive I/O banks, refer to Memory Interfaces Support in Intel Arria 10 Device Packages and related links, in the Intel® Arria® 10 Core Fabric and General Purpose I/Os Handbook.
- EMIF IP pin-out requirements for the Intel® Arria® 10 Hard Processor Subsystem (HPS) are more restrictive than for a non-HPS memory interface. The HPS EMIF IP defines a fixed pin-out in the Intel® Quartus® Prime IP file (.qip), based on the IP configuration. When targeting Intel® Arria® 10 HPS, you do not need to make location assignments for external memory interface pins. To obtain the HPS-specific external memory interface pin-out, compile the interface in the Intel® Quartus® Prime software. Alternatively, consult the device handbook or the device pin-out files. For information on how you can customize the HPS EMIF pin-out, refer to Restrictions on I/O Bank Usage for Intel® Arria® 10 EMIF IP with HPS.
- Ping Pong PHY, PHY only, RLDRAMx , QDRx and LPDDR3 are not supported with HPS.
Observe the following general guidelines when placing pins for your Intel® Arria® 10 external memory interface:
- Ensure that the pins of a single external memory interface reside within a single I/O column.
- An external memory interface can occupy one or more banks in the same I/O column. When an interface must occupy multiple banks, ensure that those banks are adjacent to one another.
- Any pin in the same bank that is not used by an external memory interface is available for use as a general purpose I/O of compatible voltage and termination settings.
- All address and command pins and their associated clock pins (CK and CK#) must reside within a single bank. The bank containing the address and command pins is identified as the address and command bank.
- To minimize latency, when the interface uses more than two banks, you must select the center bank of the interface as the address and command bank.
- The address and command pins and their associated clock pins in the address and command bank must follow a fixed pin-out scheme, as defined in the Intel® Arria® 10 External Memory Interface Pin Information File, which is available on www.altera.com.
You do not have to place every address and command pin manually. If you assign the location for one address and command pin, the Fitter automatically places the remaining address and command pins.
Note: The pin-out scheme is a hardware requirement that you must follow, and can vary according to the topology of the memory device. Some schemes require three lanes to implement address and command pins, while others require four lanes. To determine which scheme to follow, refer to the messages window during parameterization of your IP, or to the <variation_name>/altera_emif_arch_nf_<version>/<synth|sim>/<variation_name>_altera_emif_arch_nf_<version>_<unique ID>_readme.txt file after you have generated your IP. - An unused I/O lane in the address and command bank can serve to implement a data group, such as a x8 DQS group. The data group must be from the same controller as the address and command signals.
- An I/O lane must not be used by both address and command pins and data pins.
- Place read data groups according to the DQS grouping in t