FMCAD 2027: Will the FM Have a Real Impact on the CAD? Carl Pixley Disclaimer: These opinions are mine alone and not necessarily Synopsys’. Also, I tend.

Slides:



Advertisements
Similar presentations
Contact Identification The Importance of Accurate Contact Information CHAPTER THREE.
Advertisements

Using emulation for RTL performance verification
StormingForce.com Motion. StormingForce.com StormingForce’s technology is significantly increasing productivity and quality of manual repetitive tasks.
- Verifying “Golden” reused IPs The Evil’s in the Edits William C Wallace Texas Instruments Nitin Jayaram Texas Instruments Nitin Mhaske Atrenta Inc Vijay.
Cadence Design Systems, Inc. Why Interconnect Prediction Doesn’t Work.
The Secrets of Practical Verification… © 2008 Think Verification.
What are Formal Verification Methods Mathematically based languages, techniques and tools for specifying and verifying systems Language – Clear unambiguous.
Annoucements  Next labs 9 and 10 are paired for everyone. So don’t miss the lab.  There is a review session for the quiz on Monday, November 4, at 8:00.
Software Processes Coherent sets of activities for specifying, designing, implementing and testing software systems.
Presenter: PCLee – This paper outlines the MBAC tool for the generation of assertion checkers in hardware. We begin with a high-level presentation.
1 Speed, Drunkenness, and the Wall Does High Level Design/ESL Make Sense? Kris Konigsfeld Sr. Principal Engineer Oregon CPU Architecture Intel Corporation.
The Fundamentals of Managerial Economics
The Future of Formal: Academic, IC, EDA, and Software Perspectives Ziyad Hanna VP of Research and Chief Architect Jasper Design Automation Ziyad Hanna.
Business plan overview (1)
Spring 07, Feb 6 ELEC 7770: Advanced VLSI Design (Agrawal) 1 ELEC 7770 Advanced VLSI Design Spring 2007 Verification Vishwani D. Agrawal James J. Danaher.
The Design Process Outline Goal Reading Design Domain Design Flow
Design For Verification Synopsys Inc, April 2003.
Concurrent & Distributed Systems Lecture 5: Semaphores and Synchronisation Concurrent processes which don’t interact in some way don’t form an interesting.
Behavioral Design Outline –Design Specification –Behavioral Design –Behavioral Specification –Hardware Description Languages –Behavioral Simulation –Behavioral.
ECE Synthesis & Verification1 ECE 667 Spring 2011 Synthesis and Verification of Digital Systems Verification Introduction.
Strategy, Balanced Scorecard, and Strategic Profitability Analysis
School of Computer ScienceG53FSP Formal Specification1 Dr. Rong Qu Introduction to Formal Specification
Principle of Functional Verification Chapter 1~3 Presenter : Fu-Ching Yang.
Test and Verification Solutions116 th April 2010 Silicon South West, “Testing Times” The Economics of Verification Mike Bartley, TVS.
(1) Introduction © Sudhakar Yalamanchili, Georgia Institute of Technology, 2006.
Using Mathematica for modeling, simulation and property checking of hardware systems Ghiath AL SAMMANE VDS group : Verification & Modeling of Digital systems.
FAMILY ECONOMICS & FINANCIAL EDUCATION © Family Economics & Financial Education – Revised November 2004 – Investing Unit – Language of the Stock Market.
Extreme Makeover for EDA Industry
Design Verification An Overview. Powerful HDL Verification Solutions for the Industry’s Highest Density Devices  What is driving the FPGA Verification.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
FPGA-Based System Design: Chapter 6 Copyright  2004 Prentice Hall PTR Topics n Design methodologies.
CSE 494: Electronic Design Automation Lecture 2 VLSI Design, Physical Design Automation, Design Styles.
Chonnam national university VLSI Lab 8.4 Block Integration for Hard Macros The process of integrating the subblocks into the macro.
ESL and High-level Design: Who Cares? Anmol Mathur CTO and co-founder, Calypto Design Systems.
Semi-automatic Property Generation for the Formal Verification of a Satellite On-board System Wesley Gonçalves Silva.
1 Hybrid-Formal Coverage Convergence Dan Benua Synopsys Verification Group January 18, 2010.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
VLSI DESIGN CONFERENCE 1998 TUTORIAL Embedded System Design and Validation: Building Systems from IC cores to Chips Rajesh Gupta University of California,
ASIC, Customer-Owned Tooling, and Processor Design Nancy Nettleton Manager, VLSI ASIC Device Engineering April 2000 Design Style Myths That Lead EDA Astray.
1. CAD Challenges for Leading-Edge Multimedia Designs Ira Chayut, Verification Architect (opinions are my own and do not necessarily represent the opinion.
© 2006 Synopsys, Inc. (1) CONFIDENTIAL Simulation and Formal Verification: What is the Synergy? Carl Pixley Disclaimer: These opinions are mine alone and.
Business Trends and Design Methodologies for IP Reuse Allen C.-H. Wu Department of Computer Science Tsing Hua University Hsinchu, Taiwan, R.O.C {
Writing Systems Software in a Functional Language An Experience Report Iavor Diatchki, Thomas Hallgren, Mark Jones, Rebekah Leslie, Andrew Tolmach.
EE3A1 Computer Hardware and Digital Design
©2011 Gary Smith EDA, Inc.All Rights Reserved. Reality and Responsibility in the EDA Market (EDP 2011) ©2011 Gary Smith EDA, Inc.All Rights Reserved.
1 Giving the Gorilla Some Brains: How Can Formal Complement Simulation? FMCAD Panel Discussion November 14, 2006 Andreas Kuehlmann.
E-Commerce Business Plans / Business Models Tony Stanco Director, SEAS Council of Entrepreneurial Tech Transfer and Commercialization
CHAPTER 8 Developing Hard Macros The topics are: Overview Hard macro design issues Hard macro design process Physical design for hard macros Block integration.
Verification – The importance
Panel Discussion High Level Design and ESL: Who Cares? Masahiro Fujita VLSI Design and Education Center (VDEC) University of Tokyo.
© 2009 IBM Corporation Smarter Decisions for Optimized Performance IBM Global Executive Forum Panel Discussion Business Analytics and Optimization Fred.
Chapter 1 IS in the Life of Business Professionals Chapter 1.
Of Financial Accounting, 3e CORNERSTONES. © 2014 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part,
CS223: Software Engineering Lecture 2: Introduction to Software Engineering.
Chapter 11 System-Level Verification Issues. The Importance of Verification Verifying at the system level is the last opportunity to find errors before.
Equivalence checking Prof Shobha Vasudevan ECE 598SV.
Saving and Investing What’s the big deal?. What is the difference between saving and investing?
1 Chapter 3: The Measurement Fundamentals of Financial Accounting.
Inventory Folks are from Mars and Acquisition / Divestiture are from Venus What Do Inventory Processes and Estimates have to do with Timberland Transactions.
Factors to consider System component costs Methods
ASIC Design Methodology
Intelligent Design of Electronic Assets (IDEA) Workshop
332:437 Lecture 7 Verilog Hardware Description Language Basics
Introduction to Digital Electronics
332:437 Lecture 7 Verilog Hardware Description Language Basics
332:437 Lecture 7 Verilog Hardware Description Language Basics
Cost Principle and Materiality Constraint
Win with HDL Slide 4 System Level Design
Presentation transcript:

FMCAD 2027: Will the FM Have a Real Impact on the CAD? Carl Pixley Disclaimer: These opinions are mine alone and not necessarily Synopsys’. Also, I tend toward hyperbole. November 6, 2007

© 2006 Synopsys, Inc. (2) Proposition Zero Formal Methods ALREADY have had a major effect on CAD.  Most CAD tools have some form of mathematical reasoning “built in”.  Chips cannot be implemented without equivalence checking.  Constraint Based Verification is very common: It is based upon formal principles.

© 2006 Synopsys, Inc. (3) It’s hard to make a buck in EDA. My perspective is from the EDA industry. For the last ~5 years the whole EDA industry has made about $5B and it really has not changed very much. The big EDA companies have volume purchase agreements with our customers – often the deals are Texas “family style”, i.e., all you can eat for one price. This is good for financial stability but not so good for growth and innovation.

© 2006 Synopsys, Inc. (4) Proposition One Automated Synthesis from algorithm (transaction) level to RTL cannot be accepted without formal HL-to-RTL equivalence.  Design managers will not accept the results of HL synthesis without a formal tool to check independently.  Simulation is well-known to not be sufficient.  It is a hard problem but we are doing it.

© 2006 Synopsys, Inc. (5) Commentary There are two distinct problems in C2RTL equivalence  (1) Ad hoc: one set of people construct the C models by hand and another set of people implement the C models in RTL  (2) Automated synthesis: C models made by-hand and RTL automatically derived from it. (1) is MUCH harder than (2).  We have done both. (1) takes more effort and requires information that is hard to get sometimes (e.g., proper and complete constraints).

© 2006 Synopsys, Inc. (6) Proposition Two Assertion/constraint – based verification has a poor cost/benefit ratio – so far. Caveats:  Some critical parts just have to have formal analysis to avoid disaster, e.g., bus controllers.  EDA companies now sell tools in this space and make some money from it but not a lot.  Development of methodologies and libraries of assertions help but still it is a hard sell.

© 2006 Synopsys, Inc. (7) Proposition Three ESL will happen because it has to. Case in point: the cellphone  Combines RF, audio (MP3), video, full- motion video, GPS, net access, PDA, security….  All of this has to be done with low power to conserve battery life.  Caveat: On the other hand cellphones often don’t work and aren’t life critical usually. Time to market dictates that Cellphones must be designed (and verified) quickly.

© 2006 Synopsys, Inc. (8) Commentary My friend and colleague Jin Yang (Intel) believes he has found a theoretical foundation for designing a modern microprocessor (out-of-order, speculative, superscalar, etc.) in a correct-by- construction, customizable and modular manner. This MIGHT be the effect on design in 2027 that will happen..

© 2006 Synopsys, Inc. (9) Last year’s prediction: Synthesizable TB Synthesizing testbenches is possible! It looks like Eve (and probably other emulation companies) have done a lot in this direction. Score one for me!

© 2006 Synopsys, Inc. (10) Predictions for 2027 The state of electronics may be so radically different from today that we may not recognize it. By 2027 pre-formally-verified IP will be the norm for designs.  Interfaces will be much cleaner  Properties well-understood and documented  Requirements will be more mathematically expressed

© 2006 Synopsys, Inc. (11) Predictions for 2027 Fabrication technology (power, speed, size, etc.), cost-effectiveness and feature set will continue to distinguish chips as they do today. Economics will continue to dominate the way electronics are designed and sold. Fab technology will often create new problems for mathematical analysis, e.g., verification under uncertainty of parts.

© 2006 Synopsys, Inc. (12) HL Design – Huge Research Opportunities Model Checking at the word & transaction level  Increased capacity?  Better environmental information? Equivalence verification to RTL Leverage SW checking techniques Coverage opportunities ….

© 2006 Synopsys, Inc. (13) Backup slides

© 2006 Synopsys, Inc. (14) Puzzle Fact 1: Verification accounts for 50% to 70% of the design resources (time, people, compute) on many chip projects. Fact 2: Verification tools make only a fraction of revenue compared with implementation tools (e.g., synthesis, place and route, DFM, etc.) in EDA.  FORMAL verification tools (including logic checking) make a VERY small fraction. WHY?