Embedded System Design
`
`By
`Peter Marwedel
`
`1'4 il-
`
`.
`
`I
`t.
`
`I
`
`g
`
`.
`
`'
`
`--__
`
`I
`
`I
`
`I
`
`._
`
`'
`
`'
`
`H:
`
`r
`
`-
`
`I
`.".
`F
`...
`H.
`
`_
`-.|-- -_‘__'.L| 41'.
`.
`-L‘:_!_
`rill-Til. 4*":
`11.
`.
`I
`I’M-E
`
`:1. i'
`
`._-.
`-
`
`1..
`
`'
`
`1..
`
`_:
`
`.
`
`._'-
`
`.
`
`-
`
`'
`
`_'_
`
`.
`'
`
`.-
`
`'_ Springer
`
`Patent Owner, Bot M8 LLC - Ex. 2019, p. 1
`
`Patent Owner, Bot M8 LLC - Ex. 2019, p. 1
`
`

`

`A C.I.P. Catalogue record for this book is available from the Library of Congress.
`
`ISBN-10 1-4020-7690-8 (HB)
`ISBN-13 978-1-4020-7690-9 (HB)
`ISBN-10 0-387-29237-3 (PB)
`ISBN-13 978-0-387-29237-3 (PB)
`
`Published by Springer,
`P.O. Box 17, 3300 AA Dordrecht, The Netherlands.
`
`www.springeronline.com
`
`Printed on acid-free paper
`
`All Rights Reserved
`© 2006 Springer
`No part of this work may be reproduced, stored in a retrieval system, or transmitted
`in any form or by any means, electronic, mechanical, photocopying, microfilming, recording
`or otherwise, without written permission from the Publisher, with the exception
`of any material supplied specifically for the purpose of being entered
`and executed on a computer system, for exclusive use by the purchaser of the work.
`
`Printed in the Netherlands.
`
`Patent Owner, Bot M8 LLC - Ex. 2019, p. 2
`
`

`

`Introduction
`
`3
`
`Due to all the other constraints, this means that the code-size should
`be as small as possible for the intended application. This is especially
`true for systems on a chip (SoCs), systems for which all the informa-
`tion processing circuits are included on a single chip. If the instruction
`memory is to be integrated onto this chip, it should be used very effi-
`ciently.
`3 Run-time efficiency: The minimum amount of resources should be
`used for implementing the required functionality. We should be able to
`meet time constraints using the least amount of hardware resources and
`energy. In order to reduce the energy consumption, clock frequencies
`and supply voltages should be as small as possible. Also, only the
`necessary hardware components should be present. Components which
`do not improve the worst case execution time (such as many caches or
`memory management units) can be omitted.
`4 Weight: All portable systems must be of low weight. Low weight is
`frequently an important argument for buying a certain system.
`5 Cost: For high-volume embedded systems, especially in consumer
`electronics, competitiveness on the market is an extremely crucial is-
`sue, and efficient use of hardware components and the software devel-
`opment budget are required.
`
`These systems are dedicated towards a certain application.
`For example, processors running control software in a car or a train will
`always run that software, and there will be no attempt to run a computer
`game or spreadsheet program on the same processor. There are mainly two
`reasons for this:
`
`1 Running additional programs would make those systems less depend-
`able.
`2 Running additional programs is only feasible if resources such as mem-
`ory are unused. No unused resources should be present in an efficient
`system.
`
`Most embedded systems do not use keyboards, mice and large computer
`monitors for their user-interface. Instead, there is a dedicated user-inter-
`face consisting of push-buttons, steering wheels, pedals etc. Because of
`this, the user hardly recognizes that information processing is involved.
`Due to this, the new era of computing has also been characterized by the
`disappearing computer.
`
`Many embedded systems must meet real-time constraints. Not complet-
`ing computations within a given time-frame can result in a serious loss of
`
`Patent Owner, Bot M8 LLC - Ex. 2019, p. 3
`
`

`

`6
`
`EMBEDDED SYSTEM DESIGN
`
`Trains: For trains, the situation is similar to the one discussed for cars and
`airplanes. Again, safety features contribute significantly to the total value
`of trains, and dependability is extremely important.
`
`Telecommunication: Mobile phones have been one of the fastest grow-
`ing markets in the recent years. For mobile phones, radio frequency (RF)
`design, digital signal processing and low power design are key aspects.
`
`Medical systems: There is a huge potential for improving the medical
`service by taking advantage of information processing taking place within
`medical equipment.
`
`Military applications: Information processing has been used in military
`equipment for many years. In fact, some of the very first computers ana-
`lyzed military radar signals.
`
`Authentication systems: Embedded systems can be used for authentica-
`tion purposes.
`For example, advanced payment systems can provide more security than
`classical systems. The SMARTpen R(cid:2) [IMEC, 1997] is an example of such
`an advanced payment system (see fig. 1.2).
`
`Mixed−signal
`ASIC +
`transmitter
`to host PC
`
`Batteries
`
`Tilt−
`sensor
`
`Push−buttons
`
`Force−
`and
`acceleration−
`sensors
`
`Ink
`
`Figure 1.2. SMARTpen
`
`The SMARTpen is a pen-like instrument analyzing physical parameters
`while its user is signing. Physical parameters include the tilt, force and
`acceleration. These values are transmitted to a host PC and compared with
`information available about the user. As a result, it can be checked if both
`the image of the signature as well as the way it has been produced coincide
`with the stored information.
`Other authentication systems include finger print sensors or face recogni-
`tion systems.
`
`Consumer electronics: Video and audio equipment is a very important
`sector of the electronics industry. The information processing integrated
`into such equipment is steadily growing. New services and better qual-
`ity are implemented using advanced digital signal processing techniques.
`
`Patent Owner, Bot M8 LLC - Ex. 2019, p. 4
`
`

`

`Introduction
`
`7
`
`Many TV sets, multimedia phones, and game consoles comprise high-
`performance processors and memory systems. They represent special cases
`of embedded systems.
`
`Fabrication equipment: Fabrication equipment is a very traditional area in
`which embedded systems have been employed for decades. Safety is very
`important for such systems, the energy consumption is less a problem. As
`an example, fig. 1.3 (taken from Kopetz [Kopetz, 1997]) shows a container
`connected to a pipe. The pipe includes a valve and a sensor. Using the
`readout from the sensor, a computer may have to control the amount of
`liquid leaving the pipe.
`
`Figure 1.3. Controlling a valve
`
`The valve is an example of an actuator (see definition on page 2).
`
`Smart buildings: Information processing can be used to increase the com-
`fort level in buildings, can reduce the energy consumption within buildings,
`and can improve safety and security. Subsystems which traditionally were
`unrelated have to be connected for this purpose. There is a trend towards
`integrating air-conditioning, lighting, access control, accounting and dis-
`tribution of information into a single system. For example, energy can be
`saved on cooling, heating and lighting of rooms which are empty. Available
`rooms can be displayed at appropriate places, simplifying ad-hoc meetings
`and cleaning. Air condition noise can be reduced to a level required for the
`actual operating conditions. Intelligent usage of blinds can optimize light-
`ing and air-conditioning. Tolerance levels of air conditioning subsystems
`can be increased for empty rooms, and the lighting can be automatically
`reduced. Lists of non-empty rooms can be displayed at the entrance of
`the building in emergency situations (provided the required power is still
`available).
`Initially, such systems will mostly be present only in high-tech office build-
`ings.
`
`Robotics: Robotics is also a traditional area in which embedded systems
`have been used. Mechanical aspects are very important for robots. Most of
`
`Patent Owner, Bot M8 LLC - Ex. 2019, p. 5
`
`

`

