Design Con 2015
Breaking News
Comments
Newest First | Oldest First | Threaded View
D. Desharnais
User Rank
Rookie
re: War of words erupts in rival PDK camps
D. Desharnais   9/14/2010 5:06:45 PM
NO RATINGS
Part 2 of 2: We have based our warning alert due to actual experiences our customers have faced when trying to implement a hybrid approach as it was described in the original post. In a couple of serious cases now, a customer using PyCells in their design flow experienced unforeseen problems that resulted in schedule delays and non-deterministic results. Translation: non-forecasted delays and complications as back-and-forth ensued between all parties to determine root cause. Turns out root cause was not due to Cadence. In the end, this experience was not what the customer anticipated when they decided to try out a hybrid approach. As a result of cases like this we responded with our alert to help prevent these types of situations in the future. At the end of the day, customers want to tape-out chips with predictability, the highest quality, on schedule, and with the least amount of hassle; and with a vendor that will stand behind them if and when the unexpected happens. We provide that level of service at Cadence, and using SKILL-based PCells with Virtuoso provides the most deterministic path to final design closure. David Desharnais Product Management, Cadence

D. Desharnais
User Rank
Rookie
re: War of words erupts in rival PDK camps
D. Desharnais   9/14/2010 5:06:12 PM
NO RATINGS
Because of character limitations, this comment is the first of 2 parts: Multiple tens of thousands of customers use Virtuoso daily. These customers repeatedly tell us what matters most to them: stability in their full custom/analog design software and flows, that can span multiple process nodes, multiple projects, multiple geographies, and multiple design teams. Other vendors have a point of view that is understandable, but taking a customer-centric view, clearly customers need a dependable, production proven flow that drives the highest quality design with minimal risk. When it comes to supporting customers for production design, it is critical that we can act quickly and comprehensively should a problem occur. This means having visibility into all aspects of the design and flow as needed in order to identify the root cause. Our ability to respond like this is a huge assurance to customers, and reflects our commitment to stand behind our products. It is important to note that TSMC’s iPDK does not equal PyCells. iPDK contains both full SKILL-based PCell support as well as Python-based PyCells. Thus Virtuoso users can use iPDK with unfettered success, and they do. Should a customer choose to use PyCells in their flow, we cannot and do not intend to prevent that, but as a means of full-disclosure, they need to understand the risks associated with the approach. David Desharnais Product Management, Cadence

Daniel Payne
User Rank
CEO
re: War of words erupts in rival PDK camps
Daniel Payne   9/13/2010 11:16:50 PM
NO RATINGS
I needed to update my comment because I just learned that TSMC has built, qualified and shipped these cells as part of their iPDK. This really isn't a language issue, it is more a marketing ploy by Cadence to cast Fear, Uncertainty and Doubt (FUD) upon users. Virtuoso users have to simply pick up the phone and let Cadence know that this warning message needs to be removed. Now let's get back to innovating our products instead of scaring EDA users.

ESF
User Rank
Rookie
re: War of words erupts in rival PDK camps
ESF   9/13/2010 10:30:12 PM
NO RATINGS
I think “format battle” is incorrect. Fundamentally this is an IP issue between EDA vendors and IC companies. PDK’s are a form of IP. Design teams, and also foundries, simply need to decide who they want to control their PDK IP – themselves, or somebody else. Besides, IP is supported by IP providers. We don’t see a parallel message, “Warning – the use of Synopsys Designware is not supported in EDA360.” You’d be forgiven for suspecting the difference relates to Virtuoso market power. The trendy analogy is smartphones and apps, but a better one is VAX/VMS and Unix. Yes VAX/VMS was everywhere, but in the end, Unix customers got more done. Similarly, Cadence customers use PyCells not to abandon Virtuoso, but because PyCells help them get more done at sub-65nm geometries. PyCell and iPDK users get more from Virtuoso, not less. If that’s a bad thing for Cadence, then EDA really does need a new business model. If you were a Virtuoso competitor, you’d thank Cadence every day for that warning message. The reality is that Custom IC design has outgrown any one company’s control; 28nm takes an ecosystem of foundries, EDA companies, IP providers, DFM specialists etc. That means open systems and interoperability. Cadence has served the industry richly in the past and still has much to contribute beyond, “non-Skill object detected.” This is a trend Cadence ought to be leading themselves, not ceding to others. Eric Filseth CEO, Ciranova

Daniel Payne
User Rank
CEO
re: War of words erupts in rival PDK camps
Daniel Payne   9/13/2010 8:05:06 PM
NO RATINGS
Every EDA company has their own languages to extend and interact with tools: Mentor: Ample, Tcl, Genie Cadence: Skill, Tcl Ciranova: Python I truly hoped that Tcl/Tk would take over as a defacto standard, yet it didn't. Because of the proliferation of languages it is reasonable to issue a warning message by Cadence when Python code is detected by Skill. A compromise may be to allow customers to simply suppress these messages with a switch setting.

yalanand
User Rank
Rookie
re: War of words erupts in rival PDK camps
yalanand   9/11/2010 10:08:53 AM
NO RATINGS
This is going to close battle. Though so many companies joined iPDK, some of the analog biggies like TI are shifting fully to Cadence by next year. Cadence is already feeling the competition heat and warning messages to the customers :).

selinz
User Rank
CEO
re: War of words erupts in rival PDK camps
selinz   9/10/2010 8:22:57 PM
NO RATINGS
This doesn't seem like Cadence is really doing anything unreasonable. It is likely that this was prompted by a customer demanding PyCells support. I believe that they would have served themselves better by not issuing the "warning."

mark.lapedus
User Rank
Rookie
re: War of words erupts in rival PDK camps
mark.lapedus   9/10/2010 5:33:28 AM
NO RATINGS
PDK war-Round 2! Who will win the battle?



Flash Poll
Top Comments of the Week
Like Us on Facebook
EE Times on Twitter
EE Times Twitter Feed

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
EE Life
Frankenstein's Fix, Teardowns, Sideshows, Design Contests, Reader Content & More
Max Maxfield

Book Review: Deadly Odds by Allen Wyler
Max Maxfield
6 comments
Generally speaking, when it comes to settling down with a good book, I tend to gravitate towards science fiction and science fantasy. Having said this, I do spend a lot of time reading ...

Martin Rowe

No 2014 Punkin Chunkin, What Will You Do?
Martin Rowe
Post a comment
American Thanksgiving is next week, and while some people watch (American) football all day, the real competition on TV has become Punkin Chunkin. But there will be no Punkin Chunkin on TV ...

Rich Quinnell

Making the Grade in Industrial Design
Rich Quinnell
13 comments
As every developer knows, there are the paper specifications for a product design, and then there are the real requirements. The paper specs are dry, bland, and rigidly numeric, making ...

Martin Rowe

Book Review: Controlling Radiated Emissions by Design
Martin Rowe
1 Comment
Controlling Radiated Emissions by Design, Third Edition, by Michel Mardiguian. Contributions by Donald L. Sweeney and Roger Swanberg. List price: $89.99 (e-book), $119 (hardcover).