Frequently Asked Questions |
|
Answers |
| 1. What is OpenAccess? OpenAccess is a community effort to provide true interoperability versus data exchange among IC design tools through an open standard data access interface (API) and Reference Database implementation supporting that. Return to Questions |
| 2. What is being standardized? The API and its data model are the parts of OpenAccess that will be carried forward to formal standards. The Reference Database is provided as a service to provide a production grade solution "out-of-the-box" for those who wish to take advantage of it and as the "golden" model of compliant behavior. Return to Questions |
| 3. Must I use the Reference Database to be compliant to the standard? NO. The Reference Database implementation is being provided as a service that may be used for your solution but need not be. Only the API defines the standard and only the API need be used to be compliant. However, if cases arise where the API is found to be incomplete or ambiguous, the Reference Implementation's will define the standard behavior. Return to Questions |
| 4. Can there be other OpenAccess databases implemented? YES. Anyone can implement their own database and put the OpenAccess API on it. Restrictions to be aware of are those within the OpenAccess licenses should anyone creating their own database also download the Reference Implementation. In particular, the Reference Database source code is copyrighted property that may be used by the licensee -- however, this does not give one rights to copy that code into another database implementation. Return to Questions |
| 5. What are the advantages of OpenAccess for OEM and IC companies? Enables tools to be brought together to form a complete solution Enables tool choice Improves design productivity Provides true interoperability and concurrency Eliminates costly data exchange Return to Questions |
| 6. Why is "Open" access important? Allows customer choice of best-of-breed tools Allows customer to dictate the design flow Promotes EDA tool competition Provides global enterprise and cooperative design sharing Enhances technology-transfer of university research. Return to Questions |
| 7. What is the history of OpenAccess? The OpenAccess coalition was formed in Q4 1999. The members issued a request-for-technology for existing technology, looking for a solution that was proven and would be commercially adopted, and that supported a broad set of EDA tools. As a result, the Cadence Genesis database and API was selected and now forms the technology base for OpenAccess. Return to Questions |
| 8. When will the OpenAccess API specifications be released? The Version 1 (C-Level) specifications and supporting database code were released to the Coalition in 2000. These were then released to the Community (anyone who agrees to the license terms) in June 2001. The first installment of the API specification for Version 2 (C++-Level) was released in 3/2002, and the supporting database code will be released to the Community at the end of 2002. Beginning in June 2002 the Coalition member companies will have access for testing and early adoption purposes. Return to Questions |
| 9. If the OpenAccess API is sufficient for integration of tools, why is the database code being released? The OpenAccess Reference Database code is being provided free for several important reasons: To aid industry adoption by providing a production-level database that can be used immediately for testing of applications To provide a production-level database that can be used immediately by customers of compliant EDA tools To provide a "golden" reference model for compliant behavior should any ambiguities in the API specifications arise. Return to Questions |
| 10. Why is the reference database code being released in both binary and source code? The OpenAccess API along with a reference database in binary-only form would be sufficient for development and test of commercial and proprietary tools. This would also be sufficient to define the "golden behavior" in cases where specificity is incomplete or ambiguous. There is however a need for commercial customers base to have source code access for support of unique hardware platforms, fix severity 1 problems rapidly and without external dependencies, and provide for internally-used extensions that are proprietary in nature. Return to Questions |
| 11. How are the OpenAccess Coalition efforts different from other attempts? OpenAccess is the only program to make available both binary and source code for a compliant database. The SEMATECH CHDStd Program provided only a specification for an open API, but with no working database code. This made the "I" part of the ROI equation intolerable for most companies. Other commercial programs may provide, or propose to provide, an open API specification with binary-only database under normal licensing. While this is an improvement, it does not satisfy the need for an open customer-managed roadmap, nor customer requirements for commercial support autonomy. Return to Questions |
| 12. How will EDA suppliers respond to these actions? We cannot answer for all EDA suppliers, but many are lauding this move. The problems facing this industry may not be surmountable without this unifying effort. Providing proprietary code without charge to the OpenAccess Coalition and later the Community at-large has obviously been a major decision for Cadence, but they are sure it is the correct one based on the backing and support received from customers and the EDA industry as a whole. Return to Questions |
| 13. Will other EDA companies have access to the OpenAccess API? Yes, the OpenAccess API is published and available without charge or discrimination to any person or company that agrees to the license terms electronically from the OpenEDA.org web site. Further, the reference database code will be available freely to any person or company signing the required license agreement. Return to Questions |
| 14. Why aren't all major EDA companies members of OpenAccess? All EDA companies are invited and encouraged to join the Coalition or become Community members, but not all have yet opted not to join. Some may be waiting to see if OpenAccess will be successful. Others may be waiting for their customers to make clear their requirement before investing. Others may be fearful that an open interface will cause them to loose EDA tool sales to their competition. Still others may be considering the option to provide a competitive API "standard". The best way to understand why a particular company is not joining the OpenAccess effort is to ask them directly! Return to Questions |
| 15. Can any EDA supplier have access to the source code for the reference database? Yes! Initially, source code will only be made available to the OpenAccess Coalition members through Si2. Any company, EDA supplier or not, may join the Coalition. Later, the source code will be released to the Community and any person or company, EDA supplier or not, may join the Community (free of charge). Source code for Version 1 of the Reference Database was released to the Community in March 2002. Source code for Version 2 will be released to the Community at year-end 2002. Return to Questions |
| 16. What are the differences between the current Version 1 of OpenAccess and Version 2? C++ API (instead of C) Thread-safe support for multiprocessing Additional support for analog and mixed-signal design Occurrence based representation of design data Additional extensibility features Version 2 has been made more modular and readied for release to the public (Community) Return to Questions |
| 17. Will the Version 1 of the API be compatible with the Version 2 release of the database? Not completely. Version 1 is a C-level API while Version 2 is C++. The C-level API will not be carried forward into Version 2 and beyond. Any Version 1 instance of data can be moved to Version 2 by means of LEF and DEF translators that are being provided (also free of charge). Application code will have to be modified however. ...see more here.. Return to Questions |
| 18. What is included in the deliverables? Will there be translators? All software that implements the database and its API A scripting language access to the API - currently TCL Bi-directional LEF/DEF translators are provided for Version 1 LEF/DEF (v5.4) Input translation is provided with Version 2 Return to Questions |
| 19. Who will release the OpenAccess Reference Database to the world? Cadence will make the initial release to Si2 who will then release it to the Coalition and later, the Community. A technology transfer agreement between Cadence and Si2 gives Si2 rights (contractually) to distribute the database to the Community. Anyone who wishes to access this code must first sign a license agreement with Si2 (an impartial not-for-profit consortium). Thus, it is not required to sign any agreements with Cadence to gain access. Return to Questions |
| 20. When will Si2 receive Version 2 source code? Cadence has already provided Si2 with the reference database implementation in both binary and source format. This code will initially be released to the OpenAccess Community members in June 2002. At the end of 2002, this code will be released for Community download from OpenEDA.org. Return to Questions |
| 21. What are other roles Si2 plays in the OpenAccess? Si2 provides program management, support of www.openeda.org, from where the OpenAccess package may be downloaded, and services to the Coalition, including the following: Program Facilitation Technical Support Administrative Support Selected Development Marketing Standards Lifecycle Support Return to Questions |
| 22. How will Cadence, Si2 or the Coalition provide support for code once it is released to the public? When the OpenAccess code is released to Community, it will be available for download from OpenEDA.org site under license with Si2. The OpenAccess Coalition will not provide formal support for the code. However, any company may elect to provide support for the code as a business opportunity. Return to Questions |
| 23. Why was the Community Source model chosen instead of the Open Source model? In a both models, parties take software, make improvements and return improvements to the universe of users. In Open Source models, it has been shown that approval groups become so large as to slow the adoption of improvements to the code. In the OpenAccess model, the Coalition Change Team acts as a rapid approval group for submitted improvements. Return to Questions |
| 24. What is the Community? The Community is made up of the members of the public who license and download OpenAccess packages. They may then use those packages for their business or research freely according to the license terms. Also, as a Community member, it is possible to submit change recommendations (called Contributions) for consideration by the OpenAccess Change Team for inclusion into the standard and/or Reference Database. Return to Questions |
| 25. How can I join the Community? Anyone who agrees to the OpenAccess license terms and downloads an OpenAccess package from www.openeda.org becomes a member of the Community. This may be done either at an individual level or for an entire corporation. Return to Questions |
| 26. How will OpenAccess be developed going forward? Certain developments may be Community contributions once the source code is made available to the Community. Integration of these into the API and reference database, as for Coalition directed development projects, will be performed by Cadence as a contractor and partner to the Coalition. Return to Questions |
| 27. What is the Coalition? The Coalition is a group of companies in the IC industry that are working collaboratively, under the auspices of Si2, to promote the OpenAccess paradigm and provide the OpenAccess technology freely and without discrimination to all players within industry. Return to Questions |
| 28. What are the benefits of joining the Coalition? Becoming a Coalition member provides your company the following: Rights to nominate and vote of OpenAccess Change Team members Rights to propose direction and vote on OpenAccess development priorities Early insights to planned future releases of the API and reference database code Early access rights to API specifications and reference database code Additional support and training from Si2 Access to Si2 Labs for OpenAccess problem resolution Direct interaction with other OpenAccess championing companies within the Coalition Visibility in Coalition press releases Return to Questions |
| 29. How can a company become a member of the OpenAccess Coalition? The OpenAccess Coalition is open to any company that agrees to the Coalition terms and conditions. Share support expenses Commit to work with the OpenAccess API (internal to company and/or in commercial products) Possibly participate on the Coalition Change Team Review and cast vote on Coalition business including its development projects Participate in Coalition Design Work Groups Return to Questions |
| 30. Has the Coalition made any contributions to the OpenAccess technology? Yes, the OpenAccess Coalition has developed detailed requirements and functional specifications for the occurrence model and its API functions, and broad extensibility features that will be released in Version 2. Soon, another Coalition work group will be specifying the requirements and solution for managing logical and physical hierarchies. Return to Questions |
| 31. What is the Coalition Change Team? The OpenAccess Change Team is the 12-person body that determines changes to the OpenAccess API Specification and the Reference Implementation. This Team is elected by the Coalition on an annual basis from members of the Coalition. The 12-member Team will consist of a maximum of 5 EDA representatives (of which Cadence has one permanent seat), with the remainder from semiconductor or system and IC design companies. The Team is managed by two architects, one from Cadence and the other from a Change Team member company whose business is either semiconductors or electronic systems and IC design. Return to Questions |
|
| Copyright 2002 Silicon Integration Initiative, Inc. All rights reserved. Legal Notice/Disclaimer. For questions or feedback, contact Contact-Si2 |