Partial reconfiguration is supported through the following configuration interfaces:
The JTAG interface is dedicated.
If PERSIST is set and the mode is set to slave, the interface remains active. Load the partial reconfiguration bitstream as a typical flow.
If PERSIST is set and the mode is set to master, CCLK runs continuously. This makes controlling the data flow more involved. It is recommended that you use the ICAP interface instead of PERSIST in the master SelectMAP mode.
If PERSIST is not set, you can forward the data to ICAP. You can also use the STARTUP block to drive the CCLK out. See the ICAP section below for more information. Note that you must account for the clock and the data alignment.
BPI supports master mode only. This results in the CCLK being driven and continuous address incrementation. It is recommended that you avoid using PERSIST and that you use the ICAP interface instead to forward the data through the BPI data port.
SPI supports master mode only. This results in the CCLK being driven and no further read commands are issued after configuration. It is recommended that you avoid using PERSIST and that you use ICAP interface instead to forward the data through the BPI data port.
ICAP is the internal configuration access port. It behaves identically to the slave SelectMAP interface with the exception that SelectMAP has a bi-directional data port while ICAP has dedicated data inputs and outputs. To use ICAP, do not set PERSIST during the bitstream generation process.