21
Solving the System-Level Design Riddle

2014 12-10 aimee

Embed Size (px)

Citation preview

Page 1: 2014 12-10 aimee

Solving the System-Level Design Riddle

Page 2: 2014 12-10 aimee

q  This webinar will be available afterwards at www.designworldonline.com & email

q  Q&A at the end of the presentation q  Hashtag for this webinar: #DWwebinar

Before We Start

Page 3: 2014 12-10 aimee

Moderator Presenter

Aimee Kalnoskas Design World/EE

Randy Smith Sonics Inc.

Page 4: 2014 12-10 aimee

Solving the System-Level Design Riddle

December 2014

Page 5: 2014 12-10 aimee

What is the System Design Riddle?

How do I complete my design on-

time?

On-budget?

With no errors?

Sooner

With higher performance

In less area

Sooner? Sorry, I meant early…

…maybe you can drop a feature?

Then marketing says they need it…

Page 6: 2014 12-10 aimee

What’s wrong? Waterfall Methodologies

•  Sequential operations o  Little parallelism

•  Changes in one phase may result in a reset of all downstream steps

•  While design reuse (and use of purchased IP) is allowed, it cannot be fully exploited

•  If one feature is causing a delay, it may be impossible to move forward with the rest of the design until it is resolved

•  In general, the focus is on the process, rather than the desired outcome

It’s easy to see the problems with the waterfall method. It assumes that every requirement can be identified

before any design or coding occurs.

Specification

Prototype

Design

Simulation Verification Emulation

Physical Design

Software

Page 7: 2014 12-10 aimee

Reasons for Changing IC Methodology

Desired new attributes •  Ability to make reasonable progress with

an incomplete specification •  To better solve modern design challenges:

o  Time-to-market o  Power o  Security

•  Ability to easily ship “on-time”/early with a reduced feature set

•  Improved relationship between architectural, logical, physical, and software design

Some drivers for change •  Consumer products

o  Short release cycle o  Low power, but still always on o  Security o  Design costs

•  IoT o  Starting design without a complete spec

•  Makimoto’s wave shifts emphasis from standardization to customization

•  System companies are in best position to assume product risk

Page 8: 2014 12-10 aimee

Why is Sonics leading this?

0

50

100

150

200

250

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

1998

1999

2000

2001

2002

2003

2004

2005

2006

2007

2008

2009

2010

2011

2012

2013

2014

*

2015

*

2016

*

2017

*

2018

*

Avg,

Num

ber o

f IP

Bloc

ks

Perc

ent o

f Reu

se

Percent of Reuse Avg. Number of IP Blocks

Source: Semico Research Corp.

Page 9: 2014 12-10 aimee

Why is Sonics leading this?

$0

$20

$40

$60

$80

$100

$120

$0

$10

$20

$30

$40

$50

$60

$70

90nm 65nm 45nm / 40nm 32nm / 28nm 20nm 14nm* 10nm*

Tota

l M D

olla

rs

M D

olla

rs

Silicon IP Integration Cost Software IP Integration Cost Total IP Integration Cost

Source: Semico Research Corp.

Page 10: 2014 12-10 aimee

SoC Architects Drive Both SW & HW

•  Large (and growing) teams dependent upon architecture

•  SoC architect responsible for many views of architecture o  Normally disparate

•  Increasing complexity of SW and HW results in increased costs and delays

HW

SW Development of HW-independent SW

Dev. of HW-dependent SW and system architecture exploration

Performance analysis architecture validation and

RTL verification and implementation

Page 11: 2014 12-10 aimee

Worth considering: Agile SW Development

•  The Agile Manifesto was written in February of 2001, at a summit of seventeen independent-minded practitioners of several programming methodologies. The participants didn't agree about much, but they found consensus around four main values: o  Individuals and interactions over processes and tools o  Working software over

comprehensive documentation o  Customer collaboration over

contract negotiation o  Responding to change over

following a plan

Requirements

Architecture & Design

Development

Test & Feedback

“The Agile movement proposes alternatives to traditional project management. Agile approaches are typically used in software development to help businesses respond to unpredictability.”

Page 12: 2014 12-10 aimee

HW and IC Design Teams Must Evolve

Yesterday Tomorrow

Component-Level Aggregation System-Level Architecture

One-time Usage Platform Reuse

Hierarchical Requirements and Stepwise Design Management

