1 f ujitsu m icroelectronics inc world wide system lsi technology – advanced technology...

World Wide System LSI Technology – Advanced Technology Development Department 1

FUJITSU MICROELECTRONICS Inc

David Dick

Director Advanced Technology Development


FUJITSU MICROELECTRONICS IncIntroduction: What is “IPSymphony” ?

The Fujitsu WW Methodology Driven Design System

Consists of Web based executable methodologies covering RTL to GDSII Fujitsu tools used by captured methodologies ISV tool encapsulations used by methodologies Fujitsu technology libraries for ISV and Fujitsu tools

Framework is based on Web Based Engineering (WBE) layer that provides a GUI for methodology capture

as well as execution Common Software Interfaces (CSI) integrating/connecting ISV and Fujitsu tools


FUJITSU MICROELECTRONICS IncIPSymphony Architecture

Release & Bug TrackingRelease & Bug Tracking

SOC Methodology

CommonSW Interfaces

(CSI)ISV Tools Fujitsu Tools

Libraries (Data & Structure for Cells & IP)

WebBasedEng.

(WBE)


FUJITSU MICROELECTRONICS IncIntroduction: Why “IPSymphony” ?

Worldwide consistent Fujitsu design environment for Online Methodology Documentation Modular Methodology Capture Block oriented & Concurrent Methodology Execution Design Center Administration Chip Implementation Status

Enables interactive capture of worldwide Fujitsu methodology expertise

Allows execution of design methodologies over the web

Enables worldwide collaborative design

Provides IP Authoring for and IP Integration in System-on-Chip designs


FUJITSU MICROELECTRONICS IncWBE

Web Based Engineering


FUJITSU MICROELECTRONICS IncWBE: Benefits

Effectively capture and document the knowledge of “design experts” Executable captured methodology Shortens designer training time Allows Fujitsu to capture and deliver consistent methodologies

worldwide Shortens the overall design TAT through concurrency Enables intercontinental chip development Provides Web based bug reporting (software & design data) Provides automatic status of chips/blocks


FUJITSU MICROELECTRONICS IncWBE: Web Data Flow

BrowserBrowser

Web Browserhttp://host.fujitsu-fme.com

ToolTool

Design DataDesign Data

Computer #1Computer #1 Computer #2Computer #2

Computer #3Computer #3

Web Server

HTMLHTML

CGICGI

httphttp

HTMLHTMLDisplayDisplay

User Interface Methodology Execution

Tool Execution


FUJITSU MICROELECTRONICS IncWBE: Network Architecture

Engineering W/SEngineering W/S

ProgramProgramBrowserBrowser

HTMLHTML

Web ServerWeb Server

CGICGI

HTMLHTML

MethodologyMethodology

Compute ServerCompute Server

SUN, HP, HALSUN, HP, HALBatchBatchJobJob

Archive ServerArchive Server

Design DataDesign Data

VersionVersionControlControl

IP BankIP Bank

Fu

jitsu

Intr

anet

Fu

jitsu

Intr

anet

httphttp

FactoryFactory

Sun, HP, HALSun, HP, HAL

NQS, LSFNQS, LSF CVSCVS

ApacheApache

FUJITSUFUJITSU

InternetInternet

FirewallsFirewalls

InternetInternet

Customer W/SCustomer W/S

BrowserBrowser

HTMLHTML

CustomerCustomerIntranetIntranet

EWSEWS WEBWEBServerServer

ComputeComputeServerServer

ArchiveArchiveServerServer

Po

ssib

le S

cen

ario

#1

Po

ssib

le S

cen

ario

#1

Netscape,Netscape,InternetInternet

ExplorerExplorer

CUSTOMER 1CUSTOMER 1

CUSTOMER 2CUSTOMER 2

CustomerCustomerIntranetIntranet

Po

ssib

le S

cen

ario

#2

Po

ssib

le S

cen

ario

#2 Fu

ture

Fu

ture

To

day

To

day


FUJITSU MICROELECTRONICS IncWBE: All Chips on Server


FUJITSU MICROELECTRONICS IncWBE: Chip Home Page


FUJITSU MICROELECTRONICS IncWBE: Methodology Flow


FUJITSU MICROELECTRONICS IncWBE: Methodology Flow (continued)


FUJITSU MICROELECTRONICS IncWBE: Methodology Job Step


FUJITSU MICROELECTRONICS IncWBE: Methodology File Step


FUJITSU MICROELECTRONICS IncWBE: Bug Report


FUJITSU MICROELECTRONICS IncWBE: Bug Report (continued)


FUJITSU MICROELECTRONICS IncMeth

Methodologies


FUJITSU MICROELECTRONICS IncMeth: Methodology Overview


FUJITSU MICROELECTRONICS IncCSI

Common Software Interfaces


FUJITSU MICROELECTRONICS IncCSI: What is “Common Software Interface” ?

Abstract information model (interface) defined without implementation details

Based on Microsoft COM (Component Object Model)

Applications (CSI clients) can dynamically load software components (CSI servers) at runtime

