Design Reuse
Search EETimes
Silicon IP Verification IP Software IP Wanted IP !!! Free Download IP Analytics (Restricted Access) FPGA Board / Kit Design Services Foundries Main IP/SoC Products Embedded Systems Design Platform / Structured ASIC Foundries FPGA / CPLD Fabless / IDM Deals Legal Business Financial Results People ESL Design Commentary / Analysis Main Silicon IP / SoC Verification IP FPGA / CPLD Embedded Systems Design Platform / Structured ASIC ESL Design ESL Design Standards & Best Practice Structured ASIC Verification IP Main On Cores Embedded Systems EDA Tools IP Cores Tool Demos D&R Partners Research / Market Reports Events Calendar Webcasts / Podcasts Online Bookstore
On Cores
Meditations on the semiconductor and IP industries
By Warren Savage, CEO, IPextreme



Sunday Mar. 18, 2007

System Verilog still risky as an IP platform

I'm excited as anyone about System Verilog. It is a significant step forward towards a unified implementation and verification language for the design of semiconductors. Yet the reality of it supplanting today's languages is still far away due to uneven support by the EDA community.

In the article "System Verilog support for design falls short", Richard Goehring reports that designers are not rushing to the new language as fast as anticipated and cites very uneven support of System Verilog features by the EDA community.

Customers are further complaining about the lack of uniform industry support of the language in John Cooley's DeepChip newsletter. They hint of the risk of using System Verilog will lock them into a specific company's EDA design flow because they might use a feature that is not yet implemented in a competitor's product.

That's a big problem for IP companies to adopt it as a standard language. IP has an incredibly long shelf life and therefore needs to be built to last and be immune to the twists and turns of ever changing EDA flows and design methodologies. This means IP needs to be built on well-established languages and tools.

Perhaps the most obvious (and therefore least likely) solution for this System Verilog situation is to eliminate all "optional features" from the language. Tools would support the full language or not. This would also eliminate the need for meaningless spin-doctoring such as "we support most of the features", "we support 95% of the features", "we support all required features", etc.

Lacking that, it looks like we have no alternative but to stick with the old standbys of Verilog/VHDL on the design side and the alphabet soup of proprietary verification languages that can run on industry standard simulators via PLI connections.


Posted by Warren Savage on Sunday Mar. 18, 2007 | Add a Comment




RSS Feed

Add this blog to your RSS newsreader!

Archives

  • One on One: Jack Browne

  • One on One: Kathy Werner

  • One on One: Ralph Von Vignau

  • One on One: Stephen Padnos

  • One on One: Johan Van Ginderdeuren

  • One on One: John Koeter

  • One on One: Hal Barbour

  • One on One: Joe Abler

  • One on One: Brian Gardner

  • One on One: Bill Martin

  • About the Author

    Warren Savage, President and CEO of IPextreme, is a well-known and published authority in the field of semiconductor intellectual property. He has a long history of pushing the envelope of design methodology from his work in fault tolerant computing at Tandem Computers in the 1980's and driving reliable design metholologies into commercial practice at Synopsys for its DesignWare IP product in the 1990s. Much of his thinking became embodied in the seminal book on IP reuse, the Reuse Methodology Manual. Warren is taking his vision to the next level with his latest company, IPextreme, which is focused on enabling broad commercialization of IP captive in large semiconductor companies.