1 / 3

Unleash PDK with Open Standards

Unleash PDK with Open Standards. Synopsys 18th EDA Interoperability Developers' Forum Hau-Yung Chen Nov. 9, 2006. Open PDKs: Primarily a Business Issue. - Process name - SPICE Models - Schematic Symbol - Layout TF - Parameterized Devices  - DRC rule file  - LVS rule file

yuri
Download Presentation

Unleash PDK with Open Standards

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Unleash PDK with Open Standards Synopsys 18th EDA Interoperability Developers' Forum Hau-Yung Chen Nov. 9, 2006

  2. Open PDKs: Primarily a Business Issue - Process name - SPICE Models - Schematic Symbol - Layout TF - Parameterized Devices  - DRC rule file  - LVS rule file - RC extraction rule file Open Platform PDK A_X Foundry A Defined PDK PDK Open PDK FoundryA Tool X PDK A_Y PDK A_Z PDK B_X Foundry B Defined PDK Foundry B Tool Y PDK B_Y PDK B_Z PDK C_X Foundry/IDM C Defined PDK Foundry/IDMC Tool Z PDK C_Y PDK C_Z

  3. Truly Open PDKs: Everybody Wins IF: • Every involved party clearly sees the potential benefit and is willing to participate, play by the rules, and support truly open standards • Pure Play Foundry & IDM • EDA Vendor & User • Coordinated by independent bodies • Rename PDK to OPDK, UPDK, or TDK, or OK (OpenKit) • The name PDK carries too much of a single-company image • Signify a clean start and clear separation of Open Formats from old Proprietary Formats • Avoid the name confusion and conflict or even legal issues with the existing one. • Ban any proprietary languages • Enough freely available scripting languages, Tcl, Python, Perl, etc. • Why do we have to support a proprietary language in an Open system? • Ban any vendors who want to hijack the Open system with proprietary stuff. • Start with a baseline OPDK set including Schematics Symbols, Layout TF, and PCells Allow us to compete on Technology and Implementation: not on Scripting language, format, spec.

More Related