Quartus® Prime Pro Edition User Guide: Block-Based Design
ID
683247
Date
8/30/2025
Public
1.1. Block-Based Design Terminology
1.2. Block-Based Design Overview
1.3. Design Methodologies Overview
1.4. Design Partitioning
1.5. Design Block Reuse Flows
1.6. Incremental Block-Based Compilation Flow
1.7. Setting-Up Team-Based Designs
1.8. Bottom-Up Design Considerations
1.9. Debugging Block-Based Designs with the Signal Tap Logic Analyzer
1.10. Block-Based Design Flows Revision History
3.1. Preserving the Device Resources
3.2. Fixing the Safety Partitions to Logic Lock Regions
3.3. Exporting and Importing Safety Logic Partitions
3.4. I/O Banks in Safety Partitions
3.5. Safety Region Verification Tool
3.6. Implementing Partitions for the Safety Separation Design Flow Revision History
3.4.1. Preserving GPIO IP and the I/Os in I/O Banks in Safety Partitions
3.4.2. Preserving IOPLL IP in I/O Banks in Safety Partitions
3.4.3. Preserving I/Os (other than GPIO IP I/Os) in I/O Banks in Safety Partitions
3.4.4. Verifying the Preserved I/Os in the Safety Partition
3.4.5. HSIO Bank 3A in a Safety Partition
1.5.1. Reusing Core Partitions
Reusing core partitions involves exporting the core partition from the Developer project as a .qdb, and then reusing the .qdb in a Consumer project.
The Consumer assigns the .qdb to an instance in the Consumer project. In the Consumer project, the Compiler runs stages not already exported with the partition.
Figure 10. Core Partition Reuse Flow
The following steps describe the core partition reuse flow in detail.