United Business Media EE Times


Search

HOMEMARKET INTELLIGENCE UNITFORUMSDESIGNNEW PRODUCTSCAREERSBLOGSCONTACTEVENTSSIGN UP!RSSMost Popular contentTrusted Sources

 


Hooking up the blocks
Print this article Email this article Reprints RSS Digital Edition

EE Times


Ron WilsonSystem-level IC design keeps presenting interesting challenges. Mostly, these have been at the chip design level: issues about fracturing large blocks to feed them into recalcitrant synthesis tools, keeping track of all the interconnect, achieving timing closure and volumes of problems with verification. But sometimes the challenges of system-on-chip design show up back at the system-design level.

One exception to that comfortable generalization arrives with the block-oriented, hierarchical design style that is now nearly synonymous with SoC design. If you partition the design into functional blocks-or if your acquisition of the major blocks from others partitions it for you-you are left with the problem of how to interconnect them.

The obvious answer, the one that has been right since the first transistors were getting wired together to make the first quad-NAND gates, is point-to-point wiring. Each block has its input ports and output ports, and by the time you have done even a coarse trial routing of a block you know about where those pins have to be. So you put the blocks down on the chip and hook 'em up, maybe about the same time that you put in the global clock trees and power metal.

Naturally something this simple couldn't last. A couple of problems present themselves right away. No matter how careful you are at partitioning, you are likely to end up with a bunch of runs between blocks lying in critical timing paths. That means that your timing closure may depend on your ability to control the length and parasitic capacitance of runs that can take off and wander halfway across the die. Not good.

Even if your methodology can insure you against timing-closure problems caused by interblock runs, there are more structural issues. Most SoC designs are CPU-centric, like the board-level designs they are superceding. That means the interconnect between blocks is already defined for you, in the form of a microprocessor bus, a peripheral bus or perhaps a derivative bus intended for on-chip use, such as Amba. But the world of on-chip interconnect is vastly different from the world of board-level buses.

Alternatives to on-chip buses are starting to get a lot of attention. One possibility now being seen in the communications world: crossbar switches. Using switches in place of a bus not only increases the maximum bandwidth but can make the interconnect much more regular and predictable. Other ideas are being imported from the supercomputing world. Rings, arrays and octagons have been suggested, and sooner or later someone is going to try a hypercube.





The views and opinions expressed in this column are strictly those of the author and should not be taken as an editorial position of EE Times or any of its other editors, publications or Web sites.


  Free Subscription to EE Times
First Name Last Name
Company Name Title
Email address
  Click here for your Free Subscription to EETimes Europe
 
CAREER CENTER
Looking for a new job?
SEARCH JOBS
SPONSOR

RECENT JOB POSTINGS
CAREER NEWS
SRC Expands R&D Centers
The Semiconductor Research Corp has added a new center to its university R&D efforts.

For more great jobs, career related news, features and services, please visit EETimes' Career Center.


All White Papers »   

 
Education and
Learning


Learn Now:












Home | About | Editorial Calendar | Feedback | Subscriptions | Newsletter | Media Kit | Contact | Reprints|  RSS|   Digital|  Mobile
Network Websites
International
Network Features




All materials on this site Copyright © 2009 TechInsights, a Division of United Business Media LLC All rights reserved.
Privacy Statement | Terms of Service | About