1-Embedded Systems An Introduction-R
1-Embedded Systems An Introduction-R
Lecture # 1
Reference
Embedded System Design
Vahid / Givargis
What is an Embedded System
Special-purpose
Typically designed to
Tightly constrained
Low cost
Simple systems
enough
Minimum power
embedded systems is
often called firmware
Is stored in read-only
Design
Implementation
Maintenance
Challenges
Diversity of operating environments and platforms
Opportunities
Open Software Development i.e. Use of embedded
Computing performance
In a real time embedded control environment is not simply an
instructions- per-second rating.
While raw computational performance is important, other
Working conditions, such as priority, allocated time and
memory or signals availability may change.
Thus, complexity, structure and basic properties of
anymore.
Validation and certification.
Any embedded control system should be proved to be
Optimized datapath
Benefits
Some flexibility
Energy efficiency
Ubiquitous Computing
System On Chip
Network on Chip
Sizing transistors
Routing wires
Benefits
Excellent performance, smallest size, low power
Drawbacks
Features
Lower layers are fully or partially built
Features
Instead of designing the actual silicon, the designer
uses pre-built “blocks” that have already been tested
and proven.
Benefits
Good performance, good size, less NRE cost than a
full-custom implementation (perhaps $10k to $100k)
Drawbacks
Still require weeks to months to develop
Drawbacks
Bigger, expensive (perhaps $30 per unit), power
hungry, slower
Basic tradeoff
General vs. custom
Co Design Ladder
12/08/21 Embedded Systems Spring 2011 Shaftab Ahmed 36
Conclusion Revisiting