3.1. Viewing Basic Project Information 3.2. Intel® Quartus® Prime Project Contents 3.3. Managing Project Settings 3.4. Managing Logic Design Files 3.5. Managing Timing Constraints 3.6. Integrating Other EDA Tools 3.7. Exporting Compilation Results 3.8. Migrating Projects Across Operating Systems 3.9. Archiving Projects 3.10. Command-Line Interface 3.11. Managing Projects Revision History
3.7.1. Exporting a Version-Compatible Compilation Database 3.7.2. Importing a Version-Compatible Compilation Database 3.7.3. Creating a Design Partition 3.7.4. Exporting a Design Partition 3.7.5. Reusing a Design Partition 3.7.6. Viewing Quartus Database File Information 3.7.7. Clearing Compilation Results
4.1. Design Planning 4.2. Create a Design Specification and Test Plan 4.3. Plan for the Target Device 4.4. Plan for Intellectual Property Cores 4.5. Plan for Standard Interfaces 4.6. Plan for Device Programming 4.7. Plan for Device Power Consumption 4.8. Plan for Interface I/O Pins 4.9. Plan for other EDA Tools 4.10. Plan for On-Chip Debugging Tools 4.11. Plan HDL Coding Styles 4.12. Plan for Hierarchical and Team-Based Designs 4.13. Design Planning Revision History
5.1. IP Catalog and Parameter Editor 5.2. Installing and Licensing Intel® FPGA IP Cores 5.3. IP General Settings 5.4. Adding IP to IP Catalog 5.5. Best Practices for Intel® FPGA IP 5.6. Specifying the IP Core Parameters and Options ( Intel® Quartus® Prime Pro Edition) 5.7. Modifying an IP Variation 5.8. Upgrading IP Cores 5.9. Simulating Intel® FPGA IP Cores 5.10. Generating Simulation Files for Platform Designer Systems and IP Variants 5.11. Synthesizing IP Cores in Other EDA Tools 5.12. Instantiating IP Cores in HDL 5.13. Support for the IEEE 1735 Encryption Standard 5.14. Introduction to Intel FPGA IP Cores Revision History
6.2.1. Modify Entity Name Assignments 6.2.2. Resolve Timing Constraint Entity Names 6.2.3. Verify Generated Node Name Assignments 6.2.4. Replace Logic Lock (Standard) Regions 6.2.5. Modify Signal Tap Logic Analyzer Files 6.2.6. Remove References to .qip Files 6.2.7. Remove Unsupported Feature Assignments
6.4.1. Verify Verilog Compilation Unit 6.4.2. Update Entity Auto-Discovery 6.4.3. Ensure Distinct VHDL Namespace for Each Library 6.4.4. Remove Unsupported Parameter Passing 6.4.5. Remove Unsized Constant from WYSIWYG Instantiation 6.4.6. Remove Non-Standard Pragmas 6.4.7. Declare Objects Before Initial Values 6.4.8. Confine SystemVerilog Features to SystemVerilog Files 6.4.9. Avoid Assignment Mixing in Always Blocks 6.4.10. Avoid Unconnected, Non-Existent Ports 6.4.11. Avoid Illegal Parameter Ranges 6.4.12. Update Verilog HDL and VHDL Type Mapping
4.3. Plan for the Target Device
Intel offers a broad portfolio of FPGA and PLD devices. The Intel® device that you select determines factors of performance, density, and board layout. To avoid costly design changes, it is best to carefully consider and determine the target device family early in the design cycle. Intel® FPGA device families differ in cost, size, density, performance, power consumption, packaging, I/O standards, and other factors. Select the device family that best suits your most critical design requirements.
Device Family Selection Guidelines
- Refer to the Product Selector tool on the Intel® website to quickly find and compare the specifications and features of Intel® FPGA devices and development kits.
- Once you identify the target device family, refer to the device family technical documentation for detailed device characteristics. Each device family includes complete documentation, including a datasheet and user guide or handbook. You can also view a summary of each device's resources by selecting a device in the Device dialog box (Assignments > Device)
Figure 35. Device Dialog Box
- Consider whether the device family meets any requirements you have for high-speed transceivers, global or regional clock networks, and the number of phase-locked loops (PLLs)
- Consider the density requirements of your design. Devices with more logic resources and higher I/O counts can implement larger and more complex designs, but at a higher cost. Smaller devices use lower static power. Select a device larger than what your design requires if you may want to add more logic later in the design cycle, or to reserve logic and memory for on-chip debugging.
- Consider requirements for types of dedicated logic blocks, such as memory blocks of different sizes, or digital signal processing (DSP) blocks to implement certain arithmetic functions.
Did you find the information on this page useful?