High Performance Embedded Computing © 2007 Elsevier Lecture 5: Embedded Systems Issues Embedded Computing Systems Mikko Lipasti, adapted from M. Schulte.

Slides:



Advertisements
Similar presentations
Copyright 2007 Koren & Krishna, Morgan-Kaufman Part.1.1 FAULT TOLERANT SYSTEMS Part 1 - Introduction.
Advertisements

Distributed Systems Brief Overview CNT Mobile & Pervasive Computing Dr. Sumi Helal University of Florida.
Making Services Fault Tolerant
SWE Introduction to Software Engineering
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 30 Slide 1 Security Engineering.
Last Class: Weak Consistency
1 Software Fault Protection Allen Goldberg Kestrel Technology.
1 FM Overview of Adaptation. 2 FM RAPIDware: Component-Based Design of Adaptive and Dependable Middleware Project Investigators: Philip McKinley, Kurt.
©Ian Sommerville 2006Critical Systems Slide 1 Critical Systems Engineering l Processes and techniques for developing critical systems.
Chapter 13: I/O Systems I/O Hardware Application I/O Interface
IEEE and Zigbee Overview. Topics ZigBee Competing Technologies Products Some Motorola Projects Slide 2Joe Dvorak, Motorola9/27/05.
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
Software faults & reliability Presented by: Presented by: Pooja Jain Pooja Jain.
Reliability and Fault Tolerance Setha Pan-ngum. Introduction From the survey by American Society for Quality Control [1]. Ten most important product attributes.
2. Fault Tolerance. 2 Fault - Error - Failure Fault = physical defect or flow occurring in some component (hardware or software) Error = incorrect behavior.
Chapter 10 – Sociotechnical Systems 1Chapter 10 Sociotechnical Systems.
March 13, 2001CSci Clark University1 CSci 250 Software Design & Development Lecture #15 Tuesday, March 13, 2001.
FMEA-technique of Web Services Analysis and Dependability Ensuring Anatoliy Gorbenko Vyacheslav Kharchenko Olga Tarasyuk National Aerospace University.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Slide 1 Critical Systems Specification 2.
The Basic Input/Output System Unit objectives: Access the BIOS setup utility, change hardware configuration values, and research BIOS updates Explain the.
High Performance Embedded Computing © 2007 Elsevier Chapter 1, part 4: Embedded Computing High Performance Embedded Computing Wayne Wolf.
Software Reliability SEG3202 N. El Kadri.
Software is:  Computer programs, procedures, and possibly associated documentation and data relates to the operation of a computer system. [IEEE_Std_ ]
CSE 403 Lecture 14 Safety and Security Requirements.
Computer Science Open Research Questions Adversary models –Define/Formalize adversary models Need to incorporate characteristics of new technologies and.
Data Fusion & Multi-Sensors in Power Grids Rabinder N. Madan FIEEE Program Manager, Systems Theory Office of Naval Research.
© 2009 Research In Motion Limited Advanced Java Application Development for the BlackBerry Smartphone Trainer name Date.
Distributed Systems: Concepts and Design Chapter 1 Pages
Lecture on Computer Science as a Discipline. 2 Computer “Science” some people argue that computer science is not a science in the same sense that biology.
High Performance Embedded Computing © 2007 Elsevier Lecture 3: Design Methodologies Embedded Computing Systems Mikko Lipasti, adapted from M. Schulte Based.
Architectures of distributed systems Fundamental Models
Copyright John C. Knight SOFTWARE ENGINEERING FOR DEPENDABLE SYSTEMS John C. Knight Department of Computer Science University of Virginia.
 CS 5380 Software Engineering Chapter 11 Dependability and Security.
