Jump to content
 







Main menu
   


Navigation  



Main page
Contents
Current events
Random article
About Wikipedia
Contact us
Donate
 




Contribute  



Help
Learn to edit
Community portal
Recent changes
Upload file
 








Search  

































Create account

Log in
 









Create account
 Log in
 




Pages for logged out editors learn more  



Contributions
Talk
 



















Contents

   



(Top)
 


1 History  





2 Cause  





3 Testing for SEU sensitivity  





4 SEUs and circuit design  





5 Notable SEU  





6 See also  





7 References  





8 Further reading  














Single-event upset






Deutsch
Español
Français
Simple English
Türkçe
Українська

 

Edit links
 









Article
Talk
 

















Read
Edit
View history
 








Tools
   


Actions  



Read
Edit
View history
 




General  



What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Cite this page
Get shortened URL
Download QR code
Wikidata item
 




Print/export  



Download as PDF
Printable version
 
















Appearance
   

 






From Wikipedia, the free encyclopedia
 

(Redirected from Single-event upsets)

A single-event upset in the flight computers of this Airbus A330 during Qantas Flight 72 on 7 October 2008 is suspected to have resulted in an aircraft upset that nearly ended in a crash after the computers experienced several malfunctions.[1]

Asingle-event upset (SEU), also known as a single-event error (SEE), is a change of state caused by one single ionizing particle (e.g. ions, electrons, photons) striking a sensitive node in a live micro-electronic device, such as in a microprocessor, semiconductor memory, or power transistors. The state change is a result of the free charge created by ionization in or close to an important node of a logic element (e.g. memory "bit"). The error in device output or operation caused as a result of the strike is called an SEU or a soft error.

The SEU itself is not considered permanently damaging to the transistors' or circuits' functionality, unlike the case of single-event latch-up (SEL), single-event gate rupture (SEGR), or single-event burnout (SEB). These are all examples of a general class of radiation effects in electronic devices called single-event effects (SEEs).

History

[edit]

Single-event upsets were first described during above-ground nuclear testing, from 1954 to 1957, when many anomalies were observed in electronic monitoring equipment. Further problems were observed in space electronics during the 1960s, although it was difficult to separate soft failures from other forms of interference. In 1972, a Hughes satellite experienced an upset where the communication with the satellite was lost for 96 seconds and then recaptured. Scientists Dr. Edward C. Smith, Al Holman, and Dr. Dan Binder explained the anomaly as a single-event upset (SEU) and published the first SEU paper in the IEEE Transactions on Nuclear Science journal in 1975.[2] In 1978, the first evidence of soft errors from alpha particles in packaging materials was described by Timothy C. May and M.H. Woods. In 1979, James Ziegler of IBM, along with W. Lanford of Yale, first described the mechanism whereby a sea-level cosmic ray could cause a single-event upset in electronics. 1979 also saw the world's first heavy ion "single-event effects" test at a particle accelerator facility, conducted at Lawrence Berkeley National Laboratory's 88-Inch Cyclotron and Bevatron.[3]

Cause

[edit]

Terrestrial SEUs arise due to cosmic particles colliding with atoms in the atmosphere, creating cascades or showers of neutrons and protons, which in turn may interact with electronic circuits. At deep sub-micron geometries, this affects semiconductor devices in the atmosphere.

In space, high-energy ionizing particles exist as part of the natural background, referred to as galactic cosmic rays (GCRs). Solar particle events and high-energy protons trapped in the Earth's magnetosphere (Van Allen radiation belts) exacerbate this problem. The high energies associated with the phenomenon in the space particle environment generally render increased spacecraft shielding useless in terms of eliminating SEUs and catastrophic single-event phenomena (e.g. destructive latch-up). Secondary atmospheric neutrons generated by cosmic rays can also have sufficiently high energy for producing SEUs in electronics on aircraft flights over the poles or at high altitudes. Trace amounts of radioactive elements in chip packages also lead to SEUs.

Testing for SEU sensitivity

[edit]

The sensitivity of a device to SEU can be empirically estimated by placing a test device in a particle stream at a cyclotron or other particle accelerator facility. This particular test methodology is especially useful for predicting the SER (soft error rate) in known space environments but can be problematic for estimating terrestrial SER from neutrons. In this case, a large number of parts must be evaluated, possibly at different altitudes, to find the actual rate of upset.

Another way to empirically estimate SEU tolerance is to use a chamber shielded from radiation, with a known radiation source, such as Caesium-137.

When testing microprocessors for SEU, the software used to exercise the device must also be evaluated to determine which sections of the device were activated when SEUs occurred.

SEUs and circuit design

[edit]

