2010 Design, Automation &Amp; Test in Europe Conference &Amp; Exhibition (DATE 2010) 2010
DOI: 10.1109/date.2010.5457033
|View full text |Cite
|
Sign up to set email alerts
|

Leveraging application-level requirements in the design of a NoC for a 4G SoC - a case study

Abstract: Abstract-In this paper, we examine the design process of a Network on-Chip (NoC) for a high-end commercial System onChip (SoC) application. We present several design choices and focus on the power optimization of the NoC while achieving the required performance. Our design steps include module mapping and allocation of customized capacities to links. Unlike previous studies, in which point-to-point, per-flow timing constraints were used, we demonstrate the importance of using the application end-to-end travers… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
12
0

Year Published

2011
2011
2017
2017

Publication Types

Select...
3
2
1

Relationship

1
5

Authors

Journals

citations
Cited by 9 publications
(12 citation statements)
references
References 20 publications
0
12
0
Order By: Relevance
“…This is done usually by either dedicated Synchronizer library cells (typically for single bit or small set of signals) or using an ASYNC FIFO (for multiple bits and wide data-buses) [18,16]. Existing NoC topology aproaches such as [7,10,9,12] generate a network topology but do not assign clock-domains (or frequencies) to their constituent routers. This job is left to the designer to do by visual inspection and taking into consideration the clock domains of the various cores (Masters and Slaves) which are known beforehand.…”
Section: Cdc In Network On Chip Interconnectmentioning
confidence: 99%
See 3 more Smart Citations
“…This is done usually by either dedicated Synchronizer library cells (typically for single bit or small set of signals) or using an ASYNC FIFO (for multiple bits and wide data-buses) [18,16]. Existing NoC topology aproaches such as [7,10,9,12] generate a network topology but do not assign clock-domains (or frequencies) to their constituent routers. This job is left to the designer to do by visual inspection and taking into consideration the clock domains of the various cores (Masters and Slaves) which are known beforehand.…”
Section: Cdc In Network On Chip Interconnectmentioning
confidence: 99%
“…While it is feasible for the designer to assign clock-domains (or frequencies) to each router in small designs, this will be increasingly harder as SoC sizes increase. For example the 4G Modem SoC presented in [10] consists of 16 Masters and 18 Slaves with between 4 and 10 routers, even the presence of 3 or 4 clock domains would leave the designer with a large set of possible router frequency assignments. More importantly by optimizing for CDC during topology generation, the tools can generate a topology that still satisfies the performance/latency requirements, optimizes for area/power but also has a lower number of CDCs.…”
Section: Cdc In Network On Chip Interconnectmentioning
confidence: 99%
See 2 more Smart Citations
“…In addition to FPGAs, complete NoC-based SoC ASICs are presented in [7,17,72] together with a post-layout evaluation. However, neither of the works evaluate the scalability and instead focus on a single design point.…”
Section: Functional Scalabilitymentioning
confidence: 99%