UT VLSI Seminar:

OpenAccess: The Team, The Technology and Value Proposition

Sumit DasGupta Vice President, Technology Silicon Integration Initiative (Si2) Austin, TX 78727 email: [email protected]

Technologies for Open Architectures Outline

• Si2 / OpenAccess Organization and Goals • OpenAccess Technology • OpenAccess Proliferation and Progress • OpenAccess Value Proposition • Call for Action

Technologies for Open Architectures –1– First, Some Simple Q&A

• Who / what is Si2?

¡ Silicon Integration Initiative is an EDA/electronics industry consortium focused on infrastructure standards based on community contributions to enhance chip design flows • What is OpenAccess?

¡ An open, industry-standard API, and a reference implementation, to enable plug-and-play connectivity of best-in-class EDA tools to create customized design flows

¡ Based on technology contribution from • Who drives OpenAccess?

¡ Si2’s OpenAccess Coalition, which consists of members from leading EDA and end-user companies

Technologies for Open Architectures –2– Si2 Organization

Primary Charter: • Develop user-driven, infrastructure standards / solutions based on contributed technology to enhance silicon-centric design flows Si2 • Drive adoption of above solutions / standards

Primary Charter: • Within Si2’s charter, identify industry-wide infrastructure problems suitable for solution and industry-wide adoption Si2 Councils (e.g., DTC) • Define specific goals of PTAB’s

Primary Charter: • Create coalition of member companies • Drive specific problem identified above for solution and adoption, Si2 PTAB’s (e.g., OAC) based on technology contribution

Primary Charter: • Define roadmap for solution, including standardization • Define detailed development plans and contributed technology Working Groups (e.g., OAC Change Team)

Technologies for Open Architectures –3– OpenAccess Goals

• Provide IC design tool infrastructure that yields

¡ Integrated systems rather than sequential flows

¡ Choice of design tools and provider

¡ Technology transfer of innovative research

¡ Collaborative design capability for ICs

• Promote an open standard for IC design data access

• Gain adoption of the standard within the EDA industry and university research programs

Technologies for Open Architectures –4– Growing and Evolving OpenAccess Coalition

2004 Membership • Single tier membership for end-user companies, 3-tier membership for EDA companies to promote proliferation • Current membership: 24 companies and growing 8 New Members

2003 Membership • Single-tier membership • Members: 16 companies

Technologies for Open Architectures –5– Current OAC Membership

• Artisan • PDF Solutions • Cadence • Philips • CiraNova • Renesas • ClioSoft • Sagantec • HP • Silicon Canvas • IBM • Silicon Navigator • IC-Manage • ST Microelectronics • • Sun • LogicVision • Synchronicity • LSI Logic • Synplicity • • Tektronix • Motorola (Freescale) • Verisity

Technologies for Open Architectures –6– OpenAccess Process

OpenAccess Community

Issue Translators, OpenAccess OpenAccess Tracking Language Standard Reference System

Bindings, etc. IM and API Implementation RFT’s /Responses Enhancements Bugs OA Roadmap

OpenAccess Roadmap OpenAccess Integrator

OA Coalition Enhancements OpenAccess Change Team RFTs

OA Working Groups

Technologies for Open Architectures –7– ... Outline

• Si2 / OpenAccess Organization and Goals • OpenAccess Technology • OpenAccess Proliferation and Progress • OpenAccess Value Proposition • Call for Action

Technologies for Open Architectures –8– Open Access Deliverables

TheThe StandardStandard Application(s)

InformationInformation ModelModel (Graph(Graphical)ical)

API Implementation (Solaris/HP-UX/Linux, C++ Binding) APIAPI InterfaceInterface ((CC++++ BiBindindinng)g)

Persistent APIAPI Store Runtime Memory SpecificationSpecification (HTML(HTML)) TheThe ReferenceReference ImplementationImplementation

Technologies for Open Architectures –9– Information Model Scope

•• DesignDesign DataData •• TechnologyTechnology DataData

¡¡ HierarchicalHierarchical connectivityconnectivity ¡¡ AllAll technologytechnology featurefeaturess andand constraints,constraints, suchsuch as,as, wirewire width/swidth/spacing,pacing, viavia spacing,spacing, ¡¡ FloorplanFloorplan oobjectsbjects andand attributesattributes stackedstacked viavia limilimitts,s, papadd position/spacing,position/spacing, ¡¡ PhysicalPhysical llaayoutyout etc...etc...

