2.8. Hierarchical Partial Reconfiguration - 2026-08-19

Quartus® Prime Pro Edition User Guide
Version
25.1
Product Type
Device Families > Agilex Families > Agilex 5
Device Families > Agilex Families > Agilex 5 > E-Series
Device Families > Agilex Families
Device Families > Agilex Families > Agilex 7
Device Families > Agilex Families > Agilex 3
Device Families > Stratix Families
Device Families > Agilex Families > Agilex 7 > I-Series
Device Families > Cyclone Families > Cyclone 10 > Cyclone 10 GX
Device Families > Cyclone Families > Cyclone 10
Device Families > Agilex Families > Agilex 5 > D-Series
Device Families > Agilex Families > Agilex 7 > M-Series
Development Software and Tools > FPGA Design & Simulation Tools > Quartus Prime Design Software > Pro Edition
Device Families > Arria Families > Arria 10
Device Families > Agilex Families > Agilex 7 > F-Series
Device Families > Stratix Families > Stratix 10
Development Software and Tools > FPGA Design & Simulation Tools > Quartus Prime Design Software
Device Families > Cyclone Families
Device Families > Arria Families
Device Families > Agilex Families > Agilex 3 > C-Series
Resource Type
Documentation > User Guides
ft:sourceName
DITA

Hierarchical partial reconfiguration (HPR) is an extension of partial reconfiguration (PR), where you contain one PR region within another PR region. You can create multiple personas for both the child and parent partitions. You nest the child partitions within their parent partitions. Reconfiguring a parent partition does not impact the operation in the static region, but replaces the child partitions of the parent region with default child partition personas.

The HPR design flow includes the following steps:
  1. Create a base revision for the design and export the static region, as Step 7: Compile the Base Revision and Export the Static Region describes.
  2. Create the implementation revision for each persona, as Step 8: Setup PR Implementation Revisions describes, and export the parent partitions.
  3. Specify the .qdb file partition for the static and parent regions.
  4. Specify the corresponding entity for the parent or child.
When compiling the implementation revision for an HPR design, you must fully floorplan the child partition, similar to planning the PR region of a base revision. Refer to Using Parent QDB Files from Different Compiles .
Note: Hierarchical PR (HPR) designs do not support PR bitstream security verification.
Related Information