1. Intel® MAX® 10 FPGA Configuration Overview 2. Intel® MAX® 10 FPGA Configuration Schemes and Features 3. Intel® MAX® 10 FPGA Configuration Design Guidelines 4. Intel® MAX® 10 FPGA Configuration IP Core Implementation Guides 5. Dual Configuration Intel® FPGA IP Core References 6. Unique Chip ID Intel® FPGA IP Core References 7. Document Revision History for the Intel® MAX® 10 FPGA Configuration User Guide
3.1. Dual-Purpose Configuration Pins 3.2. Configuring Intel® MAX® 10 Devices using JTAG Configuration 3.3. Configuring Intel® MAX® 10 Devices using Internal Configuration 3.4. Implementing ISP Clamp in Intel® Quartus® Prime Software 3.5. Accessing Remote System Upgrade through User Logic 3.6. Error Detection 3.7. Enabling Data Compression 3.8. AES Encryption 3.9. Intel® MAX® 10 JTAG Secure Design Example
184.108.40.206. Remote System Upgrade Flow
Both the application configuration images, image 0 and image 1, are stored in the CFM. The Intel® MAX® 10 device loads either one of the application configuration image from the CFM.
Figure 3. Remote System Upgrade Flow for Intel® MAX® 10 Devices
The remote system upgrade feature detects errors in the following sequence:
- After power-up, the device samples the CONFIG_SEL pin to determine which application configuration image to load. The CONFIG_SEL pin setting can be overwritten by the input register of the remote system upgrade circuitry for the subsequent reconfiguration.
- If an error occurs, the remote system upgrade feature reverts by loading the other application configuration image. These errors cause the remote system upgrade feature to load another application configuration image:
- Internal CRC error
- User watchdog timer time-out
- Once the revert configuration completes and the device is in user mode, you can use the remote system upgrade circuitry to query the cause of error and which application image failed.
- If a second error occurs, the device waits for a reconfiguration source. If the Auto-restart configuration after error is enabled, the device will reconfigure without waiting for any reconfiguration source.
- Reconfiguration is triggered by the following actions:
- Driving the nSTATUS low externally.
- Driving the nCONFIG low externally.
- Driving RU_nCONFIG low.
Did you find the information on this page useful?