¡¡ StandardizedStandardized RouteRoute andand ViaVia semanticssemantics

¡¡ ShapesShapes

¡¡ ParasiticsParasitics (detail(detaileded andand reduced)reduced)

¡¡ ScanScan chaichainsns

¡¡ ExtensionExtension objectsobjects (app.-defined(app.-defined objects,objects, attributes, groups and properties) attributes, groups and properties) •• LibraryLibrary ManagementManagement ¡¡ OccurrenceOccurrence modelmodel andand EMHEMH ¡¡ Light-weightLight-weight susupportpport forfor handling:handling: ¡¡ TimingTiming (using(using extensionextension objectsobjects now,now, willwill bebe ¾¾ DesignDesign hierarchyhierarchy addedadded asas partpart ofof designdesign dadatata afterafter definitiondefinition ofof timitimingng constraiconstraintnt specs)specs) ¾¾ AccessAccess contcontrolrol ¡¡ DDDDMM WGWG definingdefining robustrobust APIAPI extensionextension toto plugplug inin DDMDDM solutionssolutions

Technologies for Open Architectures –10– Design Flows or Nightmares Past!

Life in the Slow and Easy Lane!

App 1 Trans 2 App 2 Trans 3

Writing translators: • Compelling job description for a PhD? Or, how to drive him/her to your competition! • Cost of developing and maintaining above flow 3-5X that of tool cost • Problems in translation:

¡ At any instant of time, what App(i) delivers is not what App(i+1) expects (syntax/semantics)

¡ Over period of time, App(i) evolves differently from App(i+1), so translator between App(i) and App(i+1) must evolve

Technologies for Open Architectures –11– Streamlined Design Flows for 90nm & Beyond!

Technologies for Open Architectures –12– Today’s Reality!

Tightly Coupled File Exchange (Cooperative, Incremental) Data Exchange Applications Application Application DLL CONTROL API DLL API Thin Mapping

File Format Private Private Runtime OpenAccess API Runtime

Translator

OA OpenAccess API Runtime OpenAccess API

OpenAccess OA OA Persistent Store Runtime Runtime

Technologies for Open Architectures –13– Example of API Benefits

Courtesy of:

Technologies for Open Architectures –14– Golden Gate Working Group Goals

Potential Short-Term Goal Long-Term Goal

OpenAccess Apps Milky Way Apps OpenAccess Apps Milky Way Apps

OA API MW API OA API

OA RTM MW RTM OA RTM

Ref. DB Bridge MW DB Ref. DB MW DB

Technologies for Open Architectures –15– Moving Forward: OA Roadmap!

2007 - 2009 2005 – 2006 3Q2004 07/2003

Key items: Key items: Potential Key items: Potential Key items: • EMH • X-routing support • Support design-to- • Formal transistor-level Plug-in for custom manufacturing modeling support ¡ Logical / Physical • hierarchy region query • Timing/delay • Support behavioral-level • Constraint modeling constraints data models ¡ Occurrence Model • Major release API • Library modeling • Support architectural-level • Multi-threading compatibility • System-in-package data models • And many more .... • Version-independent • Manufacturing test • And many more …. on-disk storage • IP security • Library & design data • Control-level tool management communication API • MW-to-OpenAccess translator • And many more …. • And many more ....

Technologies for Open Architectures –16– Outline

• Si2 / OpenAccess Organization and Goals • OpenAccess Technology • OpenAccess Proliferation and Progress • OpenAccess Value Proposition • Call for Action

Technologies for Open Architectures –17– Growing Plug-and-Play Ecosystem

OpenAccess YE2003

Cadence Synchronicity YE2002

IC Manage BindKey LSI

HP Fujitsu

Sagantec In2Fab MicroEDA

PDF Solutions Silicon Canvas ClioSoft

Technologies for Open Architectures –18– Status in Academia

• UC, Santa Cruz

¡ Student conducting OpenAccess-based research, ported and contributed Linux version of OpenAccess • NC State

¡ Design flow course based on OpenAccess, potential future research project based on OpenAccess • UC, Berkeley and UC, San Diego

