System-level bus-based communication architecture exploration using a pseudoparallel algorithm

Lih Yih Chiou, Yi Siou Chen, Chih Hsien Lee

Research output: Contribution to journalArticlepeer-review

1 Citation (Scopus)


Growing complexity in system-on-a-chip (SoC) design demands effective approaches to explore various architectures quickly for the target applications. With the common use of intellectual properties (IPs) in SoC and the large amount of data interchanges among IPs, communication architecture significantly affects the system in terms of power and performance. Therefore, designers should carefully plan the communication architecture to meet the power and performance requirements. While repeatedly performing a power optimization under a performance constraint approach N times seems practical for the power and performance coexploration, the time required to explore such solutions inevitably increases, since there are numerous performance constraints. This paper presents a pseudoparallel method for bus architecture exploration at the system level (PBAES) to speedup the power and performance of coexploration time. PBAES can intelligently search interesting portions of the design space to enhance the efficiency of coexploration, and share the candidate solutions of each to achieve a more rapid overall exploration. The experimental results indicate that PBAES is 1.6× to 14× faster than an approach without the pseudoparallel method with a generated architecture of similar quality.

Original languageEnglish
Pages (from-to)1213-1223
Number of pages11
JournalIEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems
Issue number1
Publication statusPublished - 2009 Jan 1

All Science Journal Classification (ASJC) codes

  • Software
  • Computer Graphics and Computer-Aided Design
  • Electrical and Electronic Engineering


Dive into the research topics of 'System-level bus-based communication architecture exploration using a pseudoparallel algorithm'. Together they form a unique fingerprint.

Cite this