1. Introduction to the Agilex™ 7 Device Design Guidelines
2. System Specification
3. Device Selection
4. Security Considerations
5. Design Entry
6. Board and Software Considerations
7. Design Implementation, Analysis, Optimization, and Verification
8. Debugging
9. Embedded Software Design Guidelines for Agilex™ 7 SoC FPGAs
5.1.1. Firewall Planning
5.1.2. Boot And Configuration Considerations
5.1.3. HPS Clocking and Reset Design Considerations
5.1.4. Reset Configuration
5.1.5. HPS Pin Multiplexing Design Considerations
5.1.6. HPS I/O Settings: Constraints and Drive Strengths
5.1.7. Design Guidelines for HPS Interfaces
5.1.8. Interfacing between the FPGA and HPS
5.1.9. Implementing the Agilex™ 7 HPS Component
7.1. Selecting a Synthesis Tool
7.2. Device Resource Utilization Reports
7.3. Quartus® Prime Messages
7.4. Timing Constraints and Analysis
7.5. Area and Timing Optimization
7.6. Preserving Performance and Reducing Compilation Time
7.7. Designing with Hyperflex®
7.8. Simulation
7.9. Power Analysis
7.10. Power Optimization
7.11. Design Implementation, Analysis, Optimization, and Verification Revision History
9.1. Overview
9.2. Golden Hardware Reference Design (GHRD)
9.3. Define Software Requirements
9.4. Define Software Architecture
9.5. Selecting Software Tools
9.6. Choosing the Bootloader Software
9.7. Selecting an Operating System for Your Application
9.8. Assembling Your Software Development Platform for Linux*
9.9. Assembling your Software Development Platform for Partner OS or RTOS
9.10. Driver Considerations
9.11. Boot And Configuration Considerations
9.12. System Reset Considerations
9.13. Flash Considerations
9.14. Develop Application
9.15. Test and Validate
9.16. Embedded Software Design Guidelines Revision History
6.3.1.1. Unused Pins
| Number | Done? | Checklist Item |
|---|---|---|
| 1 | Specify the reserved state for unused I/O pins. | |
| 2 | Carefully check the pin connections in the Quartus® Prime software-generated .pin file. Do not connect RESERVED pins. |
You can specify the state of unused pins in the Quartus® Prime software to allow flexibility in the board design by choosing one of the five allowable states for Reserve all unused pins on the Unused Pins category in the Device and Pin Options dialog box:
- As inputs tri-stated
- As output driving ground
- As outputs driving an unspecified signal
- As input tri-stated with bus-hold circuitry
- As input tri-stated with weak pull-up
The following list describes some of the settings and their purpose:
- The common setting is to set unused pins As inputs tri-stated with weak pull-up.
- For Agilex™ 7 M-Series devices:
- The unused pins in the HPS bank can only be reserved As inputs tri-stated with weak pull-up.
- The unused pins in the GPIO-B bank can only be reserved As inputs tri-stated without weak pull-up.
- To improve signal integrity, set the unused pins to As output driving ground. Doing this reduces inductance by creating a shorter return path and reduces noise on the neighboring I/Os.
Note: Do not use this approach if this results in many paths causing congestion for signals under the device.
- To reduce power dissipation, set clock pins and other unused I/O pins As inputs tri-stated and tie them to GND.
Connection Guidelines for Unused HPS Block
If you are not using the HPS block in the Agilex™ 7 SoC device, you can follow the guidelines below for HPS specific pins:
| Pin Function | If HPS is unused, connect to: |
|---|---|
VCCL_HPS VCCIO_HPS VCCPLL_HPS VCCPLLDIG_HPS |
If you do not intend to utilize the HPS in the Agilex™ 7 SoC device, you must still provide power to the HPS power supplies. Do not leave the HPS power supplies floating or connect them to GND. For more information, refer to HPS Supply Pins section in the Agilex™ 7 Device Family Pin Connection Guidelines. |
| 48 HPS Dedicated IO | No connect (NC) |
Related Information