IP – Based Design Methodology

Slides:



Advertisements
Similar presentations
Design Methodology for Systems-on-Chip What is needed and what is not Daniel D. Gajski Center for Embedded Computer Systems University of California, Irvine.
Advertisements

A hardware-software co-design approach with separated verification/synthesis between computation and communication Masahiro Fujita VLSI Design and Education.
SoC Challenges & Transaction Level Modeling (TLM) Dr. Eng. Amr T. Abdel-Hamid ELECT 1002 Spring 2008 System-On-a-Chip Design.
SOC Design: From System to Transistor
Copyright  2003 Dan Gajski and Lukai Cai 1 Transaction Level Modeling: An Overview Daniel Gajski Lukai Cai Center for Embedded Computer Systems University.
ECE-777 System Level Design and Automation Hardware/Software Co-design
ECOE 560 Design Methodologies and Tools for Software/Hardware Systems Spring 2004 Serdar Taşıran.
Digital Design with VHDL Presented by: Amir Masoud Gharehbaghi
SpecC and SpecCharts Reviewed and Presented by Heemin Park and Eric Kwan EE202A - Fall 2001 Professor Mani Srivastava.
APPLICATION OF DESIGN PATTERNS FOR HARDWARE DESIGN Speaker: Prof. Vytautas ŠTUIKYS, Speaker: Prof. Vytautas ŠTUIKYS, Software Engineering Department, Kaunas.
Behavioral Design Outline –Design Specification –Behavioral Design –Behavioral Specification –Hardware Description Languages –Behavioral Simulation –Behavioral.
Copyright  2006 Daniel D. Gajski 1 Extreme Makeover of System Design Science Daniel Gajski Center for Embedded Computer Systems (CECS) University of California,
Copyright  1999 Daniel D. Gajski IP – Based Design Methodology Daniel D. Gajski University of California
1 Evgeny Bolotin – ICECS 2004 Automatic Hardware-Efficient SoC Integration by QoS Network on Chip Electrical Engineering Department, Technion, Haifa, Israel.
Real-Time System Requirements & Design Specs Shaw - Chapters 3 & 4 Homework #2: 3.3.1, 3.4.1, Add Error states to Fig 4.1 Lecture 4/17.
1 Embedded Computer System Laboratory RTOS Modeling in Electronic System Level Design.
(1) Introduction © Sudhakar Yalamanchili, Georgia Institute of Technology, 2006.
Role of Standards in TLM driven D&V Methodology
Web-based design Flávio Rech Wagner UFRGS, Porto Alegre, Brazil SBCCI, Manaus, 24/09/00 Informática UFRGS.
1 Chapter 2. The System-on-a-Chip Design Process Canonical SoC Design System design flow The Specification Problem System design.
I N V E N T I V EI N V E N T I V E EDA360 - Is End-to-End Design a Riddle, a Rebus, or a Reality? April 6, 2011.
Chap. 1 Overview of Digital Design with Verilog. 2 Overview of Digital Design with Verilog HDL Evolution of computer aided digital circuit design Emergence.
Voicu Groza, 2008 SITE, HARDWARE/SOFTWARE CODESIGN OF EMBEDDED SYSTEMS 1 Hardware/Software Codesign of Embedded Systems DESIGN METHODOLOGIES Voicu.
CAD Techniques for IP-Based and System-On-Chip Designs Allen C.-H. Wu Department of Computer Science Tsing Hua University Hsinchu, Taiwan, R.O.C {
Making FPGAs a Cost-Effective Computing Architecture Tom VanCourt Yongfeng Gu Martin Herbordt Boston University BOSTON UNIVERSITY.
Principles Of Digital Design Chapter 1 Introduction Design Representation Levels of Abstraction Design Tasks and Design Processes CAD Tools.
Intro to Architecture – Page 1 of 22CSCI 4717 – Computer Architecture CSCI 4717/5717 Computer Architecture Topic: Introduction Reading: Chapter 1.
Extreme Makeover for EDA Industry
New Strategies for System Level Design Daniel Gajski Center for Embedded Computer Systems (CECS) University of California, Irvine
System Design with CoWare N2C - Overview. 2 Agenda q Overview –CoWare background and focus –Understanding current design flows –CoWare technology overview.
High Performance Embedded Computing © 2007 Elsevier Chapter 1, part 2: Embedded Computing High Performance Embedded Computing Wayne Wolf.
COE 405 Design and Modeling of Digital Systems
VLSI DESIGN CONFERENCE 1998 TUTORIAL Embedded System Design and Validation: Building Systems from IC cores to Chips Rajesh Gupta University of California,
- 1 - EE898_HW/SW Partitioning Hardware/software partitioning  Functionality to be implemented in software or in hardware? No need to consider special.
Design & Co-design of Embedded Systems Next Step: Transaction-Level Modeling Maziar Goudarzi.
Business Trends and Design Methodologies for IP Reuse Allen C.-H. Wu Department of Computer Science Tsing Hua University Hsinchu, Taiwan, R.O.C {
SpecC stands for “specification description language based on C”.
CprE 588 Embedded Computer Systems Prof. Joseph Zambreno Department of Electrical and Computer Engineering Iowa State University Lecture #5 – System-Level.
1 Copyright  2001 Pao-Ann Hsiung SW HW Module Outline l Introduction l Unified HW/SW Representations l HW/SW Partitioning Techniques l Integrated HW/SW.
System-on-Chip Design Hao Zheng Comp Sci & Eng U of South Florida 1.
EMT 351/4 DIGITAL IC DESIGN Week # 1 EDA & HDL.
System-on-Chip Design
Andreas Hoffmann Andreas Ropers Tim Kogel Stefan Pees Prof
ASIC Design Methodology
Combinational Logic Design
Digital System Design An Introduction to Verilog® HDL
COMPUTATIONAL MODELS.
EEE2135 Digital Logic Design Chapter 1. Introduction
APPLICATION OF DESIGN PATTERNS FOR HARDWARE DESIGN
System On Chip - SoC E.Anjali.
FPGAs in AWS and First Use Cases, Kees Vissers
Chapter 1: Introduction
Yogesh Mahajan, Sharad Malik Princeton University
Design Flow System Level
Hardware Description Languages
Embedded systems, Lab 1: notes
ECE-C662 Introduction to Behavioral Synthesis Knapp Text Ch
VHDL Introduction.
HIGH LEVEL SYNTHESIS.
CprE 588 Embedded Computer Systems
Professor Ioana Banicescu CSE 8843
system specification description language based on C (SpecC)
CS 153 Logic Design Lab Professor Ian G. Harris
Mark McKelvin EE249 Embedded System Design December 03, 2002
Abstract RTOS Modeling for Embedded Systems
Transaction Level Modeling: An Overview
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Synchronization Verification in System-Level Design with ILP Solvers
Digital Designs – What does it take
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Presentation transcript:

IP – Based Design Methodology Daniel D. Gajski University of California gajski@uci.edu http://www.ics.uci.edu/~gajski

Outline Drivers of IP business Obstacles to IP success Possible solutions Business models Future

IP Drivers Product complexity Market pressure Expertise shortage Productivity gap Business model

Solving Complexity / Productivity Problems IP 1. IP 2. 3. IP 4. IP

Obstacles to IP Success Partially abstracted design process Simulation based design flow Simulation models are not easily synthesizable IP definition (parameterization, verification, characterization) IP-centric models for SOC No separation of computation and communication Need for encapsulation Reuse automation IP do not fit into past methodologies and tools IP-centric methodology No clearly defined business models Volume, value-added and protection

Solving Complexity / Productivity Problems Higher level of abstraction Specification Architecture Communications Components (IP) Tools and methodologies Standardization Languages Models Protocols Documentation (IP)

Simulation Based Design Flow Simulatable but not synthesizable 3.415 2.715 case X is when X1 => when X2 => Finite State Machine Table Lookup Controller Memory

IP Definition Quality, verification, characterization vs. parameterization Quality, Verifiability, Testability, Characterizability 1 single instance No. of parameters, Generality

RTL Specs FSM FSMD S1 S1 S2 S2 S3 S3 x = 0 y = 0 ... count = n x = 0 temp1 = a(i) + b(i) temp2 = c(i) + d(i) count = count - 1 S2 S2 Count ¹ 0 Count ¹ 0 x = 1 y = 0 ... S3 S3 s(i) = temp1 * temp2 Count = 0 Count = 0 FSM FSMD

Processor (controller & datapath) RTL Architectures Inputs Control Data Count D Q FF State reg. or PC Mem Mem RF RF RF . . . Outputs D Q FF +/- + temp1 temp2 Input logic State reg. Ouput logic Controller Datapath Control Data Controller Processor (controller & datapath)

variable A: array[1..20] of integer IP-centric Specs S1 Y variable A: array[1..20] of integer C Program ………….. A D B variable i, max: integer; max = 0; for i = 1 to 20 do if (A[i] > max) then max = A[i]; end if; end for; S2 e1 e2 C S3 e3 SFSMD Concurrent, hierarchical SFSMD

IP-centric Architecture Control Processor SR/PC Mem RF RF IP Processor IP IP IP IP IP Ctrl DP Ctrl DP temp1 temp2 Controller Datapath IP-centric processor IP-centric system

IP-Centric Models Present IP Future B T C W IP

Reuse Explorations Behavior IP Channel IP synthesizable behavior PE replicable T IP at any time synthesizable behavior wrapped IP behavior transducer Channel IP at any time virtual channel channel with IP protocol C IP replicable

Reuse Optimization Wrapper Resolution (a) Two synthesizable behaviors connected by a channel A B A B C (b) Synthesizable behavior connected to an IP A A W IP IP (c) IP connected through an incompatible channel A T C W IP B T A T IP

CAD Methodology Capture – Simulate (60’s – 80’s) Describe – Synthesize (80’s – 00’s) Specify-Explore-Refine (00’s – 20’s)

Past, Present and Future Capture & Simulate Describe & Synthesize Specify, Explore & Refine Executable Spec Functionality Specs Specs Algorithms Algorithms (software) Algorithms Connectivity Architecture Protocols Communications Describe Design Design Design Timing Logic Simulate Logic Logic Simulate Physical Physical Physical Manufacturing Manufacturing Manufacturing

Present and Future Issues Describe & Synthesize Specify, Explore & Refine Manufacturing Describe Simulate Specs Algorithms (software) Physical Logic Design Executable Spec Functionality Issues: IP vs EDA Semi’ vs. Systems Simulation vs. Synthesis Hardware vs. Software VHDL vs. C Top-down vs. Bottom-up Integrated vs. Outsourced CE vs. CS Algorithms Connectivity Architecture Protocols Communications Design Timing Logic Physical Manufacturing

Analysis and validation flow SpecC Methodology Specification model IP SW synthesis HW Manufacturing Validation of algorithm and functionality Estimation Simulation Communication Architecture Implementation functionality and synchronization communication timing and performance Synthesis flow Analysis and validation flow Architecture exploration

Business Model Product, Knowledge System house IP EDA Providers vendors Design house Integrators Commodity IPs, Standard IPs, Star IPs Tools, Libraries Manufacturing Technology, Libraries

Scenario 1: Design world Business Model Product, Knowledge System house IP providers EDA vendors Design house Integrators Tools, Libraries, Commodity IPs, Standard IPs Star IPs Manufacturing Technology Scenario 1: Design world

Scenario 2: Split Design Business Model Product, Knowledge System house Design house IP providers EDA vendors Integrators Tools Star IPs Manufacturing Technology, Libraries, Commodity IPs, Standard IPs Scenario 2: Split Design

Scenario 3: IP Providers World Business Model Product, Knowledge, Assembly System house IP Providers EDA vendors Standard IPs, Star IPs, Commodity IPs Tools, Libraries Manufacturing Technology, Libraries Scenario 3: IP Providers World

Scenario 4: Systems world Business Model Product, Knowledge System house IP providers EDA vendors Tools, Libraries, Commodity IPs, Standard IPs Star IPs Manufacturing Technology Scenario 4: Systems world

Top-down vs. Bottom-up Spec Spec Real Comp. (hard) Virtual Comp. (soft) Layout Layout Manuf. Manuf.

Reuse Paradigm New Languages, guidelines, extensions Models for exploration (spec, arch, comm, RTL) Separation of computation & communication Encapsulation IP automation standards Reuse automation (Synthesis with reuse) IP-centric methodology

Conclusion