EDA Scripting Unleashed (Voted-Best-Paper)

Author:  James Masters, Intel

In many traditional design flows, high-performance robust EDA capabilities are limited to formal EDA tools. Design Automation (DA) engineers build additional project-specific capabilities either by using an EDA tool’s proprietary scripting API or by creating a standalone lightweight script that relies upon translation of design data into other formats. This results in extra runtime overhead, additional possible points of failure, and a burden of working with lossy design data formats.

With the advent of oaScript, DA engineers can quickly write scripts that directly read and write OpenAccess (OA) data using one of their favorite scripting languages – Perl, Python, Ruby, or Tcl. Also, a new OA extension is now available which provides high-speed layer manipulation and boolean operations directly within an oaScript – called “oaxPop” (OA eXtension Polygon Operators).

The combination of oaScript with oaxPop enables a DA engineer to write high-performance robust EDA capabilities without the overhead of using a formal EDA tool. This presentation will demonstrate how oaScript and oaxPop have been used together to create real-life applications that are used in a production design flow.

james_masters_-_eda_scripting_unleashed_-_real-life_examples_using_oascript_and_oaxpop

BIO:

James Masterjames_master_1000x1000s graduated from the University of Phoenix with a Bachelor of Science in Information Technology with an emphasis on computer programming. He has worked at Intel Corporation for 20 years in various full-custom design implementation roles.

James is currently managing a team focused on improving custom layout productivity for Intel’s advanced process technologies. James is an advocate of open standards that help streamline the design flow and maximize productivity and reuse.

Outside of work James enjoys outdoor activities such as camping, fishing, hiking, gardening, etc.

OpenAccess Membership Documents

OpenAccess Membership Required Documents

First: For access to current OpenAccess and oaScript (and other extensions) source code, the member must join the OpenAccess Coalition.

OpenAccess  Membership agreement:   OAC_Generic_Membership_Agreement.pdf  

oac_generic_membership_agreement

Second:   Use of OpenAccess requires the OpenAccess–Internal Use and Distribution License V 4.0 Oct. 1, 2004. 

openaccessinternaluseanddistributionlic_v4_041001

Third:   Use of Si2 OpenAccess Scripting Interface requires the ESG (Extensions Steering Group) OpenAccess ESG License v2.0 (January 31, 2013)

si2_esg_license_v2_0_01-31-2013