Visible to Intel only — GUID: jbr1442882068990
Ixiasoft
Answers to Top FAQs
1. Introduction to Quartus® Prime Pro Edition
2. Planning FPGA Design for RTL Flow
3. Selecting a Starting Point for Your Quartus® Prime Pro Edition Project
4. Working With Intel® FPGA IP Cores
5. Managing Quartus® Prime Projects
A. Next Steps After Getting Started
B. Using the Design Space Explorer II
C. Document Revision History for Quartus® Prime Pro Edition User Guide Getting Started
D. Quartus® Prime Pro Edition User Guides
3.1. Creating a New FPGA Design Project
3.2. Migrating Projects from Other Quartus® Prime Editions to Quartus® Prime Pro Edition
3.3. Migrating Your AMD* Vivado* Project to Quartus® Prime Pro Edition
3.4. Migrating Projects Across Operating Systems
3.5. Migrating Project From One Device to Another
3.6. Related Trainings
3.2.2.1. Modifying Entity Name Assignments
3.2.2.2. Resolving Timing Constraint Entity Names
3.2.2.3. Verifying Generated Node Name Assignments
3.2.2.4. Replace Logic Lock (Standard) Regions
3.2.2.5. Modifying Signal Tap Logic Analyzer Files
3.2.2.6. Removing References to .qip Files
3.2.2.7. Removing Unsupported Feature Assignments
3.2.4.1. Verifying Verilog Compilation Unit
3.2.4.2. Updating Entity Auto-Discovery
3.2.4.3. Ensuring Distinct VHDL Namespace for Each Library
3.2.4.4. Removing Unsupported Parameter Passing
3.2.4.5. Removing Unsized Constant from WYSIWYG Instantiation
3.2.4.6. Removing Non-Standard Pragmas
3.2.4.7. Declaring Objects Before Initial Values
3.2.4.8. Confining SystemVerilog Features to SystemVerilog Files
3.2.4.9. Avoiding Assignment Mixing in Always Blocks
3.2.4.10. Avoiding Unconnected, Non-Existent Ports
3.2.4.11. Avoiding Invalid Parameter Ranges
3.2.4.12. Updating Verilog HDL and VHDL Type Mapping
3.2.4.13. Converting Symbolic BDF Files to Acceptable File Formats
4.1. IP Catalog and Parameter Editor
4.2. Installing and Licensing Intel® FPGA IP Cores
4.3. IP General Settings
4.4. Adding IP to IP Catalog
4.5. Best Practices for Intel® FPGA IP
4.6. Specifying the IP Core Parameters and Options ( Quartus® Prime Pro Edition)
4.7. IP Core Generation Output ( Quartus® Prime Pro Edition)
4.8. Scripting IP Core Generation
4.9. Modifying an IP Variation
4.10. Upgrading IP Cores
4.11. Simulating Intel® FPGA IP Cores
4.12. Generating Simulation Files for Platform Designer Systems and IP Variants
4.13. Synthesizing IP Cores in Other EDA Tools
4.14. Instantiating IP Cores in HDL
4.15. Support for the IEEE 1735 Encryption Standard
4.16. Related Trainings and Resources
5.1. Viewing Basic Project Information
5.2. Managing Project Settings
5.3. Viewing Parameter Settings From the Project Navigator
5.4. Managing Logic Design Files
5.5. Managing Timing Constraints
5.6. Integrating Other EDA Tools
5.7. Exporting Compilation Results
5.8. Archiving Projects
5.9. Command-Line Interface
5.10. Related Trainings
5.7.1. Exporting a Version-Compatible Compilation Database
5.7.2. Importing a Version-Compatible Compilation Database
5.7.3. Creating a Design Partition
5.7.4. Exporting a Design Partition
5.7.5. Reusing a Design Partition
5.7.6. Viewing Quartus Database File Information
5.7.7. Clearing Compilation Results
Visible to Intel only — GUID: jbr1442882068990
Ixiasoft
3.2.4. Upgrading Non-Compliant Design RTL
The Quartus® Prime Pro Edition software introduces a new synthesis engine (quartus_syn executable).
The quartus_syn synthesis enforces stricter industry-standard HDL structures and supports the following enhancements in this release:
- Support for modules with SystemVerilog Interfaces
- Improved support for VHDL2008
- New RAM inference engine infers RAMs from GENERATE statements or array of integers
- Stricter syntax/semantics check for improved compatibility with other EDA tools
Account for these synthesis differences in existing RTL code by ensuring that your design uses standards-compliant VHDL, Verilog HDL, or SystemVerilog. The Compiler generates errors when processing non-compliant RTL. Use the guidelines in this section to modify existing RTL for compatibility with the Quartus® Prime Pro Edition synthesis.
Section Content
Verifying Verilog Compilation Unit
Updating Entity Auto-Discovery
Ensuring Distinct VHDL Namespace for Each Library
Removing Unsupported Parameter Passing
Removing Unsized Constant from WYSIWYG Instantiation
Removing Non-Standard Pragmas
Declaring Objects Before Initial Values
Confining SystemVerilog Features to SystemVerilog Files
Avoiding Assignment Mixing in Always Blocks
Avoiding Unconnected, Non-Existent Ports
Avoiding Invalid Parameter Ranges
Updating Verilog HDL and VHDL Type Mapping
Converting Symbolic BDF Files to Acceptable File Formats
Related Information