2017 IEEE 30th International Conference on Microelectronics (MIEL) 2017
DOI: 10.1109/miel.2017.8190114
|View full text |Cite
|
Sign up to set email alerts
|

SEFI cross-section evaluation by fault injection software approach and hardware detection

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
4
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(4 citation statements)
references
References 12 publications
0
4
0
Order By: Relevance
“…Among all the errors induced by fault injection, single-event functional interrupts at the system level (systems-on-chips -SoC) are undoubtedly the most difficult to characterize and to model because: i) these errors can have multiple causes and ii) during SEFIs the system can behave unpredictably [157]. Usually, SEFIs appear as a spontaneous system reset, a program execution stop (hang-up) or an upset in program execution that can be only repaired by external reset [158]. It is known that SEFIs are caused by upsets in program or data memory (critical bits) or transients and interference on internal lines or peripherical circuitry [158].…”
Section: High-level Description At System Levelmentioning
confidence: 99%
See 1 more Smart Citation
“…Among all the errors induced by fault injection, single-event functional interrupts at the system level (systems-on-chips -SoC) are undoubtedly the most difficult to characterize and to model because: i) these errors can have multiple causes and ii) during SEFIs the system can behave unpredictably [157]. Usually, SEFIs appear as a spontaneous system reset, a program execution stop (hang-up) or an upset in program execution that can be only repaired by external reset [158]. It is known that SEFIs are caused by upsets in program or data memory (critical bits) or transients and interference on internal lines or peripherical circuitry [158].…”
Section: High-level Description At System Levelmentioning
confidence: 99%
“…Usually, SEFIs appear as a spontaneous system reset, a program execution stop (hang-up) or an upset in program execution that can be only repaired by external reset [158]. It is known that SEFIs are caused by upsets in program or data memory (critical bits) or transients and interference on internal lines or peripherical circuitry [158]. Recent studies have also shown that increasing complexity and size of program code, as well as real-time operating system usage, leads to a higher probability of SEFIs that directly affects the reliability of a modern SoCs [159].…”
Section: High-level Description At System Levelmentioning
confidence: 99%
“…The authors of [15] proposed a detailed analysis and hardening architecture based on lockstep synchronization supporting FreeRTOS. The heavy ion irradiation test presented in [16] targets the SRAM and the special purpose registers of an ARM microcontroller to evaluate the impact of the radiation-induced SEU.…”
Section: Related Workmentioning
confidence: 99%
“…Most of them are designed for the verification of radio frequency systems (vii) Electrical Fault Generator. This is also called FIU (Fault Insertion Unit) [17] or FIBO (Fault Insertion Break-Out) [18]. This is an optional module required only for the testing of some UUTs, which allows simulating defects in the wiring such as open circuits (cut wires), ground connections, power connections, and pin-to-pin connections (a short circuit between wires)…”
mentioning
confidence: 99%