Unit 3
Unit 3
SYSTEM
What is an embedded system
• An embedded system is an electronic/electro-
mechanical system designed to perform a
specific function and is a combination of both
hardware and firmware (software)
• An embedded system is some combination of
computer hardware and software, either fixed
in capability or programmable, that is
specifically designed for a particular function.
EMBEDDED SYSTEM
communication
MEMORY interface
Other
supporting
IC s and
subsystem
s
CORE OF THE EMBEDDED SYSTEM
• The core of the embedded system falls in to
any one of the following categories
1. general purpose and domain specific
processors ( µp, µC, DSP )
2. ASIC(Application specific IC)
3. programmable logic devices (PLD)
4. commercial off-the-shelf components
(COTS)
GPP vs. ASIP
• General purpose processor :
Designed for general computational tasks
E.g.. Processor in the laptop
High volume production
Unit cost for a chip is low
• ASIP instruction set and architecture optimized
to specific application
• ASIP arises when the GPP are unable to meet the
application needs
Formalization of System Design using
Top – Down approach
• Requirements and Specifications of
hardware and software
• Define architectures of hardware and
software
• Coding and implementation as per
architecture
• Testing, validation and verification of
system
Diagrammatic model - UML (Universal
Modeling Language)
• Conceptual design modeling
• Classes and Objects to describe identity,
attributes, components and behaviour
– Inheritances in classes and objects
– Interfaces with the objects and their
implementation in the objects,
• Structural description of the design
components
Behavioral description in terms of
states, state machine and signals
Events description
Characteristics of an embedded
system
• Unlike general purpose computing system, embedded system
posses certain specific characteristics and these are unique.
Application and domain specific: embedded systems are developed
to do the intended functions only
• They can not be used for any purpose
• You can not replace an embedded control unit developed for a
particular domain say telecom with another control unit designed
to sey another domain like consumer electronics
Reactive and real time: emb.sys. are in constant interaction to the
real world
• Any changes happening in the real world (event)are captured by
the sensors or i/p devices
• The event may be periodic or unpredicted one(should not miss)
• So emb.sys. are generally reactive
• Timing behavior or the system should be deterministic
• Should not miss deadlines
Operates in harsh environment: the environment in which the
emb.sys. deployed may be a dusty one or high temperature
zone
• System placed in such areas should be capable to with stand
all operating conditions
• Distributed: emb.sys. may be a part of larger system
• Automatic vending m/c contains card reader, vending unit etc.
• They are independent but work together to achieve a
common goal
Small size and weight: size, weight, shape etc will be one of the
deciding factors to choose a product
• Most applications demands small sized and low weight
products
Power concerns: designed in such a way as to minimize the heat
dissipation
• May require cooling fan which occupies additional space
• Even it’s a critical constraint battery operated systems, more
the power consumption the less the battery life
Quality attributes of ES
• QA are the non-functional requirements that
need to be documented properly in any
system design.
• If the quality attributes are more concrete and
measurable it will give a positive impact on
the end product
• Operational QA
• Non-operational QA
Operational quality attributes
• Attributes related to e.s when it is in the operational mode or online
mode
Response: quickness of the system
• How fast the system is tracking the changes in input variables
• In flight control application any response delay in the system will create
potential damages to the safety of the flight
• Response time for a toy is not time critical
Throughput: efficiency of the system
• Rate of production or operation of a defined process
• Rates can be expressed in terms of units of products , batched
produced, or any other meaningful measurements.
• Generally measured in terms of benchmark (reference point)
Reliability: how much % you can rely upon the proper functioning of sys.
Mean time between failure MTBF (frq of failure in hr/wk/mon) &
mean time to repair MTTR ( how long the system is allowed to be out
Maintainability: deals with the support and
maintenance to the end user in the case of
technical issues and failures or on the basis of a
routine checkup
• As reliability increases maintainability reduced
• Two types (preventive or corrective maintenance)
• User should replace the cartridge after n number of
printouts (scheduled / periodic /preventive)
• If paper feeding part of the printer fails required
immediate repairs (maintenance to unexpected
failure/ corrective)
• Ideal value for availability is expressed
A = MTBF / (MTBF + MTTR)
Security : confidentiality( from
unauthorized disclosure), integrity ( from
unauthorized modification) , availability (
from unauthorized users)
Use of shared data, and programming the critical sections and re-entrant
functions.