`Chapter 3
`
`EMBEDDED SYSTEM HARDWARE
`
`3.1
`
`Introduction
`
`It is one of the characteristics of embedded systems that both hardware and
`software must be taken into account. The reuse of available hard- and software
`components is at the heart of the proposed platform-based design method-
`ology. The methodology will be described starting at page 151. Consistent
`with the need to consider available hardware components and with the design
`information flow shown in fig. 3.1, we are now going to describe some of the
`essentials of embedded system hardware.
`
`HW−components
`
`hardware−design
`
`hardware
`
`specification
`
`standard software
`(RTOS, ...)
`
`implementation: hw/sw codesign
`− task concurrency management
`− high−level transformations
`− design space exploration
`− hardware/software partitioning
`− compilation, scheduling
`
`realization
`
`software
`
`...
`
`(from all phases)
`
`...
`
`...
`
`...
`
`validation; evaluation (performance, energy consumption, safety, ..)
`
`application knowledge
`
`Figure 3.1. Simplified design information flow
`
`Hardware for embedded systems is much less standardized than hardware for
`personal computers. Due to the huge variety of embedded system hardware, it
`is impossible to provide a comprehensive overview over all types of hardware
`
`87
`
`Patent Owner, Bot M8 LLC - Ex. 2019, p. 6
`
`

`

`Chapter 5
`
`IMPLEMENTING EMBEDDED SYSTEMS:
`HARDWARE/SOFTWARE CODESIGN
`
`Once the specification has been completed, design activities can start. This is
`consistent with the simplified design information flow (see fig. 5.1).
`
`HW−components
`
`hardware−design
`
`hardware
`
`specification
`
`standard software
`(RTOS, ...)
`
`implementation: hw/sw codesign
`− task concurrency management
`− high−level transformations
`− design space exploration
`− hardware/software partitioning
`− compilation, scheduling
`
`realization
`
`software
`
`...
`
`(from all phases)
`
`...
`
`...
`
`...
`
`validation; evaluation (performance, energy consumption, safety, ..)
`
`application knowledge
`
`Figure 5.1. Simplified design information flow
`
`It is a characteristic of embedded systems that both hardware and software
`have to be considered during their design. Therefore, this type of design is
`also called hardware/software codesign. The overall goal is to find the right
`combination of hardware and software resulting in the most efficient product
`meeting the specification. Therefore, embedded systems cannot be designed
`by a synthesis process taking only the behavioral specification into account.
`Rather, available components have to be accounted for. There are also other
`reasons for this constraint: in order to cope with the increasing complexity of
`embedded systems and their stringent time-to-market requirements, reuse is
`essentially unavoidable. This led to the term platform-based design:
`
`151
`
`Patent Owner, Bot M8 LLC - Ex. 2019, p. 7
`
`