18CS44

MICROCONTROLLER
AND EMBEDDED
SYSTEMS

MODULE 4
CHARACTERISTICS AND
QUALITY ATTRIBUTES
Dr. Mahesh Prasanna
K.
» No matter whether it is an embedded or a non-embedded system, there will
be a set of characteristics describing the system.

» The non-functional aspects that need to be addressed in embedded

system
design are commonly referred as quality attributes.

» Whenever you design an embedded system, the design should

take into consideration of both the functional and non-functional aspects.

MP, CSE, 2
VCET
 CHARACTERISTICS OF AN
EMBEDDED SYSTEM
» Embedded Systems possess certain specific characteristics and
these
characteristics are unique to each embedded system.

» Some of the important characteristics of an embedded system

are:

1. Application and domain specific

2. Reactive and Real Time

3. Operates in harsh environments

4. Distributed

5. Small size and weight

6. Power concerns
MP, CSE, 3
VCET
» Application and Domain
Specific:
» Each embedded system is having certain functions to perform.
» Embedded systems are developed to do only intended functions.

» They cannot be used for any other purpose.

» It is the major criterion which distinguishes an embedded system from a

general
purpose system.

 For example, you cannot replace the embedded control unit of your
microwave oven with your air conditioners embedded control unit.

» Also you cannot replace an embedded control unit developed for a particular
domain say telecom with another control unit designed to serve another
domain like consumer electronics.

MP, CSE, 4
VCET
» Reactive and Real Time:

» Embedded systems are in constant interaction with the Real world through
sensors and user defined input devices which are connected to the input port
of the system.
 Any changes happening in the Real world (which is called an Event) are
captured by the sensors or input devices in Real Time and the control
algorithm running inside the unit reacts in a designed manner to bring the
controlled output variables to the desired level.

» The event may be a periodic one or an unpredicted one.

» Embedded systems produce changes in output in response to the changes

in
the input. So they are generally referred as Reactive Systems.

MP, CSE, 5
VCET
» Real Time System operation means the timing behavior of the system should
be deterministic; meaning the system should respond to requests or tasks in a
know amount of time.

» A Real Time system should not miss any deadlines for tasks or operations.

» It is not necessary that all embedded systems should be Real Time in

operations.
 Embedded applications or systems which are mission critical, like flight
control systems, Antilock Brake Systems (ABS), etc. are examples of Real
Time systems.

» The design of an embedded Real Time system should take the worst case
scenario into consideration.

MP, CSE, 6
VCET
» Operates in Harsh Environment:

» It is not necessary that all embedded systems should be deployed in

controlled environments.

» The environment in which the embedded system deployed may be a

dusty
one or a high temperature zone or an area subject to vibrations and shock.

» Systems placed in such areas should be capable to withstand all these adverse
operating conditions.

» The design should take care of the operating conditions of the area where
the
system is going to implement.
 For example, if the system needs to be deployed in a high temperature
zone, then all the components used in the system should be of high
temperature grade. MP, CSE, 7
VCET
» Here we cannot go for a compromise in cost. Also proper shock absorption
techniques should be provided to systems which are going to be
commissioned in places subject to high shock.

» Power supply fluctuations, corrosion and component aging, etc. are the other
factors that need to be taken into consideration for embedded systems to work
in harsh environments.

MP, CSE, 8
VCET
» Distributed:

» The term distributed means that, embedded systems may be a part of larger
systems.

» Many numbers of distributed embedded systems form a single large

embedded control unit.
 An automatic vending machine is a typical example for this. The vending
machine contains a card reader (for pre-paid vending systems), a vending
unit, etc. Each of them are independent embedded units but they work
together to perform the overall vending function.

MP, CSE, 9
VCET
 Another example is the Automatic Teller Machine (ATM). An
ATM
contains a reader embedded unit, responsible for reading
card and
validating the user's AIM card, transaction unit for performing
transactions, a currency counter for dispatching/ vending currency to the
authorized person and a printer unit for printing the transaction details.
 Another typical example of a distributed embedded system is the
Supervisory Control And Data Acquisition (SCADA) system used in
Control & Instrumentation applications, which contains physically
distributed individual embedded control units connected to a supervisory
module.

MP, CSE, 10
VCET
» Small Size and Weight:

» Product aesthetics is an important factor in choosing a product.

 For example, when you plan to buy a new mobile phone, you may make a
