Home > Community > Blogs > Industry Insights > open silicon ceo addressing soc ip integration challenges
 
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more conveniennt.

Register | Membership benefits
Get email delivery of the Industry Insights blog (individual posts).
 

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

Open-Silicon CEO: Addressing SoC/IP Integration Challenges

Comments(1)Filed under: DAC, SoC, verification, IP, EDA360, integration, Open-Silicon, Sherwani

Open-Silicon is a fabless SoC and ASIC design company that provides a complete "spec to silicon" development capability. As such, folks at Open-Silicon are well aware of the challenges posed by SoC design and silicon IP integration - they face those challenges every day.

In the following video interview Naveed Sherwani, Open-Silicon CEO, discusses his company's unique business model, talks about challenges in IP integration and SoC verification, and comments on statements in the EDA360 vision paper about the need for tools for integrators and for integration-optimized IP. The interview was done at the recent Design Automation Conference, where Open-Silicon, a Cadence customer and partner, was among the presenters at the Cadence booth.

 

If video fails to open, click here.

Not included here are some comments Sherwani made about addressing derivative SoC designs. He explained that Open-Silicon can take an existing chip and make modifications, starting with the existing chip and a change document from the customer. Open-Silicon then does the micro-architecture, the verification, and sometimes even the software as part of a complete solution.

In the video clip, Sherwani comments that IP must be verified in the context of the SoC and the applications it will run. I think this is a very important point. The IP doesn't work until the system works, and the system doesn't work until the software runs on it as expected.

This concept clearly expands the scope of verification. But it also opens the door to reduced costs, faster time to market, and better quality. If you take an application-driven perspective, as proposed by EDA360, there's no other way to go.

Richard Goering

 

Comments(1)

By Bill on August 9, 2010
Naveed is on target that IP must be verified in the application that is intended.  
Industry certification and plugfest can only do so much and many providers do not provide a complete subsystem (digital/analog/drivers) for this testing.  Too often, integrating components purchased from different IP vendors do not work together (and this is just at a subsystem level, let alone at the SoC).  Once you integrate the subsystem with the system, additional application testing must prove that the entire SoC works as expected.  
The first level verification that should be required for all IP is:  does it pass at least pass a certification/plugfest.  But passing this does not guarantee anything until the fully integrated design is verified.  The last level of verification must be at the integrated, complete design.  

Leave a Comment


Name
E-mail (will not be published)
Comment
 I have read and agree to the Terms of use and Community Guidelines.
Community Guidelines
The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.