The application remains unchanged even if new CSI servers are developed or existing servers are updated.

Concept realized in both UNIX and Windows environments


FUJITSU MICROELECTRONICS IncCSI: Implementation

ASCIIFile

CSICSIserverserverC

SI

CS

I

AS

CII

AS

CII

Par

ser

Par

ser

Appl.Appl.EDAEDAToolTool

BinaryDatabase

CSICSIserverserverC

SI

CS

I

ED

AE

DA

AP

IA

PI


CSICSIserverserverC

SI

CS

I


EF

FIC

IEN

CY

EF

FIC

IEN

CY

ASCIIFile


FormatFormatConverterConverter

ASCIIFile

FUJITSUFUJITSUISVISV


FUJITSU MICROELECTRONICS IncCSI: De-coupling / Current Interfaces

De-coupling possible between data format & application Data servers become totally re-usable The only contract between server & client is the interface include file Applications can be linked without knowing about future servers Independent development of servers and clients possible

Current interfaces & formats supported by CSI servers INetlist : FLDL, Verilog, VHDL IParasitic : : SPF(RSPF, DSPF), SPEF IPlacement : DEF ITiming : SDF IScanDef : DEF



IPSymphony 2.x

Main Issues


FUJITSU MICROELECTRONICS IncIPSymphony Main Issues

Very well accepted by less experienced engineers, provides complete flow guidance with all inter-related data handling

Very fast ‘time to productivity’ for new engineering team members

Experienced engineers feel it is too restrictive Too difficult to change methodology “on-the-fly” Difficult to leave IPS environment, modify with external meth and return to IPS Large effort for methodology capture / maintenance, requires detail s/w knowledge Out-of-date features and tools (can’t catch up) Unforeseeable delays of development and bug fixes


FUJITSU MICROELECTRONICS IncIPSymphony Main Issues

One fixed (non-configurable) design data structure results in: Impossible to handle typical design center scenario of dealing concurrently with

multiple releases of different customer hand-offs• Can’t perform multiple trials of implementation with different versions of netlists or used tools• Can’t handle version configuration management and logistics

Methodology functionality is “implanted” into CGI (capture) scripts Prevents use of methodology functionality outside of WBE Makes methodology capture overly complicated (merged docu, GUI, function)

Methodology documentation (flow, task description, etc.) can only be displayed if chip and block setup procedures are performed

Cannot re-use the documentation part of captured methodologies for documentation purpose only (without doing/creating things)



IPSymphonyIPSymphony 33 Overview


FUJITSU MICROELECTRONICS IncWhat is IPSymphony 3 ?

IPSymphony 3 supports Project Management Methodologies by using Tasks and Flows Design Data Management Scenario Handling Collaboration Handling Data coherency through dependency tracking Common Software Interfaces for Design Data Access

Technology and environment releases are not linked


FUJITSU MICROELECTRONICS IncArchitecture

Goal Simple way of developing/capturing/delivering know-how by the

methodologist

Modularity Every component can be used stand-alone or integrated and uses interfaces

for communication to other components

Layers Complex functionality is built by adding integration layers to existing

components

Flexibility Pre-defined behavior can be easily modified locally


FUJITSU MICROELECTRONICS IncArchitecture: Components

Project Database Central storage of project configuration data

• Technology and related information (like pin assignment)• Used tools and libraries

Central storage of project logistical data• Mini-milestones, status reports, check lists

Management and tracking of communication• Customer <-> Design Center• Design Center <-> Fabrication

Import/export functionality• Tool setup (e.g. SLIF)• Form generation (e.g. Design Input Form)



Design Data Management Project central storage of design data files Version control of design data files Manipulation of data file sets Support of scenarios, i.e. ability to follow different paths in a flow



Release/Collaboration Server Delivery of libraries, tools, tasks and flows Automatic generation and delivery of project specific library cells Automatic logging of transfers Automatic notification on new updates/patches Exchange of design data Automatic hand-off validation Encrypted transfers Automatic upload/download capability



Task and Flows Tasks: Tool execution wrapped by standardized scripting functionality Standardization takes care of all the “housekeeping” and makes script

writing fast All major languages (C/C++/Perl/Tcl) supported Tcl scripting language extension allows to describe flows Flows combine tasks to bigger units where dependencies will be tracked



Common Software Interface (CSI) Components

Used for• Design Data Access• Task Support• Project DB access

Decouples IPS components from implementation in various (scripting) languages


FUJITSU MICROELECTRONICS IncArchitecture: User Interfaces

Every component supports a Command-Line Interface (CLI)

Every component supports an optional Graphical User Interface (GUI)

Some components support a Web User Interface (Web UI)



IPSymphony 3 Framework

IPS – ADMIN - MANAGERIPS – ADMIN - MANAGER

IPS – DESIGN - MANAGERIPS – DESIGN - MANAGER

System Software & Libraries &System Software & Libraries &ConfigurationConfiguration

Project Design DataProject Design Data

1 f ujitsu m icroelectronics inc world wide system lsi technology – advanced technology...

Documents