This is a rare use case, typically reserved for platform designs where the entirety (or close to it) of the programmable logic is in a dynamic region. NoC configuration details (NMUs, NSUs, connectivity) are free to change to service the needs of each unique RM. The NoC will be completely reprogrammed during dynamic reconfiguration. All NoC endpoints quiesce and all NoC operations cease during reprogramming.
Figure 1. NoC Completely in an RP
Location Constraints for NoC cells
The placement of NoC NMUs and NSUs can be controlled by location constraints. In DFX flow, there are a few rules around location constraints for NoC cells in child implementations. They are:
- For NoC endpoints on static-boundary interface path:
- If RM owns the path, user can change the location of the NoC endpoints inside the reconfigurable module in subsequent child implementations.
- If static region owns the path, user cannot change the location of the NoC endpoints inside the reconfigurable module in subsequent child implementations.
- The NoC endpoints in static region is naturally locked down after initial implementation in DFX flow and cannot be changed in subsequent child implementations.
- For NoC endpoints internal to the reconfigurable module, there is no restriction on NoC location as long as they are inside the reconfigurable pblock range in subsequent child implementations.