FinFET SRAM optimization with fin thickness and surface orientation

Mingu Kang, S. C. Song, S. H. Woo, H. K. Park, M. H. Abu-Rahma, L. Ge, B. M. Han, J. Wang, G. Yeap, S. O. Jung

Research output: Contribution to journalArticlepeer-review

35 Citations (Scopus)

Abstract

In this paper, the design space, including fin thickness (Tfin), fin height (Hfin), fin ratio of bit-cell transistors, and surface orientation, is researched to optimize the stability, leakage current, array dynamic energy, and read/write delay of the FinFET SRAM under layout area constraints. The simulation results, which consider the variations of both Tfin and threshold voltage (Vth), show that most FinFET SRAM configurations achieve a superior read/write noise margin when compared with planar SRAMs. However, when two fins are used as pass gate transistors (PG) in FinFET SRAMs, enormous array dynamic energy is required due to the increased effective gate and drain capacitance. On the other hand, a FinFET SRAM with a one-fin PG in the (110) plane shows a smaller write noise margin than the planar SRAM. Thus, the one-fin PG in the (100) plane is suitable for FinFET SRAM design. The one-fin PG FinFET SRAM with Tfin = 10nm and H fin = 40nm in the (100) plane achieves a three times larger noise margin when compared with the planar SRAM and consumes a 17% smaller bit-line toggling array energy at a cost of a 22% larger word-line toggling energy. It also achieves a 2.3 times smaller read delay and a 30% smaller write delay when compared with the planar SRAM.

Original languageEnglish
Article number5559393
Pages (from-to)2785-2793
Number of pages9
JournalIEEE Transactions on Electron Devices
Volume57
Issue number11
DOIs
Publication statusPublished - 2010 Nov

All Science Journal Classification (ASJC) codes

  • Electronic, Optical and Magnetic Materials
  • Electrical and Electronic Engineering

Fingerprint

Dive into the research topics of 'FinFET SRAM optimization with fin thickness and surface orientation'. Together they form a unique fingerprint.

Cite this