Manually Create Configuration Runs - 2025.1 English - UG909

If you do not use the Abstract Shell or Both option for automatic configuration run creation, you can set this directly for a new set of configuration runs by doing the following:

1. in the Edit Configuration Runs window, click the + icon to create a new parent configuration run that starts with a synthesized design.
2. In the resulting dialog box, set the DFX Mode to ABSTRACT SHELL or BOTH.

Figure 1. Create a New Parent Run

The Auto Create Child Runs option is enabled by default. This option creates as many child implementation runs as necessary to implement all existing RMs (except greybox RMs) not included in the parent configuration.

Create these child runs manually by deselecting the Auto Create option and clicking OK.

Click the + again to create another run. Set the parent to the recently created run. If you set the Parent to the Abstract Shell mode parent implementation, the DFX Mode and Configuration fields are ignored, as this child run must follow the structure of the parent it relates to. Select the new RM Instance to implement within this Abstract Shell. Thiis instance references both the Reconfigurable Partition and the Reconfigurable Module. For designs with multiple Reconfigurable Partitions, many more child runs are necessary compared to a Standard DFX flow, as every RM is implemented independently.

Figure 2. Create a Child Run for the Existing Parent Run

Back in the Configuration Runs page, you can review and edit the RM Instances implemented in any of the runs, and can set any constraints or strategies to be used.

Figure 3. Set the RM Instance for the Child Run

When implementing the design, the parent run is compiled first, then all child runs can be launched in parallel. It is expected that in nearly every case, Abstract Shell runs are faster than an equivalent full configuration child run. With designs containing more than one Reconfigurable Partition, compiling each Reconfigurable Module in parallel further reduces overall compile time.

Using DFX MODE = BOTH

If DFX Mode is set to Both, then child runs of either type can be used. This approach takes slightly longer to compile the parent configuration run as both types of shells must be generated, but then you have full flexibility for the types of configuration runs that follow. For example, if you declare a greybox module for each RP, you can process the entire design using the Abstract Shell process, but then create a greybox child run to use as the initial boot of the device.

1. Create a greybox configuration by adding a new configuration and setting each RP to the predefined greybox setting.
   
   
2. Automatically generate the configuration runs using the Both option as described above. The greybox configuration is ignored.
   
   
3. Click + to create a final configuration run. When the parent is set to the impl_1 run in this case, the child run DFX mode option can be set to either STANDARD or ABSTRACT SHELL. The choice for this option determines which of the final two options are available.
   
   

The final set of Configuration Runs is a mix of Standard DFX and Abstract Shell runs. All child runs can be launched in parallel.