PDK Standardization.

Slides:



Advertisements
Similar presentations
Python - an Open Source Project Guido van Rossum CNRI
Advertisements

4 th DataGRID Project Conference, Paris, 5 March 2002 Testbed Software Test Plan I. Mandjavidze on behalf of L. Bobelin – CS SI; F.Etienne, E. Fede – CPPM;
Ch-11 Project Execution and Termination. System Testing This involves two different phases with two different outputs First phase is system test planning.
When Should We Adopt Open Access? Igor Markov University of Michigan.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Copyright © 2006 by The McGraw-Hill Companies,
Automated Tests in NICOS Nightly Control System Alexander Undrus Brookhaven National Laboratory, Upton, NY Software testing is a difficult, time-consuming.
Software engineering Process models Pavel Agejkin.
Demonstration of Energy- Efficient Developments. Experience the Power of DEED.
CNRS – INPG – UJF AIDA Workshop, April 8-9, 2013, Frascati (Roma), Italy CAD Tools for 3D-IC and TSV-based designs Kholdoun TORKI
EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks gLite Release Process Maria Alandes Pradillo.
VxVistA Project: Summary Slide The vxVistA Project is envisioned as a method of providing a platform for an Open Source EMR based on the FOIA released.
10 Years of Scientific Linux HEPiX Spring 2014, LAPP, Annecy Alan Silverman (CERN, retired)
Chapter 2 The process Process, Methods, and Tools
Quality Control Project Management Unit Credit Value : 4 Essential
EGEE is a project funded by the European Union under contract IST Testing processes Leanne Guy Testing activity manager JRA1 All hands meeting,
LloydBank ATM Project Engineering Project Design Team: Saud Malik Brittany Johnson Joseph Garrison.
A.Marchioro - CERN/PH1 Accessing 130 nm CMOS Tech for ILC (Public Version) Oct 2006, Munich A. Marchioro CERN, Div. PH 1211 Geneva 23, Switzerland.
HNDIT23082 Lecture 06:Software Maintenance. Reasons for changes Errors in the existing system Changes in requirements Technological advances Legislation.
CERN IT Department t LHCb Software Distribution Roberto Santinelli CERN IT/GS.
VxVistA Project: Summary Slide The vxVistA Project is envisioned as a method of providing a platform for an Open Source EMR based on the FOIA released.
SOFTWARE ENGINEERING. Objectives Have a basic understanding of the origins of Software development, in particular the problems faced in the Software Crisis.
EMI INFSO-RI SA1 Session Report Francesco Giacomini (INFN) EMI Kick-off Meeting CERN, May 2010.
A. Aimar - EP/SFT LCG - Software Process & Infrastructure1 SPI Software Process & Infrastructure for LCG Project Overview LCG Application Area Internal.
18/01/16 ComNets, RWTH Aachen University, Faculty 6 openWNS Open Source Wireless Network Simulator A Simulation Platform for Wireless Systems Chair of.
Microelectronics User Group Meeting TWEPP 2013, Perugia, IT 26/9/2013.
EUDET-MICELEC Status Report October 2007 A. Marchioro / CERN-PH.
MUG meeting Wrap Up A new version of the CMOS8RF (130nm) Mixed Signal Design kit has been developed at CERN and is ready for release.  Based on the foundry.
ILC Cavity Data Management Final Report June 11, 2007 Peter Kasper.
News on the 130 nm technology support Wojciech BIALAS, Kostas KLOUKINAS CERN, PH-ESE dept. CH1211, Geneve 23 Switzerland.
EGEE-III INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks Patch Preparation SA3 All Hands Meeting.
Microelectronics User Group Meeting TWEPP 2015, Lisbon, Portugal 1/10/2015.
Instrument Control Systems Seminar 2014, 20 th -24 th October 2014 Instrument Control Systems 2014 VLTSW Infrastructure VLT Software Roadmap Doc. No.:
MUX-2010 DISCUSSION : W HAT DO WE NEED NEXT IN HEP.
3D Design IPHC Frédéric Morel - Grégory Bertolone - Claude Colledani.
Comments on SPI. General remarks Essentially all goals set out in the RTAG report have been achieved. However, the roles defined (Section 9) have not.
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
What Is Software Development? Software development is the way of creating software via successive levels in the arranged means. This method includes.
Software Tools Group & Release Process Alain Roy Mine Altunay.
WMO WIS strategy – Life cycle data management WIS strategy – Life cycle data management Matteo Dell’Acqua.
Practical Project Maintenance
The Linux Kernel Christoph Lameter, Ph.D. Technical Advisory Board The Linux Foundation.
Developers Users Committers How do I configure this now? Just one more fix and I am done! CVS Download/Use Software Submit problems/ request features Store.
Title of proposal Smart Spaces 2015 Proposers (name, organization, )  … Description of idea  …
Excel Translator™ Ultimate Risk Solutions, Inc.:
Embedded Systems Software Engineering
Introduction to CAST Technical Support
Collaborative Decision Making (CDM) Saulo Da Silva
Quality Assurance System Field Service Automation
TSA2.2 QC Change Management
Access to ASIC design tools and foundry services at CERN for SLHC
SPI Software Process & Infrastructure
3DIC Consortium Meeting
Access to 65nm Technology through CERN
IEEE Std 1074: Standard for Software Lifecycle
Development of a Common Open Platform for AB Modeling: ActivitySim
Victoria Australia (BUGVA).
Chair of Communication Networks
How to Fix Microsoft Office Error 2932 at Support Number
School of EE and Computer Science
CHAPTER 2 Testing Throughout the Software Life Cycle
Lesson 9 Sharing Documents
Applied Software Implementation & Testing
Component-Based Software Engineering
OpenAccess Coalition: Goals and Status
Quality Assurance System Field Service Automation
Software Engineering I
Lesson 14 Sharing Documents
Lecture 06:Software Maintenance
Product released! Software Released! Now what?.
Chapter 2: Building a System
Presentation transcript:

