1. Hau-Yung Chen, Silicon Canvas Hau-Yung Chen, Silicon Canvas Laker & OA Integration

2. © 2003, Silicon Canvas, Inc. Laker Integration into the OpenAccess Environment, June 4, 2003 DAC AgendaAgenda u What is Laker? u How Users can benefit from Laker and OpenDB integration? u Integration Experience

3. © 2003, Silicon Canvas, Inc. Laker Integration into the OpenAccess Environment, June 4, 2003 DAC What is Laker? u A Full-Featured Smart and Flexible Layout Environment u User Centric with Controllable Automation Technology u Essential Tool for nanotechnology Post P&R fine tuning u Proven Technology with > 400 tapeouts u Customers include ATI, ISSI, TSMC, UMC, GSMC, and SMIC.

4. © 2003, Silicon Canvas, Inc. Laker Integration into the OpenAccess Environment, June 4, 2003 DAC One-Stop Shop for Efficient Design Closure u ECO u Dummy Metal Filler u Metal Slot u Notch Fix u Antenna Diode Insertion or Layer Change u Signal Integrity Check & Fix u Rip-up & Re-route u And more ….

5. © 2003, Silicon Canvas, Inc. Laker Integration into the OpenAccess Environment, June 4, 2003 DAC Hierarchical Net Tracer

6. © 2003, Silicon Canvas, Inc. Laker Integration into the OpenAccess Environment, June 4, 2003 DAC Short Locator

7. © 2003, Silicon Canvas, Inc. Laker Integration into the OpenAccess Environment, June 4, 2003 DAC Controllable Router

8. © 2003, Silicon Canvas, Inc. Laker Integration into the OpenAccess Environment, June 4, 2003 DAC Integration Experiences u Efforts  5 man months, all C++ code  dbTraverse: 2500 lines  DB interface: 8700 lines  OpenAccess Specific Code: 12000 lines  Total 23,200 lines C++ Codes by 5 man months efforts  Might need another 6 man months effort for integration with new OpenAccess release and quality assurance u Highlight  Excellent documentation u Lowlight  Need more detailed and complete examples on database traverse (i.e.oaRegionQuery) We got many problems from oaRegionQuery Hope we can learn from database viewer to be available in Dec. 2003 release?  May have to propose ways to solve oaRouteSeg and oaVia within oaRoute object oaRouteSeg and oaVia are not db objects

9. © 2003, Silicon Canvas, Inc. Laker Integration into the OpenAccess Environment, June 4, 2003 DAC Laker.oa Current Status u Can open GDSII imported DB and edit with most of Laker level-2 (polygon editor) functions.  Rule-Driven  P2P  Net Tracer, Short Locator  iDRC u Can open DEF imported DB and view route segment and via.

10. © 2003, Silicon Canvas, Inc. Laker Integration into the OpenAccess Environment, June 4, 2003 DAC Met Problem - oaRegionQuery u When query with “zoom in” bbox (smaller than CV bbox), some instances won’t be called back.

11. © 2003, Silicon Canvas, Inc. Laker Integration into the OpenAccess Environment, June 4, 2003 DAC Challenge – oaRoute Edit Model u oaRoute is a DB object; but oaRouteSegment and oaVia are attributes of oaRoute. u Don’t know which scheme is better:  User can view, move or delete one oaRoute object. If user wants to edit routeSegment or via in one oaRoute, he needs one more key to enter editing mode.  User directly view and edit oaRouteSegment and oaVia. We smash oaRoute to routeSegment and via automatically.