Networks Of Mobile Arbitrary Devices (NOMADs) Miroslaw Malek Humboldt-University Berlin, Germany
Advanced Computer Networks Topic 2: Characterization of Distributed Systems.
Part.1.1 In The Name of GOD Welcome to Babol (Nooshirvani) University of Technology Electrical & Computer Engineering Department.
Fault Tolerance David Powell LAAS-CNRS, Toulouse.
Lecture 4: Sun: 23/4/1435 Distributed Operating Systems Lecturer/ Kawther Abas CS- 492 : Distributed system & Parallel Processing.
Building Dependable Distributed Systems Chapter 1 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University
Safety-Critical Systems 7 Summary T V - Lifecycle model System Acceptance System Integration & Test Module Integration & Test Requirements Analysis.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Slide 1 Critical Systems Specification 1.
1 Component reliability Jørn Vatn. 2 The state of a component is either “up” or “down” T 1, T 2 and T 3 are ”Uptimes” D 1 and D 2 are “Downtimes”
Fault-Tolerant Computing Systems #4 Reliability and Availability
Nonbehavioral Specifications Non-behavioral Characteristics Portability Portability Reliability Reliability Efficiency Efficiency Human Engineering.
© Chinese University, CSE Dept. Distributed Systems / Distributed Systems Topic 1: Characterization of Distributed & Mobile Systems Dr. Michael R.
Slide 1 Security Engineering. Slide 2 Objectives l To introduce issues that must be considered in the specification and design of secure software l To.
DSN & SensorWare Projects Rockwell Science Center –Charles Chien UCLA –Mani Srivastava, Miodrag Potkonjak USC/ISI –Brian Schott, Bob Parker Virginia Tech.
Middleware for Fault Tolerant Applications Lihua Xu and Sheng Liu Jun, 05, 2003.
COP 5611 Operating Systems Spring 2010 Dan C. Marinescu Office: HEC 439 B Office hours: M-Wd 1:00-2:00 PM.
Topic: Reliability and Integrity. Reliability refers to the operation of hardware, the design of software, the accuracy of data or the correspondence.
CS203 – Advanced Computer Architecture Dependability & Reliability.
Seminar On Rain Technology
Pritee Parwekar. Requirements and Standards Some requirements for WSN deployment include: –Fault tolerance –Lifetime –Scalability –Real-time data.
SRA 2016 – Strategic Research Challenges Design Methods, Tools, Virtual Engineering Jürgen Niehaus, SafeTRANS.
Software Metrics and Reliability
Outline Introduction Background Distributed DBMS Architecture
Fault Tolerance & Reliability CDA 5140 Spring 2006
Fault Tolerance In Operating System
Software Reliability: 2 Alternate Definitions
COP 5611 Operating Systems Fall 2011
QNX Technology Overview
Reliability and Fault Tolerance
Automotive Embedded System
COP 5611 Operating Systems Spring 2010
InCheck: An In-application Recovery Scheme for Soft Errors
Architectures of distributed systems
Definitions Cumulative time to failure (T): Mean life:
Seminar on Enterprise Software
Presentation transcript:

High Performance Embedded Computing © 2007 Elsevier Lecture 5: Embedded Systems Issues Embedded Computing Systems Mikko Lipasti, adapted from M. Schulte Based on slides and textbook from Wayne Wolf

© 2006 Elsevier Topics Reliability, safety, and security. Consumer electronics.

© 2006 Elsevier Related disciplines Reliable/dependable system design creates systems that function even in the face of internal or external errors. Security concentrates on malicious attacks. Safety-critical system design develops methods to ensure that systems operate safely under a wide variety of error conditions.

© 2006 Elsevier Dependability and security After Avizienis et al. [Avi04]

© 2006 Elsevier Reliability requirements on embedded systems Safety-critical or high-reliability applications:  Automotive.  Aviation.  Medicine.  Critical communications. Many high-reliability applications require distributed embedded systems. Embedded systems may be vulnerable to new types of attacks.

© 2006 Elsevier Faults Faults may cause errors; reliable systems recover from faults. A fault may be transient or permanent. Types of faults:  Physical faults from manufacturing defects, radiation hazards, etc.  Design faults from improperly designed systems.  Operational faults from human error, security breaches, etc.

© 2006 Elsevier Mean time to failure Mean time to failure (MTTF) is the expected time for first system to fail: Reliability function, R(t) describes the probability that the system will operate correctly in the time interval [0,t].

© 2006 Elsevier Common fault distributions The hazard function, z(t), is the failure rate of components. Bathtub distributions are often empirically observed.  High failure rates at beginning, end of component life.

© 2006 Elsevier Possible actions after a fault Fail. Detect. Correct. Recover. Contain. Reconfigure. Restart. Repair.

© 2006 Elsevier Reliability methods Error-correction codes. Voting systems.  Triple-modular redundancy uses majority voting. Watchdog timer must be periodically reset by system to show that system operates correctly. Design diversity uses redundancy implemented in different types of components.

© 2006 Elsevier Novel attacks Embedded systems provide physical access, a key avenue for attack. Internet-enabled embedded systems provide remote access to attackers.  Example: Internet-enabled automobiles. Battery attacks exercise the system to wear out a battery. Quality-of-service attacks interfere with real- time behavior.

© 2006 Elsevier Power attack Developed by Kocher et al. Measure CPU current to determine instructions, data, key values. High-leakage devices are less vulnerable to power attacks. How might power attacks be prevented?

© 2006 Elsevier Consumer electronics architectures Consumer electronics pushes the edge of the envelope in several directions:  Complex functionality and high performance.  Often battery-powered.  Very low cost. Generally include one or more standards. We will discuss Bluetooth – the book provides additional examples.

© 2006 Elsevier Bluetooth Personal-area network.  2.5 GHz band.  Generally within 2 meters, may be extended to 30 meters. Basic network is master-slave, but higher levels of protocol stack provide peer-to-peer operation.

© 2006 Elsevier Bluetooth stack

© 2006 Elsevier Bluetooth middleware group protocol RFCOMM provides serial interface; compatible with RS-232. Service discovery protocol discovers services (printing, etc.) on the network. What types of characteristics would you expect to find in a processor for Bluetooth devices?