Concurrent Engineering and Agile IC Methodology

Dedicated Resources Shared Resources

Page 13: 2014 12-10 aimee

What an Agile IC Methodology Might Look Like

Specification

Prototype

Design

Simulation Verification Emulation

Physical Design

Waterfall Time

Page 14: 2014 12-10 aimee

What an Agile IC Methodology Might Look Like

Specification

Prototype

Design

Simulation Verification Emulation

Physical Design

Agile IC Methodology

Time

Change the slope! The more vertical the

better!

Page 15: 2014 12-10 aimee

•  Sonics’ on-chip networks help leading SoC designers solve some of the most difficult challenges in SoC design

•  Sonics System IP: On-chip Networks, Memory Subsystem, Power Partitioning & Management, Performance Monitor & Debug, Security Firewalls

How Sonics helps

Development costs

IP Integration

High Frequency

Memory Throughput

Physical Design

Power Management

Security

Time-to-market

Cortex-A15

Cluster

Cortex-A7

Cluster

Mali-T658

Cluster

CCI-400VideoEngine

VideoEncode

Cam2

Cam1

DMA

DisplayCtrl.

US

B1

US

B2

DR

AM

Ch.

1D

RA

MC

h. 2

On-

die

SR

AM

US

B3

US

BO

TG

E-net

Audio

SATA UFSSD/CF/

MMCHSIPCIe

HDMI

On-

die

RO

MP

erip

hera

ls

A2x2

G4x1

J3x1

F4x1

E4x1

H5x2

C2x3

SecurityEngine

M MMM

M M M M MMMS M

S

MM

MM

MM

M

SS

B2x3

SS

M S128 128

128

32

T

128T

128T

64T

I T I I I I

I

I

I

I

I

I

I

I

IT I I IIII

32 646432

64

64

3232 32 32 64646464

1333 MHz 1066 MHz 533 MHz

533

MH

z

267 MHz 267 MHz133 MHz267 MHz

267 MHz

64

64

64

64

64

64

133 MH

z133 M

Hz

133 MH

z133 M

Hz

400 MH

z200 M

Hz

200 MH

z

133 MHz 133 MHz 133 MHz 133 MHz133 MHz267 MHz 267 MHz

133

MH

z53

3 M

Hz

533

MH

z53

3 M

Hz

133

MH

z

DDR32133

DDR32133

IPC

ontro

lS

32T

133

MH

z

M128

I

D1x3

I4x1

T

Power DomainBoundary

SonicsGNRequestNetwork

Page 16: 2014 12-10 aimee

Sonics – The NoC Leader for 18 Years

•  Sonics enables designers to integrate any IP from anywhere, anytime o  Easy IP re-use o  Connecting third party IP/subsystems

•  Total System IP approach: o  Intelligent memory scheduling o  Optimal power-aware designs o  Data flow services: QoS, Security firewalls o  Software drivers

•  Commanding presence in digital entertainment, mobile and wireless o  200+ SoC tape-outs

•  Results: 2.5B+ units shipped o  138+ patent properties o  Improved TTM and quality

Page 17: 2014 12-10 aimee

Does Sonics Solve the Riddle?

•  No, not entirely o  Using Sonics and other high-quality IP will aid greatly o  But there are limitations that good IP alone doesn’t

solve •  Your design methodology is probably wrong,

though it may be the best you can do today

Page 18: 2014 12-10 aimee

Short term actions How you can help •  Join the LinkedIn group •  Participate in the

conversation •  Invite others to get involved

too

Sonics’ Plan •  Get the discussion started •  Create the communications

links •  Gather the interested parties

Step 1: Join the “Agile IC Methodology” group on LinkedIn Step 2: Join the conversation – participate!

Page 19: 2014 12-10 aimee

Agile IC Methodology Progress

•  Group went live on October 1, 2014… o  +280 members joined o  +50 different companies represented in the group o  20 discussions threads

•  Don’t miss out! Join Agile IC Methodology group today!

Page 20: 2014 12-10 aimee

Questions? Aimee Kalnoskas Design World/EE [email protected]

Randy Smith Sonics Inc [email protected]

Page 21: 2014 12-10 aimee

Thank You q  This webinar will be available at

designworldonline.com & email

q  Tweet with hashtag #DWwebinar

q  Connect with Design World

q  Discuss this on EngineeringExchange.com