AN 738: Intel® Arria® 10 Device Design Guidelines

Download PDF
ID 683555
Date 6/30/2017
Public
Document Table of Contents
Document Table of Contents x
1. AN 738: Intel® Arria® 10 Device Design Guidelines
1. AN 738: Intel® Arria® 10 Device Design Guidelines x
1.1. System Specification 1.2. Device Selection 1.3. Early System and Board Planning 1.4. Pin Connection Considerations for Board Design 1.5. I/O and Clock Planning 1.6. Design Entry 1.7. Design Implementation, Analysis, Optimization, and Verification 1.8. Conclusion 1.9. Document Revision History 1.10. Design Checklist 1.11. Appendix: Arria® 10 Transceiver Design Guidelines
1.1. System Specification x
1.1.1. Design Specifications 1.1.2. IP Selection 1.1.3. Qsys
1.2. Device Selection x
1.2.1. Device Family Variant and High-Speed Transceivers 1.2.2. Logic, Memory, and Multiplier Density 1.2.3. I/O Pin Count, LVDS Channels, and Package Offering 1.2.4. PLLs and Clock Routing 1.2.5. Speed Grade 1.2.6. Vertical Device Migration
1.3. Early System and Board Planning x
1.3.1. Early Power Estimation 1.3.2. Temperature Sensing for Thermal Management 1.3.3. Voltage Sensor 1.3.4. Planning for Device Configuration 1.3.5. Planning for On-Chip Debugging
1.3.4. Planning for Device Configuration x
1.3.4.1. Configuration Scheme Selection 1.3.4.2. Configuration Features 1.3.4.3. Quartus Prime Configuration Settings
1.3.4.1. Configuration Scheme Selection x
1.3.4.1.1. Serial Configuration Devices 1.3.4.1.2. Download Cables 1.3.4.1.3. Using the Parallel Flash Loader Megafunction with MAX II Devices
1.3.4.2. Configuration Features x
1.3.4.2.1. Data Compression 1.3.4.2.2. Design Security Using Configuration Bitstream Encryption 1.3.4.2.3. Remote System Upgrades 1.3.4.2.4. SEU Mitigation and CRC Error Checks
1.3.5. Planning for On-Chip Debugging x
1.3.5.1. On-Chip Debugging Tools 1.3.5.2. Planning Guidelines for Debugging Tools
1.4. Pin Connection Considerations for Board Design x
1.4.1. Device Power-Up 1.4.2. Power Pin Connections and Power Supplies 1.4.3. Configuration Pin Connections 1.4.4. Board-Related Quartus Prime Settings 1.4.5. Signal Integrity Considerations 1.4.6. Board-Level Simulation and Advanced I/O Timing Analysis
1.4.2. Power Pin Connections and Power Supplies x
1.4.2.1. Decoupling Capacitors 1.4.2.2. PLL and Transceiver Board Design Guidelines
1.4.3. Configuration Pin Connections x
1.4.3.1. DCLK and TCK Signal Integrity 1.4.3.2. JTAG Pins 1.4.3.3. MSEL Configuration Mode Pins 1.4.3.4. Other Configuration Pins
1.4.4. Board-Related Quartus Prime Settings x
1.4.4.1. Device-Wide Output Enable Pin 1.4.4.2. Unused Pins
1.4.5. Signal Integrity Considerations x
1.4.5.1. High-Speed Board Design 1.4.5.2. Voltage Reference Pins 1.4.5.3. Simultaneous Switching Noise 1.4.5.4. I/O Termination
1.5. I/O and Clock Planning x
1.5.1. Making FPGA Pin Assignments 1.5.2. Early Pin Planning and I/O Assignment Analysis 1.5.3. I/O Features and Pin Connections 1.5.4. Clock and PLL Selection 1.5.5. PLL Feature Guidelines 1.5.6. Clock Control Block 1.5.7. I/O Simultaneous Switching Noise
1.5.3. I/O Features and Pin Connections x
1.5.3.1. I/O Signaling Type 1.5.3.2. Selectable I/O Standards and Flexible I/O Banks 1.5.3.3. Memory Interfaces 1.5.3.4. Dual-Purpose and Special Pin Connections 1.5.3.5. Arria® 10 I/O Features
1.5.5. PLL Feature Guidelines x
1.5.5.1. Clock Feedback Mode 1.5.5.2. Clock Outputs
1.6. Design Entry x
1.6.1. Design Recommendations 1.6.2. Using IP Cores 1.6.3. Reconfiguration 1.6.4. Recommended HDL Coding Styles 1.6.5. Register Power-Up Levels and Control Signals 1.6.6. Planning for Hierarchical and Team-Based Design
1.6.3. Reconfiguration x
1.6.3.1. Dynamic Reconfiguration 1.6.3.2. Partial Reconfiguration
1.6.6. Planning for Hierarchical and Team-Based Design x
1.6.6.1. Planning Design Partitions 1.6.6.2. Planning in Bottom-Up and Team-Based Flows 1.6.6.3. Creating a Design Floorplan
1.7. Design Implementation, Analysis, Optimization, and Verification x
1.7.1. Selecting a Synthesis Tool 1.7.2. Device Resource Utilization Reports 1.7.3. Quartus Prime Messages 1.7.4. Timing Constraints and Analysis 1.7.5. Area and Timing Optimization 1.7.6. Preserving Performance and Reducing Compilation Time 1.7.7. Simulation 1.7.8. Formal Verification 1.7.9. Power Analysis 1.7.10. Power Optimization
1.7.4. Timing Constraints and Analysis x
1.7.4.1. Recommended Timing Optimization and Analysis Assignments
1.7.10. Power Optimization x
1.7.10.1. Device and Design Power Optimization Techniques 1.7.10.2. Quartus Prime Power Optimization Techniques
1.7.10.1. Device and Design Power Optimization Techniques x
1.7.10.1.1. Clock Power Management 1.7.10.1.2. Memory Power Reduction 1.7.10.1.3. I/O Power Guidelines
1.7.10.2. Quartus Prime Power Optimization Techniques x
1.7.10.2.1. Power Optimization Advisor
1.11. Appendix: Arria® 10 Transceiver Design Guidelines x
1.11.1. Transceiver PHY Architecture Overview 1.11.2. Transceiver Bank Architecture 1.11.3. PHY Layer Transceiver Components 1.11.4. Transceiver Phase-Locked Loops 1.11.5. Clock Generation Block (CGB) 1.11.6. Calibration 1.11.7. Transceiver Design Flow
1.11.3. PHY Layer Transceiver Components x
1.11.3.1. The GX Transceiver Channel 1.11.3.2. The GT Transceiver Channel
1.11.4. Transceiver Phase-Locked Loops x
1.11.4.1. Advanced Transmit (ATX) PLL 1.11.4.2. Fractional PLL (fPLL) 1.11.4.3. Channel PLL (CMU/CDR PLL)
1. AN 738: Intel® Arria® 10 Device Design Guidelines