¡ VLSI course using OpenAccess training materials from Si2 • U. of Michigan

¡ Evaluating future research project based on OpenAccess • CMU

¡ Student starting on OpenAccess training materials from Si2 prior to research project • SUNY, Binghampton

¡ Student starting on OpenAccess training materials from Si2 prior to research project • U. of Tokyo

¡ Initial discussions on using OpenAccess as basis for course work and training

Technologies for Open Architectures –19– Outline

• Si2 / OpenAccess Organization and Goals • OpenAccess Technology • OpenAccess Proliferation and Progress • OpenAccess Value Proposition • Call for Action

Technologies for Open Architectures –20– OpenAccess Benefits: End-users

• Saves investment in proprietary API / data model / database solution

• Enhances interoperability with vendor tools ¡ Reduces/eliminates investment to develop/maintain translators

¡ Plug-and-play access to new tools reduces integration costs

¡ Reduces/eliminates performance impact of translators on design flows

• Allows focus on core competencies, i.e., developing value-added internal tools and customized flows

• Leverage collective knowledge base and contributions of OA community, including academia

Technologies for Open Architectures –21– OpenAccess Benefits: EDA Companies

• Large EDA companies:

¡ Easier access to customers

¾ Simpler integration into their flows

¡ Less interfacing effort between internal groups

¾ Focus on tool development

¡ Easier to integrate tools when purchasing small vendors

Technologies for Open Architectures –22– OpenAccess Benefits: EDA Companies

• Small EDA companies:

¡ Reduces barrier to entry, i.e., quicker “startups”, faster ROI ¾ Less infrastructure to develop ¾ Custom infrastructure may be barrier to acceptance ¾ Focus on tool development

¡ Less interfacing effort

¾ Quickly sell to a larger market

Technologies for Open Architectures –23– OpenAccess Benefits: Universities

• Access to commercial database and its users • Ability to influence standard • Access to industry benchmark examples • Early training of students on industry standard • Potential for research on tightly-coupled applications and flows • Ability to streamline technology transfer

Technologies for Open Architectures –24– Benchmark Test Cases Conundrum!

Benchmarking Today:

Industrial Design Environment Academic Research Environment

Tools Tools e API API Divid

DB try DB s u • Identifies critical problems as part of d leading-edge design efforts • Researches / Solves problems identified • Works with academia to identify and by industry solve above problems, but,... emia-In Acad • Unwilling to release leading-edge test • Requires cutting-edge, industrial-grade cases to evaluate academic research benchmark test cases to verify solution results for fear of losing IP addresses problem

Tool to be benchmarked

Technologies for Open Architectures –25– OpenAccess Benefits: Benchmark Test Cases

Benchmarking based on OpenAccess: A Proposal!

Industrial Design Environment Academic Research Environment

Tools Tools

OA API OA API e OA DB OA DB

• Identifies critical problem as part of Divid

leading-edge design efforts try

s • Researches / solves problem identified

u by industry

• Works with academia to identify and d solve above problem, but,...

• Assists academic partner benchmark emia-In • Installs solution in industrial partner’s solution using leading-edge design internal design system to benchmark in within corporate network, then transfers

Acad partner’s environment normalized results to academic partner

• Industry gets proven solution to problem • Academics get proof-of-concept and inhibiting progress without releasing IP publication data

Technologies for Open Architectures –26– Outline

• Si2 / OpenAccess Organization and Goals • OpenAccess Technology • OpenAccess Proliferation and Progress • OpenAccess Value Proposition • Call for Action

Technologies for Open Architectures –27– OpenAccess: Call for Action!

• Step 1: Initiate what other universities have begun

¡ Sign up for OpenAccess training

¡ Inject OpenAccess into appropriate courses

• Step 2: Evaluate / initiate research projects based on OpenAccess

¡ EDA algorithms

¡ Database issues to enhance capabilities / capacity / performance

Technologies for Open Architectures –28– OpenAccess Information Sources

!!! • Si2 web-sites: ay D w ¡ www.openeda.si2.org e N ¡ www.si2.org a of n aw • Si2 contacts: D he ¡ Bill Bayer: [email protected] T s: ¡ Bob Carver: [email protected] es cc ¡ Sumit DasGupta: [email protected] nA pe O

Technologies for Open Architectures –29–