Skip to main navigation Skip to search Skip to main content

Is 25 Gb/s on-board signaling viable?

  • Dong G. Kam
  • , Mark B. Ritter
  • , Troy J. Beukema
  • , John F. Bulzacchelli
  • , Petar K. Pepeljugoski
  • , Young H. Kwark
  • , Lei Shan
  • , Xiaoxiong Gu
  • , Christian W. Baks
  • , Richard A. John
  • , Gareth Hougham
  • , Christian Schuster
  • , Renato Rimolo-Donadio
  • , Boping Wu

Research output: Contribution to journalArticlepeer-review

86 Scopus citations

Abstract

What package improvements are required for dense, high-aggregate bandwidth buses running at data rates beyond 10 Gb/s per channel, and when might optical interconnects on the board be required? We present a study of distance and speed limits for electrical on-board module-to-module links with an eye to answering these questions. Hardware-validated models of advanced organic modules and printed circuit boards were used to explore these limits. Simulations of link performance performed with an internal link modeling tool allowed us to explore the effect of equalization and modulation formats at different data rates on link bit error rate and eye opening. Our link models have been validated with active, high-speed differential bus measurements utilizing a 16-channel link chip with programmable equalization and a per-channel data rate of up to 11 Gb/s. Electrical signaling limits were then determined by extrapolating these hardware-correlated models to higher speeds, and these limits were compared to the results of recent work on on-board optical interconnects.

Original languageEnglish
Pages (from-to)328-344
Number of pages17
JournalIEEE Transactions on Advanced Packaging
Volume32
Issue number2
DOIs
StatePublished - 2009
Externally publishedYes

Keywords

  • Channel equalization
  • Electrical signaling limit
  • High-speed bus measurement
  • High-speed serial link
  • Link modeling
  • Multilevel signaling

Fingerprint

Dive into the research topics of 'Is 25 Gb/s on-board signaling viable?'. Together they form a unique fingerprint.

Cite this