1.5.4. Clock and PLL Selection

Table 42.  Clock and PLL Selection Checklist
Number Done? Checklist Item
1   Use the correct dedicated clock pins and routing signals for clock and global control signals.
2   Use the device PLLs for clock management.
3   Analyze input and output routing connections for each PLL and clock pin. Ensure PLL inputs come from the dedicated clock pins or from another PLL.

The first stage in planning your clocking scheme is to determine your system clock requirements. Understand your device’s available clock resources and correspondingly plan the design clocking scheme. Consider your requirements for timing performance, and how much logic is driven by a particular clock.

Arria® 10 devices provide dedicated low-skew and high fan-out routing networks. They are organized in a hierarchical structure that provides up to 417 unique clock domains within the device (16 GCLKs + 92 RCLKs + 309 PCLKs). There are up to 28 fractional PLLs per device and up to 18 independently-programmable outputs per PLL. You can use 16 differential dedicated GCLK input pins or 48 to 56 single-ended clock inputs.

The dedicated clock pins drive the clock network directly, ensuring lower skew than other I/O pins. Use the dedicated routing network to have a predictable delay with less skew for high fan-out signals. You can also use the clock pins and clock network to drive control signals like asynchronous reset.

Connect clock inputs to specific PLLs to drive specific low-skew routing networks. Analyze the global resource availability for each PLL and the PLL availability for each clock input pin.

Use the following descriptions to help determine which clock networks are appropriate for the clock signals in your design:

  • The GCLK networks can drive throughout the entire device, serving as low-skew clock sources for device logic. This clock region has the maximum delay compared to other clock regions but allows the signal to reach everywhere within the device. This option is good for routing global reset/clear signals or routing clocks throughout the device.
  • The RCLK networks only pertain to the quadrant they drive into and provide the lowest clock delay and skew for logic contained within a single device quadrant.
  • IOEs and internal logic can also drive GCLKs and RCLKs to create internally generated GCLKs or RCLKs and other high fan-out control signals; for example, synchronous or asynchronous clears and clock enables.
  • PLLs cannot be driven by internally-generated GCLKs or RCLKs. The input clock to the PLL must come from dedicated clock input pins or from another pin/PLL-fed GCLK or RCLK.
  • PCLK networks are a collection of individual clock networks driven from the periphery of the Arria® 10 device. Clock outputs from the DPA block, PLD-transceiver interface, I/O pins, and internal logic can drive the PCLK networks. These PCLKs have higher skew compared to GCLK and RCLK networks and can be used instead of general purpose routing to drive signals into and out of the Arria® 10 device.

If your system requires more clock or control signals than are available in the target device, consider cases where the dedicated clock resource could be spared, particularly low fan-out and low-frequency signals where clock delay and clock skew do not have a significant impact on the design performance. Use the Global Signal assignment in the Quartus® Prime Assignment Editor to select the type of global routing, or set the assignment to Off to specify that the signal should not use any global routing resources.

Related Information
Level Two Title