editor's blog
Subscribe Now

Assembling an SoC Architecture

Planning an SoC has never been easy. As chip design has moved from mostly-from-scratch design to mostly-IP (even if internal), and as the size of the chip has grown, architectural decisions have to be made with loose back-of-the-envelope estimates, since much of the detailed implementation decisions aren’t made at that point. IP in particular can vary wildly depending on the source. And, while this sounds somewhat less likely, given the strong connections between design houses and foundries, you might even want to have a bake-off between foundries if that is part of the decision process.

A small company called Chip Path launched a site at DAC that allows architects to use a browser-based architecture tool to describe the intended function of a chip, and then map that to different foundries or IP blocks or fundamental platform architectures – SoC, FPGA, etc.

While this probably sounds obvious in the abstract, the details of doing this sort of high-level advanced planning have always been difficult. None of the pieces were originally designed to talk to each other – two identically-functioned (at a high level) IP blocks may have incompatible interfaces, for example. They’ve got what they call a “connection network” – a collection of items that have been designed to interconnect easily. These address the overall SoC interconnect scheme (NoC or fabric); streaming connections; interrupts; memory maps; and reset/control, clock, and power networks.

They have created a number of different “portals” that reflect the different things you might be looking for. Some are multi-vendor, for evaluating different foundries; others are “branded”. The SoC estimation, IP search, and FPGA fitting tools are free; they also sell other tools.

As you might suspect, the company shares roots with ChipEstimate, now owned by Cadence. But today’s problem is more complex than that of ChipEstimate back in the day. At the same time, the metaphor they use for explaining what they’re doing harkens back to something more traditional: building a car. They’re treating an SoC as a similar beast, with a list of components to choose from. This more than anything else reflects the role of IP today; such a component-oriented approach would have made much less sense in the past, when so much had to be created from scratch.

You can find out more in their release

Leave a Reply

featured blogs
Apr 7, 2020
Have you seen the video that describes how the coronavirus has hit hardest where 5G was first deployed?...
Apr 7, 2020
In March 2020, the web team focused heavily on some larger features that we are working on for release in the spring. You’ll be reading about these in a few upcoming posts. Here are a few smaller updates we were able to roll out in March 2020. New Online Features for Ma...
Apr 6, 2020
My latest video blog is now available. This time I am looking at the use of dynamic memory in real-time embedded applications. You can see the video here or here: Future video blogs will continue to look at topics of interest to embedded software developers. Suggestions for t...
Apr 3, 2020
[From the last episode: We saw some of the mistakes that can cause programs to fail and to breach security and/or privacy.] We'€™ve seen how having more than one program or user resident as a '€œtenant'€ in a server in the cloud can create some challenges '€“ at leas...

Featured Video

Industry’s First USB 3.2 Gen 2x2 Interoperability Demo -- Synopsys & ASMedia

Sponsored by Synopsys

Blazingly fast USB 3.2 Gen 2x2 are ready for your SoC. In this video, you’ll see Synopsys and ASMedia demonstrate the throughput available with Synopsys DesignWare USB 3.2 IP.

Learn more about Synopsys USB 3.2