mpsoc 2003 mpsoc 2003 hardware dependent software hds
play

MPSoC 2003 MPSoC 2003 Hardware dependent Software (HdS). Hardware - PDF document

MPSoC 2003 MPSoC 2003 Hardware dependent Software (HdS). Hardware dependent Software (HdS). Multiprocessor SoC Aspects. Multiprocessor SoC Aspects. An introduction An introduction Frank Pospiech Alcatel Massy, France CTO Hardware


  1. MPSoC 2003 MPSoC 2003 Hardware dependent Software (HdS). Hardware dependent Software (HdS). Multiprocessor SoC Aspects. Multiprocessor SoC Aspects. An introduction An introduction Frank Pospiech Alcatel Massy, France CTO Hardware Coordination HdS Program Manager Frank.Pospiech@alcatel.de Outline Outline � Overview, Motivation � The HdS Concept � HdS for Multiprocessor SoCs � HdS R elated Standardization Efforts - VSIA MPSoC 2003 MPSoC 2003 Slide 2 of 74 / Slide of 74 / Frank Pospiech 1

  2. Acknowledgements Acknowledgements � Parts of this presentation are adapted from material provided by � Ian Philips, ARM � Roel Marichal, Alcatel � Sebastien Bocq, Alcatel � VSIA � I’d like to thank all of them for their very valuable contributions to this presentation � Thanks especially to all of my colleagues, who provided very useful comments when reviewing this presentation. MPSoC 2003 MPSoC 2003 Slide 3 of 74 / Slide of 74 / Frank Pospiech Outline Outline Overview, Motivation � Software Related issues in modern SoCs � The HdS Concept � A HW-SW Co-Development Process � HdS � Isn’t HdS Just Software? � HdS-API � HdS for Multiprocessor SoCs � MPSoC System � HdS Communication System � Distributed CORBA Application Management � HdS Related Standardization Efforts – VSIA � VSIA Overview � HdS-DWG Overview � DWG Status � MPSoC 2003 MPSoC 2003 Slide 4 of 74 / Slide of 74 / Frank Pospiech 2

  3. Overview Overview SoC Challenge SoC Challenge Yesterday’s system is today’s SoC! Today’s system is tomorrow’s component! Source: Source: Source: Bob Altizer, BASYS Bob Altizer, BASYS Bob Altizer, BASYS VSIA 2002 VSIA 2002 MPSoC 2003 MPSoC 2003 Slide Slide 5 of 74 / of 74 / Frank Pospiech Overview Overview Software Challenges for SoC Design Software Challenges for SoC Design Traditional Design System-on-Chip Design • Increased Design Complexity – Higher Integration • Ratio of Software to Hardware Engineers Increasing ( 2-5x) • Requirement to Port Software Across Various Processors & DSPs Source: Source: Source: Mike Kaskowitz, Mentor Graphics Mike Kaskowitz, Mentor Graphics • HW Design is Becoming More SW Focused Mike Kaskowitz, Mentor Graphics VSIA 2002 VSIA 2002 • Verification of SoC “Internals” Difficult • Application Software Needs to be Ported with Each New Generation MPSoC 2003 MPSoC 2003 Slide 6 of 74 / Slide of 74 / Frank Pospiech 3

  4. Overview. What’s the Problem? Overview. What’s the Problem? SoC complexity. SoC complexity. ARM Evidence ARM Evidence 1996: ~ 80 mm 2 on 0.5µ 1999: ~ 8 mm 2 on 0.25µ GSM 4KB D Cache Baseband ARM940T -Core ARM940T Control Chip GSM Base-Band ARM9TDMI Processor V.C. 4KB D Cache ARM940T Control 4KB I Cache ARM7TD MI ARM940T V.C. ARM9TDMI ‘Thumb’ 4KB I Cache ARM 7TD MI ‘Thu mb’ OAK DSP OAK Respectively 5 mm 2 and 2 mm 2 DSP Source: Source: Source: Ian Phillips, ARM Ian Phillips, ARM @ 0.12u “A fraction of a chip” Ian Phillips, ARM VSIA 2001 VSIA 2001 MPSoC 2003 MPSoC 2003 Slide Slide 7 of 74 / of 74 / Frank Pospiech Overview. What’s the Problem? Overview. What’s the Problem? The Productivity Gap The Productivity Gap r T G 1 r t M 0 0 1 Transistors/Chip (M) Transistor/PM (K) 20Mtr 800my 1,800my 8,500my ITRS’99 MPSoC 2003 MPSoC 2003 Slide 8 of 74 / Slide of 74 / Frank Pospiech 4

  5. Overview. What’s the Problem? Overview. What’s the Problem? Hardware is not the Hardware is not the whole whole System System !!! !!! The Productivity-Gap is a real issue … � But Hardware alone does not make a System! � … Hardware alone is no more than a Component. A Micro-Electronic System is the result of a projection of … � Architecture � Hardware � Software � … Distinguished by its gross Functional Behaviour ! Software is an important part of the Product and must be part � of the Design Process … or we are only designing a Component of the system. MPSoC 2003 MPSoC 2003 Slide Slide 9 of 74 / of 74 / Frank Pospiech Overview What’s the Problem? Overview What’s the Problem? Embedded System Challenges for HW Folks Embedded System Challenges for HW Folks � PARADIGM CHANGE! � Designers main tasks convert from processor integration to performance analysis . Concentration on functional requirements instead of integration work � Concentration on architectural exploration (including performance analysis � Re-use and Platform-based design become key! � Early validation of system/ solution correctness � Parallel hardware and software development � More effective use of previous work � Faster ways to build new elements of a solution � Ways to test more effectively, efficiently, and quickly MPSoC 2003 MPSoC 2003 Slide 10 Slide 10 of 74 / of 74 / Frank Pospiech 5

  6. Overview. What’s the Problem? Overview. What’s the Problem? Hardware is Hardware is Software Software An example Sub-System … � Reference BlueTooth Implementation :- � ARM core … 40K lines of RTL � 80K gates … 30K lines of RTL � 110KB binary … 70K lines of C total 140K source lines … Including Memory < 10% of Core Area at 0.1µ ! Source: Source: Source: Ian Phillips, ARM Ian Phillips, ARM Ian Phillips, ARM VSIA 2001 VSIA 2001 MPSoC 2003 MPSoC 2003 Slide 11 Slide 11 of 74 / of 74 / Frank Pospiech Overview. What’s the Problem? Overview. What’s the Problem? Verification & Software Gap Verification & Software Gap The Verification Gap � Kgates/ chip 100000 e t a c i b r Design a f o t Gap y 10000 t i i l b A Ability to design 1000 Verification Ability to verify Gap 100 10 1 1982 1986 1990 1994 1998 2002 2006 Source unknown The Software Gap : � “ The complexity of a System-on-Chip design is not only in the million transistors packed in a square millimetre. The major challenge for technical success of a SoC is to make sure that millions lines of software fit in with millions gates” Source : DAC2002 * * Going Mobile: The Next Horizon for Multi -million Gate Designs in the Semi-Conductor Industry, Christian BERTHET ( STMicroelectronics), DAC2002 MPSoC 2003 MPSoC 2003 Slide 12 Slide 12 of 74 / of 74 / Frank Pospiech 6

  7. Overview. What’s the Problem? Overview. What’s the Problem? Verification is a Verification is a Really Really -Big Issue Big Issue � ‘90% of chips work first time as Designed … ... Though only 50% work as R equired MEDEA R oadmap � Verification of Layout … N ot Enough Verification that it does what it was Designed to do … N ot � Enough � Verifying that it does what it is Required to do is part of the Design Process! � … And where System-Functionality is involved this includes the HW and the SW! MPSoC 2003 MPSoC 2003 Slide 13 Slide 13 of 74 / of 74 / Frank Pospiech Overview. What’s the Problem? Overview. What’s the Problem? Conclusions Conclusions Modern SoC designs involve much more than hardware � Verification software is increasingly on the critical path for � system deployment In addition to HW design reuse, there is a need to address � SW design reuse: IP = HW + SW + Methodology for re-use and verification It is useful to develop a standard abstraction for the software � that “sits directly on top” of the hardware… Hardware Dependent Software (HdS) as part of the Embedded SW . MPSoC 2003 MPSoC 2003 Slide 14 Slide 14 of 74 / of 74 / Frank Pospiech 7

  8. Outline Outline � Overview, Motivation � The HdS Concept � A HW-SW Co-Development Process � HdS � Isn’t HdS Just Software? � HdS-API � HdS for Multiprocessor SoCs � HdS R elated Standardization Efforts - VSIA MPSoC 2003 MPSoC 2003 Slide Slide 15 15 of 74 / of 74 / Frank Pospiech Development process investigations: Development process investigations: Co Co-design of HW and SW design of HW and SW Analysis & Analysis & Requirements Specification (power, area, speed, cost, …) Architecture Architecture Functional Requirements Performance Analysis Architectural Requirements (containing soft VC’s) (latency, throughput, S/N, utilization, etc.) Mapping: HW/ SW Partitioning, Scheduling, ... Mapping: HW/ SW Partitioning, Scheduling, ... Design Design Co-Design Interface Design Including SW Design HW Design (SW/ SW , HW/ SW, HW/ HW) Co-Verification Source: Source: Source: Roel Marichal Roel Marichal Roel Marichal System Integration and Test Alcatel 2002 Alcatel 2002 MPSoC 2003 MPSoC 2003 Slide 16 Slide 16 of 74 / of 74 / Frank Pospiech 8

  9. “ Hardware view” of Switch Fabric “ Hardware view” of Switch Fabric Programmable Devices Source: Source: Source: Roel Marichal Roel Marichal Roel Marichal Alcatel 2002 Alcatel 2002 MPSoC 2003 MPSoC 2003 Slide 17 Slide 17 of 74 / of 74 / Frank Pospiech A HW A HW-SW Co SW Co-Development Process Development Process SW organisation w.r.t Verification and Test SW organisation w.r.t Verification and Test Source: Source: Source: Roel Marichal Roel Marichal Roel Marichal Alcatel 2002 Alcatel 2002 MPSoC 2003 MPSoC 2003 Slide Slide 18 18 of 74 / of 74 / Frank Pospiech 9

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend