1. About the Nios® V Processor Lockstep
2. Overview
3. Controlling the Nios® V Processor Lockstep
4. Programming Model
5. Signals, Interfaces, and Build Parameters
6. Using Nios® V Processor Lock Step
A. Document Revision History for the Nios® V Processor: Lockstep Implementation User Guide
B. Appendix
4.4.1. CPUs’ Reset Control Register - DCLSM_CPURC
4.4.2. DCLSM Basic Control Register - DCLSM_CTRL
4.4.3. DCLSM Blind Window Control Register - DCLSM_BWCR
4.4.4. All Alarms’ Prior Alarms’ Fault Injection Register - ERRCTRL_ALL_ALARMS_PRIOR_AFI
4.4.5. INTREQ Configuration Register - ERRCTRL_INTREQ_CONF
4.4.6. Timeout Deadline and Status Register - ERRCTRL_TIMEOUT
4.4.7. Timeout Acknowledgment Register - ERRCTRL_TIMEOUT_ACK
4.4.8. Enable Key fRSmartComp Control Register - ERRCTRL_ENABLE_KEY
4.4.9. Root Fault Injection Control register - ERRCTRL_ROOT_INJ
4.4.10. Alarm Fault Injection Control register - ERRCTRL_ALARM_INJ
4.4.11. Event Mask Configuration register - ERRCTRL_MASKA and ERRCTRL_MASKB
4.4.12. Alarm Routing Configuration register - ERRCTRL_ROUTA and ERRCTRL_ROUTB
4.4.13. Error Controller PGO LOG Reset Control register - ERRCTRL_PGOLOGRST
4.4.14. PGO0 and PGO4 Configuration registers - ERRCTRL_PGO0 and ERRCTRL_PGO4
4.4.15. FN_MODEIN Control Register - ERRCTRL_FNMODEIN
4.4.16. FN_MODEOUT register - ERRCTRL_FNMODEOUT
4.4.17. All Alarms After Fault Injection - ERRCTRL_FNGIALARMS
4.4.18. Error Controller Context Register - ERRCTRL_FNGICTXT4
4.4.19. CMP Mismatch CONTEXT Registers - ERRCTRL_FNGICMPCTXT0 … ERRCTRL_FNGICMPCTXT3
4.4.20. STATISTICS registers: ERRCTRL_FNGISTAT0 and ERRCTRL_FNGISTAT4
4.4.21. State register - ERRCTRL_FNPERIPHGI4
3.2.2.2. Alarm Fault Injection
The Alarm Fault Injection is available on all the alarms. You can activate the Alarm Fault injection using the interfaces in the following table.
Interface | Actions |
---|---|
Configuration Interface | Writing the ERRCTRL_ALARM_INJ register. |
Each bit on the interface corresponds to an alarm. More than one bit can be activated and deactivated at any time. After the Alarm Fault Injection has been used, write the interface to all zeros to deactivate it (and thus remove the generated alarms).
In addition to the sequential INTREQ generation, the Alarm Fault Injection operates as a basic combinatorial function, as outlined in the following table.
Input | Output |
---|---|
|
Combinational update:
|
|
- The Alarm Fault Injection has the following constraints:
- The fRSmartComp does not take any action, and the internal state represented on architectural and micro-architectural registers is not changed, except for the INTREQ primary output, which may be activated. If so, it remains activated until ERRCTRL_INTREQ_CONF[5:0] is set back to 6’b010101 (INTREQ clear action).
- The Alarm Fault injection can be activated at any time and deactivated at any time, without any restart sequence, apart from the INTREQ clear action when INTREQ is activated.