AN 866: Mitigating and Debugging Single Event Upsets in Intel® Quartus® Prime Standard Edition
ID
683869
Date
9/28/2021
Public
1.1. Failure Rates
1.2. Mitigating SEU Effects in Embedded User RAM
1.3. Mitigating SEU Effects in Configuration RAM
1.4. Internal Scrubbing
1.5. SEU Recovery
1.6. Intel® Quartus® Prime Software SEU FIT Reports
1.7. Triple-Module Redundancy
1.8. Evaluating a System's Response to Functional Upsets
1.9. CRAM Error Detection Settings Reference
1.10. Document Revision History
2.3.4.1.2. Specifying an Error List From Prompt Mode
You can operate the Targeted Fault Injection feature interactively by specifying the number of faults to be 0 (-n 0). The Fault Injection Debugger presents prompt mode commands and their descriptions.
Prompt Mode Command | Description |
---|---|
F | Inject a fault |
E | Read the EMR |
S | Scrub errors |
Q | Quit |
In prompt mode, you can issue the F command alone to inject a single fault in a random location in the device. In the following examples using the F command in prompt mode, three errors are injected.
F #3 0x12 0x34 0x56 0x78 * 0x9A 0xBC +
- Error 1 – Single bit error at frame 0x12, bit 0x34
- Error 2 – Uncorrectable error at frame 0x56, bit 0x78 (an * indicates a multi-bit error)
- Error 3 – Double-adjacent error at frame 0x9A, bit 0xBC (a + indicates a double bit error)
F 0x12 0x34 0x56 0x78 *
One (default) error is injected:
Error 1 – Single bit error at frame 0x12, bit 0x34. Locations after the first frame/bit location are ignored.
F #3 0x12 0x34 0x56 0x78 * 0x9A 0xBC + 0xDE 0x00
Three errors are injected:
- Error 1 – Single bit error at frame 0x12, bit 0x34
- Error 2 – Uncorrectable error at frame 0x56, bit 0x78
- Error 3 – Double-adjacent error at frame 0x9A, bit 0xBC
- Locations after the first 3 frame/bit pairs are ignored