Freeze the Boundary of this Container
This option prevents changes that modify the boundary of a BDC. The boundary
includes BDC ports, interfaces, port maps, port widths, and parameters. With this
option selected, nothing on the BDC boundary will change. All interfaces will have
the port maps preserved, port widths will not change, and no parameters (with the
clk_domain property) will propagate
from the top-level block design to the BDC and vice-versa.
Enable Dynamic Function eXchange on this container
BDCs enable an IP-centric and project-based environment in IP integrator to create a DFX design in Vivado. A BDC represents the Reconfigurable Partition (RP), Enable Dynamic Function eXchange on this container option converts a BDC into an RP. Once the BDC is converted, the icon on BDC changes to show a DFX label.
Multiple variants as Reconfigurable Modules (RM) can be added to the BDC for the RP instance. It is critical that the port list for each RM for a given RP is identical, even if not all of the ports are used by each RM.
For further information regarding the DFX flow in IP integrator, refer to Vivado Design Suite User Guide: Dynamic Function eXchange (UG909).
Specify BDC variants for synthesis and/or simulationYou can specify different sources for a Block Design Container. Different sources can be viewed as variants of a BDC. Variants of a BDC can differ in the IP blocks within the same defined boundary of the BDC. Once a variant source block design is added, you can select the active variant among these sources for the top-level BD. This action will update the BDC in real-time to show the contents of the new active variant. In addition, you can specify different sources used for BDC synthesis and simulation. Please refer to the Synthesis sources and Simulation sources in Figure 1. Click the + to add the variants of BDC.
An aperture is a range that restricts or bounds the address assignment. Address assignments must fit within apertures on the addressing path. Normally you only specify assignments and not apertures. However, BDC apertures are used in DFX or non-DFX designs to configure the SmartConnect and NoC blocks as if it were an address assignment. Hence BDC apertures cannot overlap (within the same network) or with other assignments. Changing BDC apertures for a design causes a SmartConnect and/or NoC to re-generate.
- Indicates that is not entered by the user and it is auto-calculated to cover the sum of RM address assignments. A BDC auto-aperture does not restrict assignments, but instead it grows or shrinks based on the assignments. Auto apertures are not saved on disk, and are always calculated from assignments. They cannot be edited by the user.
- Indicates that it was entered by the user, and it restricts address assignment. Manual apertures are saved in the BD file.
In non-DFX designs, Auto setting carries the same values for both address assignment (of the active variant) and aperture. If desired, you can still override and specify manual values. In non-DFX designs, the SmartConnect or NoC blocks do not need to cover each variant.
In DFX designs, the tool examines at all RM variants to automatically calculate the aperture values because the address assignments might be different for each RM (variant) in RP BDC.
- RM1 with a 1M assignment
- RM2 with an 8M assignment
S_AXIof the BDC boundary. You can add this aperture manually or automatically with the Vivado tool by examining all assignments. For further information regarding the DFX and BDC apertures, refer to Vivado Design Suite User Guide: Dynamic Function eXchange (UG909).
Addressing Tab of the Block Design Container Customization Dialog Box
- Manual BDC apertures are in black font and are editable.
- Auto BDC apertures are in gray font and are non-editable.
- Click the button
- Select the BDC interface
- Assign the address base and range values