1. MAX® 10 FPGA Configuration Overview
2. MAX® 10 FPGA Configuration Schemes and Features
3. MAX® 10 FPGA Configuration Design Guidelines
4. 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 MAX® 10 FPGA Configuration User Guide
3.1. Dual-Purpose Configuration Pins
3.2. Configuring MAX® 10 Devices using JTAG Configuration
3.3. Configuring MAX® 10 Devices using Internal Configuration
3.4. Implementing ISP Clamp in 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. MAX® 10 JTAG Secure Design Example
2.2.1.2.4. Remote System Upgrade Status Registers
| Bits | Name | Description |
|---|---|---|
| 33:30 | msm_cs | The current state of the master state machine (MSM). |
| 29 | ru_wd_en | The current state of the enabled user watchdog timer. The default state is active high. |
| 28:0 | wd_timeout_value | The current, entire 29-bit watchdog time-out value. |
| Bits | Name | Description |
|---|---|---|
| 31 | nconfig | An active high field that describes the reconfiguration sources which caused the MAX® 10 device to leave the previous application configuration. In the event of a tie, the higher bit order takes precedence. For example, if the nconfig and the ru_nconfig triggered at the same time, the nconfig takes precedence over the ru_nconfig. |
| 30 | crcerror | |
| 29 | nstatus | |
| 28 | wdtimer | |
| 27:26 | Reserved | Reserved—set to 0. |
| 25:22 | msm_cs | The state of the MSM when a reconfiguration event occurred. The reconfiguration will cause the device to leave the previous application configuration. |
| 21:0 | Reserved | Reserved—set to 0. |
Related Information