2006
DOI: 10.1109/jproc.2006.875789
|View full text |Cite
|
Sign up to set email alerts
|

Asynchronous Techniques for System-on-Chip Design

Abstract: | SoC design will require asynchronous techniques as the large parameter variations across the chip will make it impossible to control delays in clock networks and other global signals efficiently. Initially, SoCs will be globally asynchronous and locally synchronous (GALS). But the complexity of the numerous asynchronous/synchronous interfaces required in a GALS will eventually lead to entirely asynchronous solutions. This paper introduces the main design principles, methods, and building blocks for asynchron… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
156
0

Year Published

2009
2009
2021
2021

Publication Types

Select...
4
2
2

Relationship

0
8

Authors

Journals

citations
Cited by 273 publications
(156 citation statements)
references
References 36 publications
0
156
0
Order By: Relevance
“…A complete data transfer should wait about one or two more clock cycles at each transfer through serialized two flip-flops, and the next data transfer cannot start before the previous data transfer is completed [10,14]. To prevent overheads caused by synchronizing with a two-flop synchronizer for all data bits on wide data paths, an asynchronous handshake protocol bundled with such data paths is typically used [12,15]. A speculative synchronizer [16] and a parallel flop synchronizer [17] to alleviate the inherent latency have been presented, but they have failed to perfectly eliminate the latency.…”
Section: Synchronization Methods In a Heterochronous Environmentmentioning
confidence: 99%
See 1 more Smart Citation
“…A complete data transfer should wait about one or two more clock cycles at each transfer through serialized two flip-flops, and the next data transfer cannot start before the previous data transfer is completed [10,14]. To prevent overheads caused by synchronizing with a two-flop synchronizer for all data bits on wide data paths, an asynchronous handshake protocol bundled with such data paths is typically used [12,15]. A speculative synchronizer [16] and a parallel flop synchronizer [17] to alleviate the inherent latency have been presented, but they have failed to perfectly eliminate the latency.…”
Section: Synchronization Methods In a Heterochronous Environmentmentioning
confidence: 99%
“…Lastly, an asynchronous environment does not have any restrictions of the clock, but an asynchronous design technique needs extra handshaking circuits for its finegrained and localized data synchronization [4,12].…”
Section: Introductionmentioning
confidence: 99%
“…asynchronous, it can seamlessly integrate with the routing fabric without the necessity to cross timing domains as would be the case in a GALS system. Applying an asynchronous design methodology across the whole system eliminates the need for synchronization circuits and design difficulties such as timing closure [26].…”
Section: Design Considerationsmentioning
confidence: 99%
“…The implementation of the read part presents no difficulty. The set/reset latch can be implemented as cross-coupled nor-gates which do not need relative sizing unlike the implementation with cross-coupled inverters (see [4]). Only the wack needs some attention.…”
Section: Implementing Qdi Operatorsmentioning
confidence: 99%
“…A worst-case example, where the adversary path contains just one gate, is the Caltech "Q-element" (see [4]) shown in We analyze the isochronic fork (li, li1, li2). Initially, x 2 is true and ro is false.…”
Section: B a Worst-case Examplementioning
confidence: 99%