1.3.3. Parameter Settings
|Which operation mode will you be using?||REMOTE||Specifies the configuration mode.|
|Which configuration device will you be using?||
||Choose the configuration device you are using.|
|Add support for writing configuration parameters||—||Enable this if you need to write configuration parameters.|
|Add support for Avalon Interface 1||—||Enable this if you are using Avalon interface.|
|Enable reconfig POF checking||—||Allows you to enable .pof checking, which allows the remote update block to verify the existence of an application configuration image before the image is loaded. When you turn on this parameter, the Remote Update Intel® FPGA IP core checks the .pof and sends the reconfig signal. This option is disabled by default.|
The POF checking feature detects and verifies the existence of an application configuration image before the image is loaded. Loading an invalid application configuration image may lead to unexpected behavior of the FPGA including system failure. Examples of invalid application configuration images are:
- A partially programmed application image
- A blank application image
- An application image assigned with a wrong start address
- If the header section is invalid, the Remote Update Intel® FPGA IP does not trigger reconfiguration and asserts pof_error signal.
- If the header section is valid, but the corruption appears in a different part of the image, the IP triggers application image reconfiguration. The reconfiguration fails due to a CRC mismatch and the nSTATUS signal asserts. The IP then loads the factory image.
Did you find the information on this page useful?