1 / 58

The Chip Design Crisis

The Chip Design Crisis. Univ.-Prof. Dr.-Ing. Markus Rupp June,2 2008. Outline. Why Mobile Communications? Problems in the Design of Wireless Systems Complexity Gap Design Productivity Gap Problems and Solutions Parallelism, IP-Reuse, Predictive Design

Download Presentation

The Chip Design Crisis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. The Chip Design Crisis Univ.-Prof. Dr.-Ing. Markus Rupp June,2 2008

  2. Outline • Why Mobile Communications? • Problems in the Design of Wireless Systems • Complexity Gap • Design Productivity Gap • Problems and Solutions • Parallelism, IP-Reuse, Predictive Design • Inconsistent Design, Lack of Tool Support, Refinement Techniques, Design Languages, Automatic HW/SW Partitioning • Virtual Prototyping, Automatic Testing and Verification, Automatic Float to Fix Conversion • Static Code Analysis, automatic DFG and CFG Generation, Code Understanding and Interpretation • Low Power and Power aware Designs • Software Defined Radio • Conclusions

  3. Why Mobile Communications? • Communication is a deep, human requirement • In particular in oral form • We would like to speak with arbitrary persons any time at any location.

  4. Mobile communication of the past • C-Netz Autotelefonnetz C • Start Nov.1984 • First only in automobiles (later portable 10 kg) • Starting price ca. 50.000 öS • First fully automatic mobile cellular net (radius about 15 km)

  5. How do we communicate today? • GSM • Developed to support speech only (intro Austria in 94) • Although, today also SMS (in Austria 95) and with GPRS also data transmission possible. • UMTS • Supports equally speech and various data services • Even Multimedia Application with Video Streaming • WLAN • Originally planned as pure data communication (Internet) • Supports also speech services (VoIP)

  6. Is Mobile Communication successful? Until selling of one Million units, it took…

  7. Is Mobile Communication successful?http://www.rtr.at/en/tk/TeilnehmerstaendeMF2007 9,7 9,6 8,4 User in Austria in Millions 2006 2006 2005

  8. What makes Mobile Communications a difficult task? • Limited Spectrum • Most of Spectrum is used by ORF!

  9. Spectrum

  10. What makes Mobile Communications a difficult task? • Limited Spectrum • Most of Spectrum is used by ORF! • Limited Battery Power • Battery increases with 2% per year

  11. Power Handy requires only 0,000 000 000 000 1 Watt for reception!

  12. What makes Mobile Communications a difficult task? • Limited Spectrum • Most of Spectrum is used by ORF! • Limited Battery Power • Battery increases with 2% per year • Multi-path propagation

  13. Multi Path Propagation

  14. Multi Path Propagation

  15. What makes Mobile Communications a difficult task? • Limited Spectrum • Most of Spectrum is used by ORF! • Limited Battery Power • Battery increases with 2% per year • Multi-path propagation • Complexity

  16. Complexity Gap in 3rd G. Wireless Processor Performance (Moore)

  17. Design Productivity Gap Transistors per Chip (M) Productivity Trans./Staff - Mo. 10,000 100,000,000 1,000 10,000,000 .10m 58%/Yr. compound Complexity growth rate 100 1,000,000 10 100,000 .35m 1 10,000 x x 1,000 .1 x x x x x x 100 21%/Yr. compound Productivity growth rate .01 2.5m 10 .001 1991 1999 2001 2003 2007 1989 1993 1995 1997 2005 2009 1983 1985 1987 1981 Logic Tr./Chip Source: SEMATECH Tr./S.M.

  18. Some Observations in 3rd Generation Wireless • Today, about 70% of development time is verification. • 90% of the product cost are predetermined by its detailed specification. • Standards (UMTS R99 in Dec.1999, R4 in March 2001,R5 in March 2003, R6 (Dez 04), R7 (Sep 05), R8 (Nov 07?). change faster than the product design cycle. • The required time to market becomes decisive: launching six months early, triples profits, six months late results in breaking even.

  19. Sematech‘s Answer (1999) • For every $1 invested in EDA tools, an additional $2 to $5 are spent on integration into the design flow. • No EDA vendor or using company can supply all the tools needed today. • Promote rapid integration of new tools from industry and university research. • Create Chip Hierarchical Design System technical standard (CHDStd) • This has not happened until today!

  20. Outline • Why Mobile Communications? • Problems in the Design of Wireless Systems • Complexity Gap • Design Productivity Gap • Problems and Solutions • Parallelism, IP-Reuse, Predictive Design • Inconsistent Design, Lack of Tool Support, Refinement Techniques, Design Languages, Automatic HW/SW Partitioning • Virtual Prototyping, Automatic Testing and Verification, Automatic Float to Fix Conversion • Static Code Analysis, automatic DFG and CFG Generation, Code Understanding and Interpretation • Low Power and Power aware Designs • Software Defined Radio • Conclusions

  21. Problems and Solutions • Solutions to the Complexity Problem: • Predictive Design • Parallelism • Hardware Accelerators • Re-using IP • = “Classical Approaches”

  22. Problems and Solutions • Solutions to the Design Productivity Problem: • No Solutions currently in Products • Multitude of Problems exist:

  23. System-Design Marketing Research Implementation Inconsistent Design

  24. High Level of abstraction Low Lack in Tool Support Ptolemy

  25. Lack in Tool Support • A multitude of EDA Tools exists already . • However, they all cover only a certain part of the design flow. • Major disadvantage of existing EDA Tools: not compatible to each other! • Basic lack exists in: • HW/SW/FW partitioning • Platform based designs • Float-to-Fix conversion • Power aware design at High Level description

  26. Dream: Consistent Design Flow

  27. Dream: Consistent Design Flow • Can be achieved... • Via a single design representation covering all design steps equally • Via one-code paradigm • Via refinement steps • Via closing the tool gap...

  28. Open Tool Integration Environment (OTIE)

  29. Design Database (DBB) Internal View • For static code analysis • property tables, • process table, • and basic block tables • of the DDB are used.

  30. Automatic HW/SW Partitioning Example Delay Profile Estimator (a UMTS receiver component) Cost = ρCostCC + (1- ρ) CostGC ρ = 0.68 .. 0.7 We basically achieved the same result as well-trained design group We needed about 6 seconds!

  31. Outline • Why Mobile Communications? • Problems in the Design of Wireless Systems • Complexity Gap • Design Productivity Gap • Problems and Solutions • Parallelism, IP-Reuse, Predictive Design • Inconsistent Design, Lack of Tool Support, Refinement Techniques, Design Languages, Automatic HW/SW Partitioning • Virtual Prototyping, Automatic Testing and Verification, Automatic Float to Fix Conversion • Static Code Analysis, automatic DFG and CFG Generation, Code Understanding and Interpretation • Low Power and Power aware Designs • Software Defined Radio • Conclusions

  32. Algorithmic Design Architectural Design HW Realisation SW Implementation FW Development Algorithmic Design Architectural Design VP Implementation HW Realisation SW Implementation FW Development Algorithmic Design Architectural Design VP Implementation HW Realisation SW Implementation FW Development Virtual Prototyping (1)

  33. HW/SW Interface VP Virtual Prototyping (2) • Virtual Prototype: • Whole system behavior can be tested via simulation • but not as fast as having a prototype available • After HW is available, VP can be replaced SW/FW HW

  34. System bus Direct I/O Supporting Platform Based Designs in VP . . . DMA DSP RAM . . . HA1 HA2

  35. Automatic VP Generation Environment

  36. Results of Industrial Deployment Design effort for manual VP creation [Person-hours] Total = 144 person-hours A matter of seconds!!!

  37. Verification (1) Today, about 70% of development time is verification

  38. Verification (2) • With such high complexity, a complete verification on every level is not possible! • The higher the design level, the faster the simulation time • Run all but one module (DUT) on highest possible design levels. • Generate test vectors automatically for all design levels.

  39. Direct I/O Bus Automatic Test Pattern Reuse Registers Memory HA1 HA2 Memory image …  DSP DMA C test program

  40. Float SDI Generation Optimisation Hybrid Evaluation Float/Fixed Conversion Environment SSD SSD

  41. Float to Fix Conversion Results {16} {8,16,32}

  42. Float to Fix Conversion Results

  43. Outline • Why Mobile Communications? • Problems in the Design of Wireless Systems • Complexity Gap • Design Productivity Gap • Problems and Solutions • Parallelism, IP-Reuse, Predictive Design • Inconsistent Design, Lack of Tool Support, Refinement Techniques, Design Languages, Automatic HW/SW Partitioning • Virtual Prototyping, Automatic Testing and Verification, Automatic Float to Fix Conversion • Static Code Analysis, automatic DFG and CFG Generation, Code Understanding and Interpretation • Low Power and Power aware Designs • Software Defined Radio • Conclusions

  44. Process Graph Representation Process (CFG) Basic Block (DFG) a b c z • Process is represented as CFG • One Basic Block consists of a DFG

  45. Control Flow Graph of an FIR Filter

  46. CFG Example • E.g. function of aDelay Profile Estimator • Basic Blocks and function are annotated with properties • Operations +,-,* • Control if, jmp • Loop counter

  47. 7 - 20X 2 – 5X 20 – 50 % Power Aware Design POWER REDUCTION OPPORTUNITIES SYSTEM LEVEL BEHAVIORAL LEVEL RT LEVEL LOGIC LEVEL TRANSISTOR LEVEL LAYOUT LEVEL

  48. Power Reduction • Dynamic Methods • Sleep modes • Dynamic frequency scaling (DFS) • Dynamic voltage scaling (DVS) • Reducing Switching Activity • Clock gating • Minimization of glitches • Reducing number of operations • Adapting Process Technology • Reducing capacitance • Reducing leakage current • Reducing supply voltage

  49. Outline • Why Mobile Communications? • Problems in the Design of Wireless Systems • Complexity Gap • Design Productivity Gap • Problems and Solutions • Parallelism, IP-Reuse, Predictive Design • Inconsistent Design, Lack of Tool Support, Refinement Techniques, Design Languages, Automatic HW/SW Partitioning • Virtual Prototyping, Automatic Testing and Verification, Automatic Float to Fix Conversion • Static Code Analysis, automatic DFG and CFG Generation, Code Understanding and Interpretation • Low Power and Power aware Designs • Software Defined Radio • Conclusions

  50. Software Defined Radio • What is the next step in direction automatic chip design? • Software design is cheaper than Hardware design (also faster). • Why not designing a new and very flexible HW platform, so flexible that algorithmic descriptions can directly be run on it runtime reconfigurable HW?

More Related