AN 1009: Preserving Nios® II Processor IP for Quartus® Prime Version 24.1 and Newer

Download PDF
ID 839394
Date 3/17/2025
Public
Document Table of Contents
Document Table of Contents x
1. AN 1009: Preserving Nios® II Processor IP for Quartus® Prime Version 24.1 and Newer 2. Preserving Nios® II Processor IP in Quartus® Prime Pro Edition Version 24.1 or Newer 3. Preserving Nios® II Processor IP in Quartus® Prime Standard Edition Version 24.1std or Newer 4. Archiving Projects 5. Document Revision History for AN 1009: Preserving Nios® II Processor IP for Quartus® Prime Version 24.1 and Newer
1. AN 1009: Preserving Nios® II Processor IP for Quartus® Prime Version 24.1 and Newer x
1.1. Overview
2. Preserving Nios® II Processor IP in Quartus® Prime Pro Edition Version 24.1 or Newer x
2.1. Installing and Setting Up the Software 2.2. Preserving the Nios® II Processor in Quartus® Prime Pro Edition
2.1. Installing and Setting Up the Software x
2.1.1. Quartus® Prime Pro Edition and Nios® II Processor Software Build Tools 2.1.2. Configuring the Software
2.1.2. Configuring the Software x
2.1.2.1. Configuring the IP Regeneration Policy 2.1.2.2. Configuring the Output Directory 2.1.2.3. Quartus® Prime Command Line Restrictions
2.2. Preserving the Nios® II Processor in Quartus® Prime Pro Edition x
2.2.1. Using QSYS Approach 2.2.2. Using QIP Approach
2.2.1. Using QSYS Approach x
2.2.1.1. Handling Hardware Component in the Quartus® Prime Pro Edition Project 2.2.1.2. Handling Software Component as Eclipse IDE Project
2.2.1.1. Handling Hardware Component in the Quartus® Prime Pro Edition Project x
2.2.1.1.1. Limitations on the Preserved Projects in Quartus® Prime Pro Edition version 24.1 and Newer
2.2.1.2. Handling Software Component as Eclipse IDE Project x
2.2.1.2.1. Error and Description
2.2.2. Using QIP Approach x
2.2.2.1. Handling Hardware Component in the Quartus® Prime Pro Edition Project 2.2.2.2. Handling Software Component as Eclipse IDE Project
2.2.2.1. Handling Hardware Component in the Quartus® Prime Pro Edition Project x
2.2.2.1.1. Limitations on the Preserved Nios® II Processor in Quartus® Prime Pro Edition version 24.1 and Newer
2.2.2.2. Handling Software Component as Eclipse IDE Project x
2.2.2.2.1. Error and Description
3. Preserving Nios® II Processor IP in Quartus® Prime Standard Edition Version 24.1std or Newer x
3.1. Installing and Setting Up the Software 3.2. Preserving the Nios® II Processor in Quartus® Prime Standard Edition
3.1. Installing and Setting Up the Software x
3.1.1. Quartus® Prime Standard Edition and Nios® II Processor Software Build Tools 3.1.2. Configuring the Software
3.1.2. Configuring the Software x
3.1.2.1. Configuring the IP Regeneration Policy
3.2. Preserving the Nios® II Processor in Quartus® Prime Standard Edition x
3.2.1. Using QIP Approach 3.2.2. Using QSYS Approach
3.2.1. Using QIP Approach x
3.2.1.1. Handling Hardware Component in the Quartus® Prime Standard Edition Project 3.2.1.2. Handling Software Component as Eclipse IDE Project
3.2.1.1. Handling Hardware Component in the Quartus® Prime Standard Edition Project x
3.2.1.1.1. Limitations on the Preserved Nios® II Processor in Quartus® Prime Standard Edition version 24.1std and Newer
3.2.1.2. Handling Software Component as Eclipse IDE Project x
3.2.1.2.1. Error and Description
1. AN 1009: Preserving Nios® II Processor IP for Quartus® Prime Version 24.1 and Newer
2. Preserving Nios® II Processor IP in Quartus® Prime Pro Edition Version 24.1 or Newer
3. Preserving Nios® II Processor IP in Quartus® Prime Standard Edition Version 24.1std or Newer
4. Archiving Projects
5. Document Revision History for AN 1009: Preserving Nios® II Processor IP for Quartus® Prime Version 24.1 and Newer

3.2.2. Using QSYS Approach

Quartus® Prime Standard Edition software does not support the QSYS approach.

According to the Configuring the IP Regeneration Policy, the Quartus® Prime Standard Edition software always regenerates design files during the Analysis and Synthesis stage. Unlike the QIP approach, the QSYS approach cannot bypass this regeneration policy, which leads to compilation errors.

Figure 26. QSYS File in Project Files
Figure 27. Compilation Error from QSYS Approach
Level Two Title