Electronic Design Automation- The Next 50 Years

hourglassjurorΜηχανική

5 Νοε 2013 (πριν από 3 χρόνια και 7 μήνες)

98 εμφανίσεις

3
Axel Jantsch
Royal Institute of Technology, Stockholm
June 6, 2001
Is the Evolution of EDA Predictable?
4
Axel Jantsch
Royal Institute of Technology, Stockholm
June 6, 2001
Implementation Technology
years
50
25
40
35
30
45
now
15
10
5
20
5
Axel Jantsch
Royal Institute of Technology, Stockholm
June 6, 2001
EDA Evolution
m EDA has its own
technological evolution
m It also depends inherently
on implementation
technology
Õ e.g. FPGA
Õ e.g. deep submicron
effects
Õ System-on-Chip
challenges
years
50
25
40
35
30
45
now
15
10
5
20
Implementation
technology
EDA evolution
6
Axel Jantsch
Royal Institute of Technology, Stockholm
June 6, 2001
Weather Forecast revisited
7
Axel Jantsch
Royal Institute of Technology, Stockholm
June 6, 2001
Patterns and Trends in EDA
m Design entry moves towards application concepts
m Design methodologies are organized in layers
m A strong need for automation
m Well understood steps can always be automated
8
Axel Jantsch
Royal Institute of Technology, Stockholm
June 6, 2001
EDA Entry Moves towards Applications
years
2020
2010
2000
1970
1980
1990
S
t
i
c
k

d
i
a
g
r
a
ms

a
n
d

l
a
y
o
u
t
B
o
ol
e
an

e
q
u
at
i
o
n
s

an
d



r
e
g
i
s
t
er
t
r
a
n
s
f
er
s
A
l
g
o
r
i
t
hm
s
D
o
m
ai
n

sp
eci
f
i
c
l
an
g
u
a
g
es
N
e
t
l
i
s
t
s
9
Axel Jantsch
Royal Institute of Technology, Stockholm
June 6, 2001
Layers of Design Methodologies
Requirements definition
System design
Implementation and coding
Manufacturing
Design is organized in layers for
2 reasons:
m To handle complexity
m To reuse
m FPGAs ?
m Deep submicron effects?
m System-on-Chip challenges?
10
Axel Jantsch
Royal Institute of Technology, Stockholm
June 6, 2001
Degree of Automation Increases
A design task is automated whenever possible because
m It is faster
m It is cheaper
m It is more reliable
m Types of automation:
Õ Synthesis
Õ Reuse
Design entry
11
Axel Jantsch
Royal Institute of Technology, Stockholm
June 6, 2001
The Price of Automation
m Well understood tasks
can always be automated
m Automation always
comes at a price
+ Design process is
fast
+ Design process is
cheap
+ Design process is
reliable
- Product is expensive
- Product is slow
- Product is not
optimal
M
a
n
u
a
l
Automated
Product
Design entry
M
a
nu
a
l
Automated
Product
Design entry
12
Axel Jantsch
Royal Institute of Technology, Stockholm
June 6, 2001
Product Development in 2050
m Design entry is based on functionality seen by the user
m Marketing people and users are system designers
m Time from idea to market is 1 month
m Complete automation from design entry to
manufacturing
m The design process is very stable except hot spots
m The design process is mostly independent of
implementation technology
m Human designers will do:
Õ Optimize critical parts
Õ Support and develop the design process
Õ Accommodate changing implementation technology
13
Axel Jantsch
Royal Institute of Technology, Stockholm
June 6, 2001
+
Example Product Development
+
For Kids 6-10 years
Pure voice, no data, no web
Local phone calls only
5 emergency numbers
Reliable voice recognition
Toy like shape and colours
Can be located
Robust
Cheap
+
10 kr
Product manager
Pockephone
(50 kr)
14
Axel Jantsch
Royal Institute of Technology, Stockholm
June 6, 2001
Product Development
Add system functions
and services (IPs)
System estimation
Synthesize interfaces
and overall control
Manufacturing
m System functions and
services are future
Intellectual Property blocks
(IPs).
m IPs are described in
standardized notations
allowing mixing, interfacing
synthesis, and validation.
m Trade-offs are done in terms
of system level functionality,
cost and performance
factors.
Detailed estimation
15
Axel Jantsch
Royal Institute of Technology, Stockholm
June 6, 2001
Summary - Main Conclusion
m Long term trends:
Õ Design entry moves towards applications
Õ Layered methodologies shield against impacts from
implementation technology
Õ There is both a demand for and possibility of
automation
m The overall design methodology will mature and
stabilize
m System design will depend less on implementation
technology
m The EDA tool chains and design methodologies will only
evolve and grow over the decades
16
Axel Jantsch
Royal Institute of Technology, Stockholm
June 6, 2001
Summary - System Design in 2050
m Product managers and end users will be system
designers
m Design entry will be based on configuration of end
user functions
m The design and synthesis tasks will essentially be the
integration of functionality modules and system
features