comparative study on the pros and cons of the products available in the
market. Definitely the product aesthetics (size, weight, shape, style, etc.
will be one of the deciding factors to choose a product.

» People believe in the phrase "Small is beautiful". Moreover it is convenient

to
handle a compact device than a bulky product.

» In embedded domain also compactness is a significant deciding factor.

» Most of the application demands small size and low weight products.

MP, CSE, 11
VCET
» Power Concerns:

» Power management is another important factor that needs to be considered

in
designing embedded systems.

» Embedded systems should be designed in such a way as to minimize the

heat
dissipation by the system.

» The production of high amount of heat demands cooling requirements like

cooling fans which in turn occupies additional space and make a system
bulky.

» Nowadays ultra low power components are available in the market. Select the
design according to the low power components like low dropout regulators,
and controllers/ processors with power saving modes.

» Also power management is aMP,critical

CSE, constraint in battery operated
12
VCET
 QUALITY ATTRIBUTES OF
EMBEDDED SYSTEMS
» Quality attribute are 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 system development process
and the end product.

» The various quality attributes that needs to be addressed in any embedded

system development are broadly classified into two, namely

'Operational Quality Attributes' and 'Non-Operational Quality Attributes'.

MP, CSE, 13
VCET
»The Operational Quality » The Non-Operational
Attributes Quality
represent the quality Attributes needs to be addressed for
relevant related the product 'not ' on-the basis
attributeswhen ittois in
system thethe operational
embedded of
operational aspects are
grouped
mode or 'online' mode.
under this category.
1. Response 1. Testability & debug-ability

2. Throughput 2. Evolvability

3. Reliability 3. Portability

4. Maintainability 4. Time to Prototype and Market

5. Security 5. Per Unit and Total Cost

6. Safety

MP, CSE, 14
VCET
» 1. Response: is a measure of quickness of the system. It gives an idea about
how fast your system is tracking the changes in input variables.

» Most of the embedded systems demand fast response which should be almost
Real Time.
 For example, an embedded system deployed in flight control application
should respond in a Real Time manner. Any response delay in the system
will create potential damages to the safety of the flight as well as the
passengers.

» It is not necessary that all embedded systems should be Real Time in

response.
 For example, the response time requirement for an electronic toy is not at
all time critical. There is no specific deadline that this system should
respond wit in this particular timeline.
MP, CSE, 15
VCET
» 2. Throughput: deals with the efficiency of a system. Throughput is defined
as the rate of production or operation of a defined process over a stated period
of time.

» The rates can be expressed in terms of units of products, batches produced,

or
any other meaningful measurements.
 In case of a Card Reader, throughput means how many transactions
the Reader can perform in a minute or in an hour or in a day.

» Throughput is generally measured in terms of 'Benchmark'.

» A 'Benchmark' is a reference point by which something can be measured.

» Benchmark can be a set of performance criteria that a product is expected to

meet or a standard product that can be used for comparing other products of
the same product line.
MP, CSE, 16
VCET
» 3. Reliability: is a measure of how much % you can rely upon the proper
functioning of the system or what is the% susceptibility of the system to
failures.

» Mean Time Between Failures (MTBF) and Mean Time To Repair (MTTR)
are the terms used in defining system reliability.
 MTBF gives the frequency of failures in hours/ weeks/ months.
 MTTR specifies how long the system is allowed to be out of order
following a failure.

» For an embedded system with critical application need, it should be of

order
of minutes.

MP, CSE, 17
VCET
» 4. Maintainability: deals with support and maintenance to the end user or
client in case of technical issues and product failures or on the basis of a
routine system checkup.

» Reliability and Maintainability are considered as two complementary

disciplines.

» A more reliable system means a system with less corrective maintainability

requirements and vice versa. As the reliability of the system increases, the
chances of failure and non-functioning reduces, thereby the need for
maintainability is also reduced.

» Maintainability is closely related to the system availability. Maintainability

can be broadly classified into two categories, namely, 'Scheduled or Periodic
Maintenance (preventive maintenance)' and 'Maintenance to unexpected
failures (corrective maintenance)'.
MP, CSE, 18
VCET
» Some embedded products may use consumable components or may contain
components which are subject to wear and tear and they should be
replaced on a periodic basis. The period may be based on the total hours of
the system usage or the total output the system delivered.
 A printer is a typical example for illustrating the two types of
maintainability. An inkjet printer uses ink cartridges, which are
consumable components and as per the printer manufacturer the end
user should replace the cartridge after each 'n' number of printouts, to
get quality prints. This is an example for 'Scheduled or Periodic
maintenance'.
 If the paper feeding part of the printer fails the printer fails to print and
it requires immediate repairs to rectify this problem. This is an
example of 'Maintenance to unexpected failure'.
MP, CSE, 19
VCET
» In both of the maintenances (scheduled and repair), the-printer needs to
be
brought offline and during this time it will not be available for the user.

» In any embedded system design, the ideal value for availability is expressed
as

» Ai = MTBF / (MTBF + MTTR)

» Where, Ai – Availability in the ideal conditions.

MP, CSE, 20
VCET
» 5. Security: aspect covers ‘Confidentiality’, 'Integrity', and 'Availability' (The
term 'Availability' mentioned here is not related to the term 'Availability'
mentioned under the 'Maintainability' section).

» Confidentiality deals with the protection of data and application from

unauthorized disclosure.

» Integrity deals with the protection of data and application from unauthorized
modifications.

» Availability deals with protection of data and application from unauthorized

users.
 A very good example of the 'Security' aspect in an embedded product is a
Personal Digital Assistant (PDA). The PDA can be either a shared
resource (e.g. PDAs used in LAB setups) or an individual one.

MP, CSE, 21
VCET
  If it is a shared one, there should be some mechanism in the form of
user name and password to access into a particular person's profile – An
example of' Availability.

» Also all data and applications present in the PDA need not be accessible to all
users. Some of them are specifically accessible to administrators only. For
achieving this, Administrator and user levels of security should be
implemented – An example of Confidentiality.

» Some data present in the PDA may be visible to all users but there may not be
necessary permissions to alter the data by the users. That is Read Only access
is allocated to all users – An example of Integrity.

MP, CSE, 22
VCET
» 6. Safety: 'Safety' and 'Security' are confusing terms. Sometimes you may feel
both of them as a single attribute. But they represent two unique aspects in
quality attributes.
 Safety deals with the possible damages that can happen to
 the operators,
 public and the environment;
 due to
 the breakdown of an embedded system,
 the emission of radioactive or hazardous materials from the embedded
products.

MP, CSE, 23
VCET
» The breakdown of an embedded system may occur due to a hardware failure
or a firmware failure.

» Safety analysis is a must in product engineering to evaluate the anticipated

damages and determine the best course of action to bring down the
consequences of the damages to an acceptable level.

» Some of the safety threats are sudden (like product breakdown) and some of
them are gradual (like hazardous emissions from the product).

MP, CSE, 24
VCET
» 1. Testability & Debug-ability: deals with how easily one can test his/ her
design, application; and by which means he/ she can test it.

» For an embedded product, testability is applicable to both the embedded

hardware and firmware.
 Embedded hardware testing ensures that the peripherals and the total
hardware functions in the desired manner, whereas firmware testing
ensures that the firmware is functioning in the expected way.

» Debug-ability is a means of debugging the product as such for figuring out

the probable sources that create unexpected behavior in the total system.

MP, CSE, 25
VCET
» Debug-ability has two aspects in the embedded system development context,
namely, hardware level debugging and firmware level debugging.
 Hardware debugging is used for figuring out the issues created by
hardware problems whereas firmware debugging is employed to figure out
the probable errors that appear as a result of flaws in the firmware.

» 2. Evolvability: is a term which is closely related to Biology.

» Evolvability is referred as the non-heritable variation. For an embedded

system, the quality attribute 'Evolvability' refers to the ease with which the
embedded product (including firmware and hardware) can be modified to
take advantage of new firmware or hardware technologies.

MP, CSE, 26
VCET
» 3. Portability: is a measure of 'system independence'.

» An embedded product is said to be portable if the product is capable of

functioning 'as such' in various en environments, target processors/
controllers and embedded operating systems.

» The ease with which an embedded product can be ported on to a new

platform is a direct measure of the rework required.

» A standard embedded product should always be flexible and portable.

» In embedded products, the term 'porting' represents the migration of the

embedded firmware written for one target processor (i.e., Intel x86) to a
different target processor (say ARM Cortex M3 processor).

MP, CSE, 27
VCET
» If the firmware is written in a high level language like 'C' with little target
processor-specific functions (operating system extensions or compiler
specific utilities), it is very easy to port the firmware for the new processor by
replacing those 'target processor-specific functions' with the ones for the new
target processor and re-compiling the program for the new target processor•
specific settings. Re-compiling the program or the new target processor
generates the new target processor-specific machine codes.

» If the firmware is written in Assembly Language for a particular family of

processor (say x86 family), it will be difficult to translate the assembly
language instructions to the new target processor specific language and so the
portability is poor.

MP, CSE, 28
VCET
» If you look into various programming languages for application development
for desktop applications, you will see that certain applications developed on
certain languages run only on specific operating systems and some of them
run independent of the desktop operating systems.

» For example, applications developed using Microsoft technologies (e.g.

Microsoft Visual C++ using Visual studio) is capable of running only on
Microsoft platforms and will not function on other operating systems;
whereas applications developed using 'Java' from Sun Microsystems
works on any operating system that supports Java standards.

MP, CSE, 29
VCET
» 4. Time to Prototype and Market: is the time elapsed between the
conceptualization of a product and the time at which the product is ready for
selling (for commercial product) or use (for non-commercial products).

» The commercial embedded product market is highly competitive and time to

market the product is a critical factor in the success of a commercial
embedded product.

» There may be multiple players in the embedded industry who develop

products of the same category (like mobile phone, portable media players,
etc.). If you come up with a new design and if it takes long time to develop
and market it, the competitor product may take advantage of it with their
product.

MP, CSE, 30
VCET
» Also, embedded technology is one where rapid technology change is
happening. If you start your design by making use of a new technology and if
it takes long time to develop and market the product, by the time you market
the product, the technology might have superseded with a new technology.

» Product prototyping helps a lot in reducing time-to-market. Whenever you

have a product idea, you may not be certain about the feasibility of the idea.

» Prototyping is an informal kind of rapid product development in which the

important features of the product under consideration are developed.

» The time to prototype is also another critical factor. If the prototype is

developed faster, the actual estimated development time can be brought down
significantly. In order to shorten the time to prototype, make use of all
possible options like the use of off-the-shelf components, re-usable assets,
etc.
MP, CSE, 31
VCET
» 5. Per Unit and Total Cost: is a factor which is closely monitored by both
end user (those who buy the product) and product manufacturer (those who
build the product).

» Cost is a highly sensitive factor for commercial products. Any failure to

position the cost of a commercial product at a nominal rate, may lead to the
failure of the product in the market. Proper market study and cost benefit
analysis should be carried out before taking a decision on the per-unit cost of
the embedded product.

» From a designer/ product development company perspective the ultimate aim

of a product is to generate marginal profit. So the budget and total system
cost should be properly balanced to provide a marginal profit.

MP, CSE, 32
VCET
» The Product Life Cycle (PLC): Every embedded product has a product
life
cycle which starts with the design and development phase.

» The product idea generation; prototyping, Roadmap definition, actual

product design and development are the activities carried out during this
phase.

» During the design and development phase there is only investment and
no
returns.

» Once the product is ready to sell, it is introduced to the market. This stage is
known as the Product Introduction stage.

» During the initial period the sales' and revenue will be low. There won't be
much competition and the product sales and revenue increases with time. In
the growth phase, the product grabs high market share.
MP, CSE,
VCET
33
» During the maturity phase, the growth and sales will be steady and the
revenue reaches its peak.

» The Product retirement/ Decline phase starts with the drop in sales volume;
market share and revenue. The decline happens due to various reasons like
competition from similar product with enhanced features or technology
changes, etc. At some point of the decline stage, the manufacturer announces
discontinuing of the product.

» The different stages of the embedded products life cycle-revenue, unit cost
and profit in each stage-are represented in the following Product Life-cycle
graph.

MP, CSE, 34
VCET
MP, CSE, 35
VCET
 18CS44
MICROCONTROLLER AND
EMBEDDED SYSTEMS

MODULE 4
EMBEDDED SYSTEMS –
APPLICATION-
AND DOMAIN-
Dr. Mahesh Prasanna
SPECIFIC K.MP,
CSE,
» Embedded systems are application and domain specific, meaning; they are
specifically built for certain applications in certain domains like consumer
electronics, telecom, automotive, industrial control, etc.

» It is possible to replace a general purpose computing system with another

system which is closely matching with the existing system, whereas it is not
the case with embedded systems.

» Embedded systems are highly specialized in functioning and are dedicated for
a specific application. Hence it is not possible to replace an embedded system
developed for a specific application in a specific domain with another
embedded system designed for some other application in some other domain.

MP, CSE, 37
VCET
 WASHING MACHINE–APPLICATION-
SPECIFIC EMBEDDED SYSTEM
» An embedded system contains sensors, actuators, control unit and application-
specific user interfaces like keyboards, display units, etc. One can see all these
components in a washing machine. Some of them are visible and some of them
may be invisible.

» The actuator part of the washing machine consists of a motorized agitator,

tumble tub, water drawing pump and inlet valve to control the flow of water
into the unit.

» The sensor part consists of the water temperature sensor, level sensor, etc.

» The control part contains a micro• processor/ controller based board with
interfaces to the sensors and actuators.
MP, CSE, 38
VCET
» The sensor data is fed back to the control unit and the control unit
generates
the necessary actuator outputs.

» The control unit also provides connectivity to user interfaces like

» keypad for setting the washing time,

» selecting the type of material to be washed like light, medium, heavy duty,
etc.

» User feedback is reflected through the display unit and LEDs connected to
the
control board.

MP, CSE, 39
VCET
» Functional block diagram of
washing

MP, CSE, 40
VCET
Washing machine comes in two models, top loading and front loading.

» In top loading models the agitator of the machine twists back and forth and
pulls the cloth down to the bottom of the tub. On reaching the bottom of the
tub the clothes work their way back up to the top of the tub where the agitator
grabs them again and repeats the mechanism.

» In the front loading machines, the clothes are tumbled and plunged into the
water over and over again. This is the first phase of washing.

» In the second phase of washing, water is pumped out from the tub and the
inner tub uses centrifugal force to wring out more water from the clothes by
spinning at several hundred Rotations Per Minute (RPM). This is called a
'Spin Phase'.

MP, CSE, 41
VCET
General principle of working of the washing machine:

» The basic controls consist of a timer, cycle selector mechanism, water

temperature selector, load size selector and start button.

» The mechanism includes the motor, transmission, clutch, pump, agitator,

inner tub, outer tub and water inlet valve.

» The integrated control panel consists of a microprocessor/ controller based

board with I/O interfaces and a control algorithm running in it.

MP, CSE, 42
VCET
» Input interface includes the keyboard which consists of wash type selector:
Wash, Spin and Rinse; clothe selector: Light, Medium, Heavy duty and
washing time setting, etc.

» The output interface consists of LED/ LCD displays, status indication LEDs,
etc. connected to the I/O bus of the controller.

» The other types of I/O interfaces which are invisible to the end user are
different kinds of sensor interfaces: water temperature sensor, water level
sensor, etc., and actuator interface including motor control for agitator and
tub movement control, inlet water flow control, etc.

MP, CSE, 43
VCET
 AUTOMOTIVE – DOMAIN-SPECIFIC
EMBEDDED SYSTEM
» The major application domains of embedded systems are consumer, industrial,
automotive, telecom, etc. The following Figure gives an overview of the various
types of electronic control units employed in automotive applications.

MP, CSE, 44
VCET
» Inner Working of Automotive Embedded Systems:

» Automotive embedded systems are the one where electronics take control over
the mechanical systems. The presence of automotive embedded system in a
vehicle varies from simple mirror and wiper controls to complex air bag
controller and antilock brake systems (ABS).

» Automotive embedded systems are normally built around microcontrollers or

DSPs or a hybrid of the two and are generally known as Electronic Control
Units (ECUs).

» The number of embedded controllers in an ordinary vehicle varies from 20 to

40 whereas a luxury veh1cle like Mercedes S and BMW 7 may contain over
100 embedded controllers.

» The first embedded system used in automotive application was the

microprocessor based fuel injection system introduced by Volkswagen 1600
MP, CSE, 45
in 1968. VCET
» The various types of electronic control units (ECUs) used in the automotive
embedded industry can be broadly classified into two:

» High-speed Electronic Control Units (HECUs): are deployed in critical

control units requiring fast response. They include fuel injection systems,
antilock brake systems, engine control, electronic throttle, steering controls,
transmission control unit and central control unit.

» Low-speed Electronic Control Units (LECUs): are deployed in applications

where response time is not so critical. They generally are built around low
cost microprocessors/ microcontrollers and digital signal processors. Audio
controllers, passenger and driver door locks, door glass controls (power
windows), wiper control, mirror control, seat control systems, head lamp and
tail lamp controls, sun roof control unit etc., are examples of LECUs.

MP, CSE, 46
VCET
» Automotive Communication Buses:

» Automotive applications make use of serial buses for communication, which

greatly reduces the amount of wiring required inside a vehicle. The different
types of serial interface buses deployed in automotive embedded applications
are –

» Controller Area Network (CAN)

» Local Interconnect Network (LIN)

» Media Oriented System Transport (MOST) Bus

MP, CSE, 47
VCET
» 1. Controller Area Network (CAN): The CAN bus was originally proposed
by Robert Bosch, pioneer in the Automotive embedded solution providers.

» CAN supports medium speed (ISO 11519-class B with data rates up to 125
Kbps) and high speed (ISO 11898 class C with data rates up to 1Mbps) data
transfer.

» CAN is an event-driven protocol interface with support for error handling in

data transmission.

» It is generally employed in-safety system like airbag control; power train

systems like engine control and Antilock Brake System (ABS); and
navigation systems like GPS.

MP, CSE, 48
VCET
» 2. Local Interconnect Network (LIN): LIN bus is a single master
multiple
slave (up to 16 independent slave nodes) communication interface.

» LIN is a low speed, single wire communication interface with support

for
data rates up to 20 Kbps and is used for sensor/ actuator interfacing.

» LIN bus follows the master communication triggering technique to eliminate

the possible bus arbitration problem that can occur by the simultaneous
talking of different slave nodes connected to a single interface bus.

» LIN bus is employed in applications like mirror controls, fan controls, seat
positioning controls, window controls, and position controls where response
time is not a critical issue.

MP, CSE, 49
VCET
» 3. Media Oriented System Transport (MOST) Bus: MOST is targeted for
automotive audio/ video equipment interfacing, used primarily in European
cars.

» A MOST bus is a multimedia fibre-optic point-to-point network implemented

in a star, ring or daisy• chained topology over optical fibre cables.

» The MOST bus specifications define the physical (electrical and optical
parameters) layer as well as the application layer, network layer, and media
access control.

» MOST bus is an optical fibre cable connected between the Electrical Optical
Converter (EOC) and Optical Electrical Converter (OEC), which would
translate into the optical cable MOST bus.

MP, CSE, 50
VCET
» Key Players of the Automotive Embedded Market:

» The key players of the automotive embedded market can be visualized in

three verticals: silicon providers, tools and platform providers and solution
providers.

» 1. Silicon Providers: are responsible for providing the necessary chips which
are used in the control application development.

» The chip may be a standard product like microcontroller or DSP or ADC/

DAC chips.

» Some applications may require specific chips and they are manufactured as
Application Specific Integrated Chip (ASIC).

MP, CSE, 51
VCET
» 2. Tool and Platform Providers: are manufacturers and suppliers of various
kinds of development tools and Real Time Embedded Operating Systems for
developing and debugging different control unit related applications.

» Tools fall into two categories, namely embedded software application

development tools and embedded hardware development tools.

» 3. Solution Providers: Solution providers supply Original Equipment

Manufacturer (OEM) and complete solution for automotive applications
making use of the chips, platforms and different development tools.

MP, CSE, 52
VCET
 18CS44
MICROCONTROLLER AND
EMBEDDED SYSTEMS

MODULE 4
HARDWARE SOFTWARE
CO-DESIGN AND
PROGRAM MODELING
Dr. Mahesh Prasanna
K.
» In the traditional embedded system development approach, the hardware
software partitioning is done at an early stage and engineers from the
software group take care of the software architecture development and
implementation, whereas engineers from the hardware group are responsible
for building the hardware required for the product.

» There is less interaction between the two teams and the development happens
either serially or in parallel. Once the hardware and software are ready, the
integration is performed.

» The increasing competition in the commercial market and need for reduced
'time-to-market' the product calls for a novel approach for embedded system
design in which the hardware and software are co-developed instead of
independently developing both.

MP, CSE, 54
VCET
 FUNDAMENTAL ISSUES IN
HARDWARE SOFTWARE CO-DESIGN
» The hardware software co-design is a problem statement and when we try to
solve this problem statement in real life we may come across multiple issues in
the design.

» The following section illustrates some of the fundamental issues in hardware

software co-design.

» Selecting the model

» Selecting the architecture

» Selecting the language

» Partitioning system requirements into hardware and software

MP, CSE, 55
VCET
» Selecting the Model: In hardware software co-design, models are used for
capturing and describing the system characteristics.

» A model is a formal system consisting of objects and composition rules. It is

hard to make a decision on which model should be followed in a particular
system design. Most often designers switch between varieties of models from
the requirements specification to the implementation aspect of the system
design. The reason being, the objective varies with each phase.
 For example, at the specification stage, only the functionality of the
system is in focus and not the implementation information. When the
design moves to the implementation aspect, the information about the
system component is is revealed and the designer has to switch to a model
capable of capturing the system's structure.

MP, CSE, 56
VCET
» Selecting the Architecture: A model only captures the system characteristics
and does not provide information on 'how the system can be manufactured?’

» The architecture specifies how a system is going to implement in terms of

the number and types of different components and the interconnection among
them.

» Controller architecture, Datapath Architecture, Complex Instruction Set

Computing (CISC), Reduced Instruction Set Computing (RISC), Very Long
Instruction Word Computing (VLIW), Single Instruction Multiple Data
(SIMD), Multiple Instruction Multiple Data (MIMD), etc., are the commonly
used architectures in system design.

» Some of them fall into Application Specific Architecture Class (like

Controller Architecture), while others fall into either General Purpose
Architecture Class (CISC, RISC, etc.) or Parallel Processing Class (like
VLIW, SIMD, MIMD, etc.). MP, CSE, 57
VCET
» The Controller Architecture implements the finite state machine model
(FSM) using a state register and two combinational circuits.

» The state register holds the present state and the combinational circuits
implement the logic for next state and output.

» The Datapath Architecture is best suited for implementing the data flow
graph model where the output is generated as a result of a set of predefined
computations on the input data.

» A datapath represents a channel between the input and output; and

» in datapath architecture the datapath may contain registers, counters,

register files, memories and ports along with high speed arithmetic units.
Ports connect the datapath to multiple buses.

MP, CSE, 58
VCET
» The Finite State Machine Datapath (FSMD) architecture combines the
controller architecture with datapath architecture.

» It implements a controller with datapath.

» The controller generates the control input, whereas the datapath processes
the data.

» The datapath contains two types of I/O ports,

» out of which one acts as the control port for receiving/ sending the
control
signals from/ to the controller unit and

» the second I/O port interfaces the datapath with external world for
data input
and data output.

MP, CSE, 59
VCET
» The Complex Instruction Set Computing (CISC) architecture uses an
instruction set representing complex operations.

» It is possible for a CISC instruction set to perform a large complex

operation with a single instruction. The use of a single complex instruction
in place of multiple simple instructions greatly reduces the program
memory access and program memory size requirement.

» However it requires additional silicon for implementing microcode

decoder for decoding the CISC instruction.

» The datapath for the CISC processor is complex.

MP, CSE, 60
VCET
» The Reduced Instruction Set Computing (RISC) architecture reuses
instruction set representing simple operations and it requires the execution of
multiple RISC instructions to perform a complex operation.

» The data path of RISC architecture contains a large register file for storing
the operands and output.

» RISC instruction set is designed to operate on registers. RISC architecture

supports extensive pipelining.

» The Very Long Instruction Word (VLIW) architecture implements

multiple
functional units (ALUs, multipliers, etc.) in the datapath.

» The VLIW instruction packages one standard instruction per functional

unit of the datapath.

MP, CSE, 61
VCET
» Parallel Processing architecture implements multiple concurrent Processing
Elements (PEs) and each processing element may associate a datapath
containing register and local memory.

» Single Instruction Multiple Data (SIMD) and Multiple Instruction

Multiple Data (MIMD) architectures are examples for parallel processing
architecture.
» In SIMD architecture, a single instruction is executed in parallel with the help
of the Processing Element. The scheduling-of the instruction execution and
controlling of each PE is performed through a single controller. The SIMD
architecture forms the basis of reconfigurable processor.

» On the other hand, the processing elements of the MIMD architecture execute
different instructions at a given point of time. The MIMD architecture forms
the basis of multiprocessor systems.

MP, CSE, 62
VCET
» Selecting the Language: A programming language captures a
'Computational Model' and maps it into architecture. There is no hard and fast
rule to specify which language should be used for capturing this model. A
model can be captured using multiple programming languages like C, C++,
C#, Java, etc. for software implementations and languages like VHDL,
System C, Verilog, etc. for hardware implementations.

» On the other hand, a single language can be used for capturing a variety of
models.

» Certain languages are good in capturing certain computational model.

For example, C++ is a good candidate for capturing an object oriented
model.

» The only pre-requisite in selecting a programming language for capturing

a
model is that the language should capture
MP, CSE, the model easily. 63
VCET
» Partitioning System Requirements into Hardware and Software: It may
be possible to implement the system requirements in either hardware or
software (firmware).

» It is a tough decision making task to figure out which one to opt.

» Various hardware software trade-offs are used for making a decision on the
hardware-software partitioning.

MP, CSE, 64
VCET
 COMPUTATIONAL MODELS IN
EMBEDDED DESIGN
» Different Computational Models used in Embedded System design are
–

1. Data Flow Graph/ Diagram (DFG) model

2. Control Data Flow Graph/ Diagram (CDFG) model

3. State Machine model

4. Sequential Program model

5. Concurrent/ Communicating Process model

6. Object-Oriented model

MP, CSE, 65
VCET
» Data Flow Graph/ Diagram (DFG) Model: The DFG model translates the
data processing requirements into a data flow graph.

» The Data Flow Graph model is a data driven model in which the program
execution is determined by data. This model emphasizes on the data and
operations on the data transform the input data to output data.

» Indeed Data Flow Graph is a visual model in which the operation on the data
(process) is represented using a block (circle) and data flow is represented
using arrows. An inward arrow to the process (circle) represents input data
and an outward arrow from the process (circle) represents output data in DFG
notation.

» Embedded applications which are computational intensive and data driven are
modeled using the DFG model.

MP, CSE, 66
VCET
» Suppose one of the functions in an application contains the computational
requirement x = a + b; and y = x – c. The following Figure illustrates the
implementation of a DFG model for implementing these requirements.

» In a DFG model, a data path is the data flow path from input to output.

» A DFG model is said to be acyclic DFG (ADFG), if it doesn't contain multiple

values
for the input variable and multiple output values for a given set of input(s).
MP, CSE, 67
VCET
» Control Data Flow Graph/ Diagram (CDFG) Model: In a DFG model, the
execution is controlled by data and it doesn't involve any control operations
(conditionals).

» The Control DFG (CDFG) model is used for modeling applications involving
conditional program execution. CDFG models contains both data operations
and control operations.

» The CDFG uses Data Flow Graph (DFG) as element and conditional
(constructs) as decision makers. CDFG contains both data flow nodes and
decision nodes, whereas DFG contains only data flow nodes.

» If flag = 1, x = a + b; else y = a – b; this requirement contains a decision

making process. The CDFG model for the same is given in the following
Figure.

MP, CSE, 68
VCET
» The control node is represented by a
'Diamond' block which is the decision
making element in a normal flow chart
based design.

» CDFG translates the requirement, which

is modeled to a concurrent process
model. The decision on which process is
to be executed is determined by the
control node.
» TA real world example for modeling the embedded application using CDFG
is the capturing and saving of the image to a format set by the user in a
digital still camera.

MP, CSE, 69
VCET
» State Machine Model: The State Machine model is used for modeling
reactive or event-driven embedded systems whose processing behavior is
dependent on state transitions. Embedded systems used in the control and
industrial applications are typical examples for event driven systems.

» The State Machine model describes the system behavior with 'States',
'Events', 'Actions' and 'Transitions'.
 State is a representation of a current situation.
 An event is an input to the state. The event acts as stimuli
for state transition.
 Transition is the movement from one state to another.
 Action is an activity to be performed by the state machine.

MP, CSE, 70
VCET
» A Finite State Machine (FSM) model is one in which the number of states
are finite.
 As an example let us consider the design of an embedded system for
driver/ passenger 'Seat Belt Warning' in an automotive using the FSM
model. The system requirements are captured as.
 When the vehicle ignition is turned on and the seat belt is not fastened within
10 seconds of ignition ON, the system generates an alarm signal for 5 seconds.
 The Alarm is turned off when the alarm time (5 seconds) expires or if the
driver/ passenger fasten the belt or if the ignition switch is turned off,
whichever happens first.
 Here the states are 'Alarm Off', 'Waiting' and 'Alarm On' and the events are
'Ignition Key ON', 'Ignition Key OFF', 'Timer Expire', 'Alarm Time Expire' and
'Seat Belt ON'.

MP, CSE, 71
VCET
 Using the FSM, the system requirements can be modeled as given in following
Figure.

 The 'Ignition Key ON' event triggers the 10 second timer and transitions the
state to 'Waiting'.
 If a 'Seat Belt ON' or 'Ignition Key OFF' event occurs during the wait state, the
state transitions into 'Alarm Off'.
 When the wait timer expires in the waiting state, the event 'Timer Expire' is
generated and it transitions the state to 'Alarm On' from the 'Waiting' state.
MP, CSE, 72
VCET
 The 'Alarm On' state continues until a 'Seat Belt ON' or 'Ignition Key OFF'
event or 'Alarm Time Expire' event, whichever occurs first. The occurrence of
any of these events transitions the state to 'Alarm Off'.
 The wait state is implemented using a timer. The timer also has certain set of
states and events for state transitions. Using the FSM model, the timer can be
modeled as shown in the following Figure.

MP, CSE, 73
VCET
 As seen from the FSM, the timer state can be either 'IDLE' or 'READY' or
'RUNNING'.
 During the normal condition when the timer is not running, it is said to be in
the 'IDLE' state.
 The timer is said to be in the 'READY' state when the timer is loaded with the
count corresponding to the required time delay. The timer remains in the
'READY' state until a 'Start Timer' event occurs.
 The timer changes its state to 'RUNNING' from the 'READY' state on receiving
a 'Start Timer' event and remains in the 'RUNNING' state until the timer count
expires or a 'Stop Timer' even occurs. The timer state changes to 'IDLE' from
'RUNNING' on receiving a 'Stop Timer' or 'Timer Expire' event.

MP, CSE, 74
VCET
Example 1: Design an automatic tea/ coffee vending machine based on FSM
model for the following requirement.

» The tea/ coffee vending is initiated by user inserting a 5 rupee coin. After
inserting the coin, the user can either select 'Coffee' or 'Tea' or press 'Cancel'
to cancel the order and take back the coin.

» The FSM representation for the above requirement is given in the following
Figure.

MP, CSE, 75
VCET
» The FSM representation contains four states namely; 'Wait for coin' 'Wait for
User Input', 'Dispense Tea' and 'Dispense Coffee'.

» The event 'Insert Coin' (5 rupee coin insertion), transitions the state to 'Wait
for User Input'. The system stays in this state until a user input is received
from the buttons 'Cancel', 'Tea' or 'Coffee'.

» If the event triggered in 'Wait State' is 'Cancel' button press, the coin is
pushed out and the state transitions to 'Wait for Coin'. If the event received in
the 'Wait State' is either 'Tea' button press, or 'Coffee' button press, the state
changes to 'Dispense Tea' or 'Dispense Coffee' respectively.

» Once the coffee/ tea vending is over, the respective states transitions back to
the 'Wait for Coin' state.

MP, CSE, 76
VCET
Example 2: Design a coin operated public telephone unit based on FSM
model for the following requirements.

» The calling process is initiated by lifting the receiver (off-hook)

of the telephone unit

» After lifting the phone the user needs to insert a 1 rupee coin to make the call

» If the line is busy, the coin is returned on placing the receiver back on the
hook (on-hook)

» If the line is through, the user is allowed to talk till 60 seconds and at the end
of 45th second, prompt for inserting another 1 rupee coin for continuing the
call is initiated

» If the user doesn't insert another 1 rupee coin, the call is terminated on
completing the 60 seconds time slot

MP, CSE, 77
VCET
» The system is ready to accept new call request when the receiver is placed
back on the hook (on-hook)

» The system goes to the 'Out of Order' state when there is a line fault.

» The FSM model shown

in the following Figure

is a simple representation.

MP, CSE, 78
VCET
» Most of the time state machine model translates the requirements into
sequence driven program and it is difficult to implement concurrent
processing with FSM. This limitation is addressed by the Hierarchical/
Concurrent Finite State Machine model (HCFSM).

» The HCFSM is an extension of the FSM for supporting concurrency and

hierarchy.

» HCFSM extends the conventional state diagrams by the AND, OR

decomposition of States together with inter level transitions and a broadcast
mechanism for communicating between concurrent processes.

» HCFSM uses statecharts for capturing the states, transitions, events and
actions.

» The Harel Statechart, UML State diagram, etc. are examples for popular
statecharts used for the HCFSM modeling of embedded systems.
MP, CSE, 79
VCET
» Sequential Program Model: In the sequential programming Model, the
functions or processing requirements are executed in sequence. It is same as
the conventional procedural programming.

» Here the program instructions are iterated and executed conditionally and the
data gets transformed through a series of operations.

» FSMs are good choice for sequential program modeling.

» Another important tool used for modeling sequential program is Flow Charts.

» The FSM approach represents the states, events, transitions

and actions, whereas the Flow Chart models the execution flow.

» The execution of functions in a sequential program model for the 'Seat

Belt
Warning' system is illustrated below.

MP, CSE, 80
VCET
MP, CSE, 81
VCET
» Communicating Process Model: The concurrent or
Concurrent/
communicating process model models concurrently executing
tasks/
processes.

» It is easier to implement certain requirements in concurrent processing model

than the conventional sequential execution.

» Sequential execution leads to a single sequential execution of task and

thereby leads to poor processor utilization, when the task involves I/O
waiting, sleeping for specified duration etc.

» If the task is split into multiple subtasks, it is possible to tackle the CPU usage
effectively, when the subtask under execution goes to a wait or sleep mode,
by switching the task execution.

» However, concurrent processing model requires additional overheads in task

scheduling, task synchronization and
MP,communication.
VCET
CSE, 82
» As an example for the concurrent processing model let us examine how we
can implement the 'Seat Belt Warning' system in concurrent processing
model. We can split the tasks into:

1. Timer task for waiting 10 seconds (wait timer task)

2. Task for checking the ignition key status (ignition key status
monitoring task)

3. Task for checking the seat belt status (seat belt status monitoring task)

4. Task for starting and stopping the alarm (alarm control task)

5. Alarm timer task for waiting 5 seconds (alarm timer task)

» We have five tasks here and we cannot execute them randomly or

sequentially. We need to synchronize their execution through some
mechanism.

MP, CSE, 83
VCET
» We need to start the alarm only after the expiration of the 10 seconds wait
timer and that too only if the seat belt is OFF and the ignition key is ON.
Hence the alarm: control task is executed only when the wait timer is expired
and if the ignition key is in the ON state and seat belt is in the OFF state.

» One way of implementing a concurrent model for the 'Seat Belt Warning'
system is illustrated in the following Figure.

MP, CSE, 84
VCET
MP, CSE, 85
VCET
» Object-Oriented Model: The object-oriented model is an object based model
for modeling system requirements. It disseminates a complex software
requirement into simple well defined pieces called objects.

» Object-oriented model brings re-usability, maintainability and productivity in

system design.

» In the object-oriented modeling, object is an entity used for representing

or modeling a particular piece of the system.

» Each object is characterized by a set of unique behavior and state.

» A class is an abstract description of a set of objects and it can be

considered
as a 'blueprint' of an object.

MP, CSE, 86
VCET
» A class represents the state of an object through member variables and object
behavior through member functions. The member variables and member
functions of a class can be private, public or protected.
 Private member variables and functions are accessible only within the
class, whereas public variables and functions are accessible within the
class as well as outside the class.
 The protected variables and functions are protected from external access.

» However classes derived from a parent class can also access the protected
member functions and variables.

» The concept of object and class brings abstraction, hiding and protection.

MP, CSE, 87
VCET
 18CS44
MICROCONTROLLER AND
EMBEDDED SYSTEMS

MODULE 4
EMBEDDED FIRMWARE
DESIGN AND
DEVELOPMENT
Dr. Mahesh Prasanna
K.
» The embedded firmware is responsible for controlling the various peripherals
of the embedded hardware and generating response in accordance with the
functional requirements mentioned in the requirements for the particular
embedded product.

» Firmware is considered as the master brain of the embedded system.

» Embedded firmware is stored at a permanent memory (ROM).

» Designing embedded firmware requires

» understanding of the particular embedded product hardware, like

various
component interfacing, memory map details I/O port details,

» configuration and register details of various hardware chips used and some
programming language (low level assembly language or a high level
languages like C/C++/JAVA).
MP, CSE, 89
VCET
» Embedded firmware development process starts with

» the conversion of the firmware requirements into a program model

» using modeling skills like UML or flow chart based

representation.

» The UML diagrams or flow chart gives a diagrammatic representation of the

decision items to be taken and the tasks to be performed.

MP, CSE, 90
VCET
 EMBEDDED FIRMWARE DESIGN
APPROACHES
» The firmware design approaches for embedded product is purely dependent on
the complexity of the functions to be performed, the speed of operation
required, etc.

» Two basic approaches are used for embedded firmware design. They are

» 'Conventional Procedural Based Firmware Design' (also known as 'Super Loop

Model') and

» 'Embedded Operating System (OS) Based Design'.

MP, CSE, 91
VCET
» The Super Loop Based Approach:

» The Super Loop based firmware development approach is adopted for

applications that are not time critical and where the response time is not so
important.

» Super loop approach is very similar to a conventional procedural

programming where the code is executed task by task.

» The task, listed at the top of the program code, is executed first and the tasks,
just below the top are executed after completing the first task. This is a true
procedural one.

» In a multiple task based system, each task is executed in serial in this

approach.

MP, CSE, 92
VCET
» The firmware execution flow for this will be
–
1. Configure the common parameters and perform
initialization for
various hardware components memory, registers, etc.

2. Start the first task and execute it

3. Execute the second task

4. Execute the next task

5. :

6. :

7. Execute the last defined task

8. Jump back to the first task and follow the same flow.

» From the firmware execution sequence, it is obvious that the order in

which the tasks to be executed Mare,P Cfixed and they are hard coded in the
Also the operation is an infinite lo o pESb, VaCsEeTd 93
» We can visualize the operational sequence listed above in terms of a ‘C’
program code as –

» From the above 'C' code you can see that the
tasks 1 to n are performed one after another
and when the last task (nth task) is executed,
the firmware execution is again re-directed
to Task 1 and it is repeated forever in the
loop.

» This repetition is achieved by using an

infinite loop. This approach is also referred
as 'Super loop based Approach'.

MP, CSE, 94
VCET
» Since the tasks are running inside an infinite loop, the only way to come out
of the loop is either a hardware reset or an interrupt assertion.

» A hardware reset brings the program execution back to the main loop.

» An interrupt request suspends the task execution temporarily and performs

the corresponding interrupt routine and on completion of the interrupt routine
it restarts the task execution from the point where it got interrupted.

» The 'Super loop based design' doesn't require an operating system, since there
is no need for scheduling which task is to be executed and assigning
priority to each task. In a super loop based design, the priorities are
fixed and the order in which the tasks to be executed are also fixed.

» Hence the code for performing these tasks will be residing in the code
memory without an operating system image.

MP, CSE, 95
VCET
» Super loop based design is deployed in low cost embedded products and
products where response time is not time critical. Some embedded products
demand this type of approach.
 For example, reading/ writing data to and from a card using a card reader
requires a sequence of operations like checking the presence of card,
authenticating the operation, reading/writing, etc.
 A typical example of a 'Super loop based' product is an electronic video
game toy containing keypad and display unit. The program running inside
the product may be designed in such a way that it reads the keys to detect
whether the user has given any input and if any key press is detected the
graphic display is updated. Even if the application misses a key press, it
won't create any critical issues; rather it will be treated as a bug in the
firmware.
MP, CSE, 96
VCET
» The 'Super loop based design' is simple and straight forward without any OS
related overheads.

» The major drawback of this approach is that any failure in any part of a task
will affect the total system. If the program hangs up at some point while
executing a task, it may remain there forever and ultimately the product stops
functioning.

» Another major drawback of 'Super loop based design' approach is the lack
of
real timeliness.

» There are corrective measures for this also. The best advised option in use
interrupts for external events requiring real time attention.

MP, CSE, 97
VCET
» The Embedded Operating System (OS) Based
Approach:
» The Operating System (OS) based approach contains operating systems,
which can be either a General Purpose Operating System (GPOS) or a Real
Time Operating System (RTOS) to host the user written application
firmware.

» The General Purpose OS (GPOS) based design is very similar to a

conventional PC based application development, where the device contains
an operating system (Windows/ Unix/ Linux, etc. for Desktop PCs) and you
will be creating and running user applications on top of it.
 Example of a GPOS used in embedded product development is Microsoft®
Windows XP Embedded 8.1, whIch offers customization to use industry devices
like Personal Digital Assistants (PDAs), Hand held devices/ Portable devices,
Point of Sale (PoS) Terminals, Patient Monitoring Systems, etc.

MP, CSE, 98
VCET
» OS based applications also require 'Driver software' for different hardware
present on the board to communicate with them.

» The Real Time Operating System (RTOS) based design is

employed in embedded products demanding Real-time response.

» RTOS respond in a timely and predictable manner to events. Real Time

operating system contains a Real Time kernel responsible for performing pre-
emptive multitasking, scheduler for scheduling tasks, multiple threads, etc. A

» Real Time Operating System (RTOS) allows flexible scheduling of system

resources like the CPU and memory and offers some way to communicate
between tasks.
» 'Windows Embedded Compact', 'pSOS', 'VxWorks', 'ThreadX', 'MicroC/OS-III',
'Embedded Linux', 'Symbian', etc., are examples of RTOS employed in embedded
product development.
MP, CSE, 99
VCET
 EMBEDDED FIRMWARE
DEVELOPMENT LANGUAGES

Embedded firmware can be –

» a target processor/ controller specific language (Assembly language or

Low
level language) or

» a target processor/ controller independent language (C, C++,

JAVA, etc.) commonly known as High Level Language or

» a combination of Assembly and High level Language.

MP, CSE, 100

VCET
» Assembly Language Based Development:

» 'Assembly language' is the human readable notation of 'machine

language',
whereas 'machine language' is a processor understandable language.

» Processors deal only with binaries (1s and 0s). Machine language is a
binary
representation.

» Assembly language and machine languages are processor/ controller

dependent and an assembly program written for one processor/ controller
family will not work with others.

» Assembly language programming is the task of writing processor specific

machine code in mnemonic form, converting the mnemonics into actual
processor instructions (machine language) and associated data using an
assembler. MP, CSE, 101
VCET
» The general format of an assembly language instruction is
an Opcode followed by Operands.

» The Opcode tells the processor/ controller what to do and the Operands
provide the data and information required to perform the action specified by
the opcode.
 Example: MOV A, #30 – This instruction mnemonic moves decimal value 30 to
the 8051 Accumulator register. Here MOV A is the Opcode and 30 is the operand.
The same instruction when written in machine language: 01110100 00011110 –
where the first 8-bit binary value 01110100, represents the opcode MOV A and the
second 8-bit binary value 00011110 represents the operand 30.
 The mnemonic INC A is an example for instruction holding operand implicitly in
the Opcode. The machine language representation of the same is 00000100.

» Assembly language instructions are written one per line.

MP, CSE, 102

VCET
» A machine code program thus consists of a sequence of assembly language
instructions, where each statement contains a mnemonic (Opcode +
Operands).

» Each line of an assembly language program is split into four fields as given
below:

MP, CSE, 103

VCET
» The sample code given below using 8051 Assembly language illustrates the
structured assembly language programming. Each Assembly instruction
should be written in a separate line.

» The Assembly program contains a main routine and it may or may not
contain subroutines. The example given above is a subroutine, which can be
invoked by a main program by the Assembly instruction:

» Label can also be directly replaced by putting the desired address first and
then writing the Assembly code, as given below:

MP, CSE, 104

VCET
» The Assembly language program written in assembly code is saved
as .asm
(Assembly file) file or .src (source) file.

» Any text editor like 'notepad' or 'WordPad' from Microsoft® or the text editor
provide by an Integrated Development (IDE) tool can be used for writing the
assembly instructions.

» When a program is too complex or too big; the entire code can be divided
into sub-modules and each module can be re-usable (called as Modular
Programming). Modular programs are usually easy to code, debug and alter.

MP, CSE, 105

VCET
» Source File to Object File Translation: Translation of assembly code to
machine code is performed by assembler. Keil software is a popular
assembler for the 8051 family microcontroller.

MP, CSE, 106

VCET
» Library File Creation and Usage: Libraries are specially formatted, ordered
program collections of object modules that may be used by the linker at a
later time. When the linker processes a library, only those object modules in
the library that are necessary to create the program are used. Library files are
generated with extension '.lib'.
 Library is some kind of source code hiding technique. If you don't want to
reveal the source code behind the various functions you have written in your program
and at the same time you want them to be distributed to application developers for
making use of them in their applications, you can supply them as library files and give
them the details of the public functions available from the library (function name,
function input/output, etc). For using a library file in a project, add the library to the
project.
 'LIB51' from K eil Software is an example for a library creator and it is used for
creating library files for A51 Assembler/ C51 Compiler for 8051
specific MP, CSE,
VCET 107
» Linker and Locater: Linker and Locater is another software
utility
responsible for "linking the various object modules in a multi-module project
and assigning absolute address to each module".

» Linker is a program which combines the target program with the code of
other programs (modules) and library routines.

» During the process of linking, the absolute object module is created. The
object module contains the target code and information about other programs
and library routines that are required to call during the program execution.

» The absolute object file is used for creating hex files for dumping into the
code memory of the processor/ controller.
» 'BL51' from Keil Software is an example for a Linker & Locater for A51
Assembler/ C51 Compiler for 8051 specific controller.

MP, CSE, 108

VCET
» Object to Hex File Converter: Hex File is the representation of the machine
code and the hex file is dumped into the code memory of the processor/
controller.

» The hex file representation varies depending on the target processor/

controller make.
 For Intel processors/ controllers the target hex file format will be 'Intel
HEX' and for Motorola, the hex file should be in 'Motorola HEX' format.

» HEX files are ASCII files that contain a hexadecimal representation of target
application.

» Hex file is created from the final 'Absolute Object File' using the Object to
Hex File Converter utility.
» 'QH51' from Keil software is an example for Object to Hex File Converter
utility
for A51 Assembler/ C51 Compiler for
MP, 8051
VCET
CSE, specific controller. 109
» Advantages of Assembly » Drawbacks of Assembly
Language Based Development: Language Based Development:

» Efficient Code Memory and Data » High Development Time

Memory Usage (Memory » Developer
Optimization) Dependency

» High Performance » Non-Portable

» Low Level Hardware Access

» Code Reverse Engineering

MP, CSE, 110

VCET
» High Level Language Based
Development:
» Any high level language (like C, C++ or Java) with a supported cross
compiler (for converting the application developed in high level language to
target processor specific assembly code) for the target processor can be used
for embedded firmware development.
» The most commonly used high level language for embedded firmware application
development is 'C'.

» ‘C’ is the well defined, easy to use high level language with extensive cross platform
development tool support. Nowadays Cross-compilers for C+ + is also emerging out.

» The various steps involved in high level language based embedded firmware
development is same as that of assembly language based development;

» except that the conversion of source file written in high level language to
object file is done by a cross-compiler, whereas in Assembly language
based
development, it is carried out byMaP,nCSaEs, 111
» The various steps involved in the conversion of a program written in high
level language to corresponding binary file/ machine language is illustrated in
the following Figure.

MP, CSE, 112

VCET
» Advantages of High Level » Drawbacks of High Level
Language Based Development: Language Based Development:

» Reduced Development Time » Cross-compilers available for high

» Developer level languages may not be so

Independency efficient
» Portability » Investment required for high level
language based development tools

MP, CSE, 113

VCET
» Mixing Assembly and High Level language:

» Certain embedded firmware development situations may demand the

mixing of high level language with Assembly and vice versa.

» High level language and assembly languages are usually mixed in three
ways; namely,

» mixing Assembly Language with High Level Language,

» mixing High Level Language with Assembly and

» In-line Assembly programming.

MP, CSE, 114

VCET
» Mixing Assembly with High Level Language (e.g. Assembly Language with
‘C’): Assembly routines are mixed with 'C' in situations where the entire
program is written in 'C' and the cross-compiler do not have a built in support
for implementing certain features like Interrupt Service Routine functions
(ISR) or if the programmer wants to take advantage of the speed and
optimized code offered by machine code generated by hand written assembly
rather than cross compiler generated machine code.

» Mixing 'C' and Assembly is little complicated; in the sense-the programmer

must be aware of how parameters are passed from the 'C' routine to Assembly
and values a returned from assembly routine to 'C' and how 'Assembly
routine' is invoked from the 'C' code.

MP, CSE, 115

VCET
» The following steps givean idea howC51 cross-compiler performs
the mixing of Assembly code with 'C':

1. Write a simple function in C that passes parameters and returns values

the way you want your assembly routine to.

2. Use the SRC directive ( #PRAGMA SRC at the top of the file) so that
the
C compiler generates an .SRC file instead of an .OBJ file.

3. Compile the C file. Since the SRC directive is specified, the .SRC file is
generated. The .SRC file contains the assembly code generated for the C
code you wrote.

4. Rename the .SRC file to .A51 file.

5. Edit the .A51 file and insert the assembly code you want to execute in
the
body of the assembly function shell included in the .A51 file.
MP, CSE, 116
VCET
» Mixing High level language with Assembly (e.g. 'C' with
Assembly
Language): Mixing the code written in a high level language like 'C' and
Assembly language is useful in the following scenarios:
1. The source code is already available in Assembly language and a routine written
in a high level language like 'C' needs to be included to the existing code.

2. The entire source code is planned in Assembly code for various reasons like
optimized code, optimal performance, efficient code memory utilization and
proven expertise in handling the Assembly, etc. But some portions of the code
may be very difficult and tedious to code in Assembly. For example 16-bit
multiplication and division in 8051 Assembly Language.

3. To include built in library functions written in 'C' language provided by the cross
compiler. For example: Built in Graphics library functions and String operations
supported by 'C'.

MP, CSE, 117

VCET
» Inline Assembly: Inline assembly is another technique for inserting target
processor/ controller specific Assembly instructions at any location of a
source code written in high level language ‘C’.

» This avoids the delay in calling an assembly routine from a ‘C’ code.

» Special keywords are used to indicate the start and end of Assembly
instructions.

» C51 uses the keywords #pragma asm and #pragma endasm to indicate
a block of code written in assembly.

MP, CSE, 118

VCET
» ‘C’ versus ‘Embedded C’: 'C' is a well well
structured,
standardized general purpose programming defined and with
language
extensive
manipulation support.
» 'C' offers a combination of the features of high level languagebit
and assembly
and helps in hardware access programming (system level programming) as
well as business package developments (Application developments like pay
roll systems, banking applications, etc).

» The conventional 'C' language follows ANSI standard and it incorporates

various library files for different operating systems.

» A platform (operating system) specific application, known as, compiler is

used for the conversion of programs written in 'C' to the target processor (on
which the OS is running) specific binary files.

» Hence it is a platform specific development.

MP, CSE, 119
VCET
» Embedded C can be considered as a subset of conventional ‘C’ language.
Embedded C supports all 'C' instructions and incorporates a few target
processor specific functions/ instructions.

» It should be noted that the standard ANSI 'C' library implementation is always
tailored to the target processor/ controller library files in Embedded C.

» The implementation of target processor/ controller specific functions/

instructions depends upon the processor/ controller as well as supported
cross-compiler for the particular Embedded C language.

» A software program called 'Cross-compiler' is used for the conversion of

programs written in Embedded C to target processor/ controller specific
instructions (machine language).

MP, CSE, 120

VCET
 C Embedded C
C is a general purpose Embedded C is an extension of
programming C
language, which can be used to design language and used to
develop
any type of desktop-based applications.
microcontroller-based applications.
C language program is hardware Embedded C program is
hardware
independent.
dependent.
Embedded C requires specific
C language uses standard compilers to compilers that are able to generate
compile and execute the program. particular hardware/ microcontroller-
based output.

Readability, modifications, bug fixing, Readability, modifications, bug fixing,

etc., are very easy in a C language etc., are not easy in a Embedded
MP, CSE, 121
VCET C
» Compiler versus Cross-Compiler: Compiler is a software tool that converts a
source code written in a high level language on top of a particular operating
system running on specific target processor architecture (e.g. Intel x86/
Pentium).

» Here the operating system, the complier program and the application making
use of the source code run on the same target processor.

» The source code is converted to the target processor specific machine

instructions. The development is platform specific (OS as well as target
processor on which the OS is running).

» Compilers are generally termed as 'Native Compilers'. A native compiler

generates machine code for the same machine (processor) on which it is
running.

MP, CSE, 122

VCET
» Cross-compilers are software tools used in cross-platform development
applications.

» In cross-platform development, the compiler running on a particular target

processor/ OS converts the source code to machine code for a target processor
whose architecture and instruction set is different from the processor on
which the compiler is running or for an operating system which is different
from the current development environment OS.

» Embedded system development is a typical example for cross-platform

development where embedded firmware is developed on a machine with
Intel/ AMD or any other target processors and the same is converted into
machine code for any other target processor architecture (e.g. 8051, PIC,
ARM, etc.). Keil C51 is an example for cross-compiler.

MP, CSE, 123

VCET