By definition, SEUs do not destroy the circuits involved, but they can cause errors. In space-based microprocessors, one of the most vulnerable portions is often the 1st and 2nd-level cache memories, because these must be very small and have very high speed, which means that they do not hold much charge. Often these caches are disabled if terrestrial designs are being configured to survive SEUs. Another point of vulnerability is the state machine in the microprocessor control, because of the risk of entering "dead" states (with no exits), however, these circuits must drive the entire processor, so they have relatively large transistors to provide relatively large electric currents and are not as vulnerable as one might think. Another vulnerable processor component is RAM, and more specifically static RAM (SRAM) used in cache memories. SRAM memories are usually designed with transistor sizes close to the minimum allowed by technology to allocate the maximum number of bits per unit area. Small transistor sizes and high bit density make memories one of the most susceptible components to SEUs.[4] To ensure resilience to SEUs, often an error correcting memory is used, together with circuitry to periodically read (leading to correction) or scrub (if reading does not lead to correction) the memory of errors, before the errors overwhelm the error-correcting circuitry.

In digital and analog circuits, a single event may cause one or more voltages pulses (i.e. glitches) to propagate through the circuit, in which case it is referred to as a single-event transient (SET). Since the propagating pulse is not technically a change of "state" as in a memory SEU, one should differentiate between SET and SEU. If a SET propagates through digital circuitry and results in an incorrect value being latched in a sequential logic unit, it is then considered an SEU.

Hardware problems can also occur for related reasons. Under certain circumstances (of both circuit design, process design, and particle properties) a "parasitic" thyristor inherent to CMOS designs can be activated, effectively causing an apparent short-circuit from power to ground. This condition is referred to as latch-up, and in absence of constructional countermeasures, often destroys the device due to thermal runaway. Most manufacturers design to prevent latch-up and test their products to ensure that latch-up does not occur from atmospheric particle strikes. In order to prevent latch-up in space, epitaxial substrates, silicon on insulator (SOI) or silicon on sapphire (SOS) are often used to further reduce or eliminate the susceptibility.

Notable SEU

[edit]

See also

[edit]

References

[edit]
  1. ^ Neutron-Induced Single Event Upset (SEU) FAQ, Microsemi Corporation, retrieved October 7, 2018, The cause has been traced to errors in an onboard computer suspected to have been induced by cosmic rays.
  • ^ Binder, Smith, Holman (1975). "Satellite Anomalies from Galactic Cosmic Rays". IEEE Transactions on Nuclear Science. NS-22, No. 6 (6): 2675–2680. Bibcode:1975ITNS...22.2675B. doi:10.1109/TNS.1975.4328188. S2CID 3032512 – via IEEE Explore.{{cite journal}}: CS1 maint: multiple names: authors list (link)
  • ^ Petersen, Koga, Shoga, Pickel, & Price (2013). "The Single Event Revolution". IEEE Transactions on Nuclear Science. Vol. 60, No.3.
  • ^ Torrens, G.; Alheyasat, A.; Alorda, B.; Barcelo, S.; Segura, J.; Bota, S. A. (2020). "Transistor Width Effect on the Power Supply Voltage Dependence of α-SER in CMOS 6T SRAM". IEEE Transactions on Nuclear Science. 67 (5): 811–817. Bibcode:2020ITNS...67..811T. doi:10.1109/TNS.2020.2983586. ISSN 0018-9499. S2CID 216198845.
  • ^ Ian Johnston (17 February 2017). "Cosmic particles can change elections and cause planes to fall through the sky, scientists warn". Independent. Retrieved 5 September 2018.
  • ^ The Invisible Neutron Threat (2012), Target 4 Flight Path 30L Publications, Los Alamos National Laboratory
  • Further reading

    [edit]
    General SEU
    SEU in programmable logic devices
    SEU in microprocessors
    SEU related masters theses and doctoral dissertations

    Retrieved from "https://en.wikipedia.org/w/index.php?title=Single-event_upset&oldid=1225616355"

    Categories: 
    Digital electronics
    Individual particles
    Hidden categories: 
    CS1 maint: multiple names: authors list
    CS1: long volume value
    Articles with short description
    Short description is different from Wikidata
    Articles lacking in-text citations from August 2009
    All articles lacking in-text citations
     



    This page was last edited on 25 May 2024, at 16:28 (UTC).

    Text is available under the Creative Commons Attribution-ShareAlike License 4.0; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.



    Privacy policy

    About Wikipedia

    Disclaimers

    Contact Wikipedia

    Code of Conduct

    Developers

    Statistics

    Cookie statement

    Mobile view



    Wikimedia Foundation
    Powered by MediaWiki