Visible to Intel only — GUID: ztx1491669079478
Ixiasoft
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. Combining Design Block Reuse and Incremental Block-Based Compilation
1.8. Setting-Up Team-Based Designs
1.9. Bottom-Up Design Considerations
1.10. Debugging Block-Based Designs with the Signal Tap Logic Analyzer
1.11. Block-Based Design Flows Revision History
1.12. Intel® Quartus® Prime Pro Edition User Guide: Block-Based Design Document Archive
Visible to Intel only — GUID: ztx1491669079478
Ixiasoft
1.5. Design Block Reuse Flows
Design block reuse allows you to preserve a design partition as an exported .qdb file, and reuse this partition in another project. Reuse of core or root partitions involves partitioning and constraining the block prior to compilation, and then exporting the block for reuse in another project. Effective design block reuse requires planning to ensure that the source code and design hierarchy support the physical partitioning of device resources that these flows require.
- Core partition reuse—allows reuse of synthesized or final snapshots of a core partition. A core partition can include only core resources (LUTs, registers, M20K memory blocks, and DSPs).
- Root partition reuse—allows reuse of a synthesized or final snapshot of a root partition. A root partition includes periphery resources (including I/O, HSSIO, PCIe, PLLs), as well as any associated core resources, while leaving a core partition open for subsequent development.
At a high level, the core and root partition reuse flows are similar. Both flows preserve and reuse a design partition as a .qdb file. The Developer defines, compiles, and preserves the block in the Developer project, and the Consumer reuses the block in one or more Consumer projects.
The following sections describe the core and root partition reuse flows in detail.