1. Stratix® 10 SEU Mitigation Overview
2. Stratix® 10 Mitigation Techniques for CRAM
3. Secure Device Manager ECC Detection
4. Stratix® 10 SEU Mitigation Implementation Guides
5. Advanced SEU Detection IP References
6. Stratix® 10 Fault Injection Debugger References
7. Stratix® 10 SEU Mitigation User Guide Archives
8. Document Revision History for the Stratix® 10 SEU Mitigation User Guide
4.1. Setting the SEU_ERROR Pin
4.2. Setting Up the SEU Mitigation Features
4.3. Enabling Priority Scrubbing
4.4. Performing Hierarchy Tagging
4.5. Programming Sensitivity Map Header File into Memory
4.6. Performing Lookup for Sensitivity Map Header
4.7. Using the Fault Injection Debugger
4.8. Analyzing SEU Errors Using Signal Tap
4.9. Quartus® Prime Software SEU FIT Reports
2.4. Designating the Sensitivity of the Design Hierarchy
In the Quartus® Prime software, you indicate the criticality of each logic block by generating partitions, and assigning a sensitivity ID tag to each partition. The Quartus® Prime software stores this information in a Sensitivity Map Header File (.smh).
When an error occurs during system operation, the system determines the impact of the error by looking up the classification in the .smh file. The system can then take corrective action based on the classification.
Note: You must have a licensed version of Quartus® Prime software to generate .smh files.
To access the .smh file, you must add an instance of the Advanced SEU Detection IP core to your design.