Overview of Segmented Configuration - The industry focuses on faster software boot processes and updates to meet growing demands [2] - Segmented configuration is introduced as a new approach to align solutions with silicon features and boundaries, aiming for faster boot times [10][11] - The primary goal is to boot processors, memory, and OS before loading the PL, offering flexibility in PL configuration [12] Technical Details - Segmented configuration splits the booting process into two phases: PS/boot PDI and PL PDI [11][17] - PS/boot PDI configures the PS, PMC, DDR, CPM, and horizontal NoC [17] - PL PDI configures the user design, vertical NoC, transceivers, I/O, and hardened blocks in the PL [17] - The flow allows dynamic reloading of the PL configuration, enabling on-the-fly changes in the PL domain [29] Implementation and Consistency - Enabling segmented configuration in Vivado leads to a "Zynq MPSoC-like" deployment of the PL [20] - The tool requires identification of necessary NoC connectivity for the initial boot image [21] - Consistency between implementation runs is ensured by locking the NoC solution and exporting/importing it using Tcl commands [30][31] PL Reconfiguration - PL reconfiguration requires pausing activity between the PS and PL and flushing any remaining transactions from the NMU [38] - Users need to unload/load drivers as needed before or after PL reconfiguration, applying device tree overlays [39] - The PL PDI can be fetched by the software application and loaded using high-speed interfaces [40]