PARIS SpringSoft announced the compliance of its Laker custom layout automation system with the OpenAccess (OA) database standard, offering standard interoperability and a robust ecosystem.
The latest version of the Laker custom layout automation system builds on several years of collaboration by SpringSoft with other industry leaders to develop the infrastructure and technology required to deliver on the promise of the OA effort.
It is completely compatible with the OA database and API, which can be used as the centre of a multi-vendor interoperable IC design environment.
It supports all the necessary interfaces, libraries and design kits, including interoperable process design kits (iPDKs) from TSMC, to work within a heterogeneous tool environment.
It also works with other custom IC tools, such as Cadence's Virtuoso. The interoperability means that a layout created in Cadence's Virtuoso can be used in the Laker system and vice versa, for example.
The OA standard effort was initiated with a goal of dramatically reducing the number of translation steps in a typical EDA flow by using a single standard database and API that were created specifically for IC design.
This also prevents the loss of data in communicating between tools as there is no database conversion required.
OA is built on a standard database and API, avoiding conflicts or ambiguities in data interpretation, and features centralized support for name mapping, data integrity, import, export, and other routine database chores.
The Laker system supports all of these standardization features in the latest release, ensuring a true interoperable platform for a multi-tool flow.
An important part of SpringSoft's approach to OpenAccess is to ensure multi-vendor interoperability for all three OA application interfaces: file exchange, data exchange, and common runtime model.
While most EDA multi-vendor scenarios use the data exchange interface (i.e. the application uses the OpenAccess API to access design data, but then reformats it into a unique runtime model used by the application), SpringSoft embraces the much more tightly coupled runtime model interface.
Using the runtime model, applications work together in the same memory on a shared OpenAccess runtime model.
“Our strategy with OpenAccess is to be the most open, including to integration by competitors”, said Oz Levia, VP of marketing and business development, “our customers can choose Laker without finding themselves locked into a data format”, he added.
SpringSoft has worked closely with key OA supporters such as Synopsys, Magma Design Automation, Mentor Graphics, and TSMC to test and implement the OA standard in complete environment.
It has demonstrated interoperability with a variety of tool suppliers, and has tested the latest versions of OA extensively to ensure reliability and seamless integration.
The Laker System's support of OA extends to IPL PDKs (iPDKs) the industry's first interoperable process design kits from TSMC. The iPDK support features support for TSMC's 65-nm process, with a roadmap to 40 and 28nm support.
Visit SpringSoft's website