1. Agilex™ 5 SEU Mitigation Overview
2. Agilex™ 5 CRAM Error Mitigation
3. Secure Device Manager ECC Error and SmartVID Errors Detection
4. Agilex™ 5 SEU Mitigation Implementation Guides
5. IP and Software References
6. Document Revision History for the SEU Mitigation User Guide: Agilex™ 5 FPGAs and SoCs
4.6.1. Launching and Setting Up the Fault Injection Debugger
4.6.2. Configuring Your Device using a Software Object File (.sof)
4.6.3. Constraining Regions for Fault Injection
4.6.4. Injecting Errors to Predefined Safe Locations
4.6.5. Blowing Fuse Bit to Enable Injecting All Error Types
4.6.6. Injecting Errors to Random Locations
4.6.7. Injecting Errors to Specific Locations
4.6.8. Injecting Double Adjacent Errors
4.6.9. Injecting SDM ECC Errors
4.6.10. Analyzing SEU or SDM ECC Errors Using Signal Tap
2.4. SEU Sensitivity Processing
Reconfiguring a running FPGA has a significant impact on the system. Using SEU sensitivity processing, you can identify if the SEU on a CRAM bit is critical to the function of your FPGA design. You can perform SEU sensitivity processing using the Advanced SEU Detection IP core.
In many instances, an SEU impacts CRAM bits that are not critical to the function of the design. For example:
- Configuration bits that are not used because they control unused logic and routing wires
- Portions such as test circuitry that are not utilized in the functional operations of the FPGA
- Non-critical functions that may be logged but do not need to be reprogrammed or reset
When planning recovery from an SEU, you must account for the time required to bring the FPGA to a state consistent with the current state of the system. For example, if an internal state machine is in an illegal state, it may require reset. In addition, the surrounding logic may need to account for this unexpected operation.
Typically, only 40% of all CRAM bits can be used even in the most heavily utilized device. This means that only 40% of SEUs require intervention and you can ignore the rest.