A novel triple-node-upset-tolerant CMOS latch design using single-node-upset-resilient cells

  • Zhiyuan Song
  • , Aibin Yan
  • , Jie Cui
  • , Zhili Chen
  • , Xuejun Li
  • , Xiaoqing Wen
  • , Chaoping Lai
  • , Zhengfeng Huang
  • , Huaguo Liang

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

35 Scopus citations

Abstract

Nano-scale CMOS circuits are vulnerable to single-event triple-node-upsets (SETUs). This paper proposes the design of a novel CMOS latch to tolerate any SETU using single-node-upset-resilient cells converged at a highly reliable node. The latch makes use of three single-node-upset-resilient cells, each of which mainly consists of triple mutually feeding back 2-input C-elements. These cells have a common converged output node feeding back to the output of the latch, making the latch capable of tolerating any SETU. Simulation results not only confirm the SETU tolerance capability but also show a significant area-power-delay-product reduction of 96.81% for the proposed latch compared with the only existing SETU hardened latch.

Original languageEnglish
Title of host publicationProceedings - 2019 IEEE International Test Conference in Asia, ITC-Asia 2019
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages139-144
Number of pages6
ISBN (Electronic)9781728147185
DOIs
StatePublished - Sep 2019
Externally publishedYes
Event3rd IEEE International Test Conference in Asia, ITC-Asia 2019 - Tokyo, Japan
Duration: 3 Sep 20195 Sep 2019

Publication series

NameProceedings - 2019 IEEE International Test Conference in Asia, ITC-Asia 2019

Conference

Conference3rd IEEE International Test Conference in Asia, ITC-Asia 2019
Country/TerritoryJapan
CityTokyo
Period3/09/195/09/19

Keywords

  • C element
  • Hardened latch
  • Single node upset
  • Triple node upset

Fingerprint

Dive into the research topics of 'A novel triple-node-upset-tolerant CMOS latch design using single-node-upset-resilient cells'. Together they form a unique fingerprint.

Cite this