PDK Standardization

Use of standardized design kit and process flow by all consortium members -> (tracking of releases, documentation, quality assurance – wrrrrr!), Standardization of design kit – work in agreement and close collaboration with Tezzaron – we have to see what will be provided in the PDK release promised by Bob Patti for June, Shall we show some initiative in meantime to look ahead our needs and solutions appropriate to our needs that may be different with respect to ‘industrial’ 3D-IC users Standardization of tools (CAD platform Cadence <-> MicroMagic, verification DRC, LVS, 3DLVS, ERC – there are many ideas and some groups manage to find their way through this bumpy road) Recommendation coming from one group/coordination person (track of release versions, documentation access for downloading current PDK release) Patch working of PDK to satisfy current needs of separate groups in the consortium -> translated to some good software codes realizing goals like LVS, 3DLVS, screening, GDS layer compatibility -> how to put all these efforts under one umbrella -> Shall silicon brokers (metal fill routine was life saving) take this work on themselves (CMP-MOSIS-CMC), Tezzaron job? -> Shall / can we provide effort to follow CERN scheme done for 0.13um IBM process (hire external developer Cadence VCAD)? -> Shall we organize ourselves and provide pdk maintenance within the consortium members?

ISSUES: DFII – OA (OA can be technology independent – good in case Tezzaron provides access to other processes than Chartered), OA is compatible with MicroMagic OA – translation from DFII is painful Distribution of standard digital cells – is ARM rework in agreement with NDA? More?

Many people highlight necessity of standardization and availability of features allowing stable and longer term designs How should we organize ourselves? We talk to Tezzaron to pass our ideas and discuss what Tezzaron is planning to provide to us. Discuss in meantime within the consortium Bring all discussion to more concrete results when we meet at VIPS in ~1 month Who is willing to commit to / have resources to / contribute to shared work ? When? How? How many runs/year shall we think about – to provide smooth design flows, to justify and motivate efforts on the standardized stabilized PDK Which way to go?

The ultimate goal should be to provide a whole standardized package including DBI feature (extremely appealing to the HEP community) – it can be difficult to imagine having that on runs organized by silicon brokers (special operation and approach to the frame preparation are required) what do the consortium members think about this? Any other ideas??? Needs?