Page 1 Embedded Systems Design: A Unified Hardware/Software Introduction 1 Chapter 1: Introduction Page 2 Embedded Systems Design: A Unified Hardware/Software Introduction 1 Chapter 1: Introduction Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 2 Outline • Embedded systems overview – What are they? • Design challenge – optimizing design metrics • Technologies – Processor technologies – IC technologies – Design technologies Page 3 Embedded Systems Design: A Unified Hardware/Software Introduction 1 Chapter 1: Introduction Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 2 Outline • Embedded systems overview – What are they? • Design challenge – optimizing design metrics • Technologies – Processor technologies – IC technologies – Design technologies Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 3 Embedded systems overview • Computing systems are everywhere • Most of us think of “desktop” computers – PC’s – Laptops – Mainframes – Servers • But there’s another type of computing system – Far more common. Page 4 Embedded Systems Design: A Unified Hardware/Software Introduction 1 Chapter 1: Introduction Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 2 Outline • Embedded systems overview – What are they? • Design challenge – optimizing design metrics • Technologies – Processor technologies – IC technologies – Design technologies Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 3 Embedded systems overview • Computing systems are everywhere • Most of us think of “desktop” computers – PC’s – Laptops – Mainframes – Servers • But there’s another type of computing system – Far more common.

Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 4 Embedded systems overview • Embedded computing systems – Computing systems embedded within electronic devices – Hard to define. Nearly any computing system other than a desktop computer – Billions of units produced yearly, versus millions of desktop units – Perhaps 50 per household and per automobile Computers are in here.

And even here. Lots more of these, though they cost a lot less each. Page 5 Embedded Systems Design: A Unified Hardware/Software Introduction 1 Chapter 1: Introduction Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 2 Outline • Embedded systems overview – What are they? • Design challenge – optimizing design metrics • Technologies – Processor technologies – IC technologies – Design technologies Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 3 Embedded systems overview • Computing systems are everywhere • Most of us think of “desktop” computers – PC’s – Laptops – Mainframes – Servers • But there’s another type of computing system – Far more common. Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 4 Embedded systems overview • Embedded computing systems – Computing systems embedded within electronic devices – Hard to define.

May 28, 2017. Point-of-sale systems. Portable video games. Satellite phones. Smart ovens/dishwashers. Speech recognizers. Stereo systems. Teleconferencing systems. Givargis, Embedded System Design: A Unified Hardware Software Approach. Kris Kuchcinski (LTH).

Nearly any computing system other than a desktop computer – Billions of units produced yearly, versus millions of desktop units – Perhaps 50 per household and per automobile Computers are in here. And even here. Lots more of these, though they cost a lot less each.

Page 1 Embedded Systems Design: A Unified Hardware/Software Introduction 1 Chapter 8: State Machine and Concurrent Process Model Page 2 Embedded Systems Design: A Unified Hardware/Software Introduction 1 Chapter 8: State Machine and Concurrent Process Model Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 2 Outline • Models vs. Languages • State Machine Model – FSM/FSMD – HCFSM and Statecharts Language – Program-State Machine (PSM) Model • Concurrent Process Model – Communication – Synchronization – Implementation • Dataflow Model • Real-Time Systems Page 3 Embedded Systems Design: A Unified Hardware/Software Introduction 1 Chapter 8: State Machine and Concurrent Process Model Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 2 Outline • Models vs. Lego Batman 2 Full Movie Download more.

Languages • State Machine Model – FSM/FSMD – HCFSM and Statecharts Language – Program-State Machine (PSM) Model • Concurrent Process Model – Communication – Synchronization – Implementation • Dataflow Model • Real-Time Systems Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 3 • Describing embedded system’s processing behavior – Can be extremely difficult • Complexity increasing with increasing IC capacity – Past: washing machines, small games, etc. • Hundreds of lines of code – Today: TV set-top boxes, Cell phone, etc. • Hundreds of thousands of lines of code • Desired behavior often not fully understood in beginning – Many implementation bugs due to description mistakes/omissions – English (or other natural language) common starting point • Precise description difficult to impossible • Example: Motor Vehicle Code – thousands of pages long. Introduction Page 4 Embedded Systems Design: A Unified Hardware/Software Introduction 1 Chapter 8: State Machine and Concurrent Process Model Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 2 Outline • Models vs. Languages • State Machine Model – FSM/FSMD – HCFSM and Statecharts Language – Program-State Machine (PSM) Model • Concurrent Process Model – Communication – Synchronization – Implementation • Dataflow Model • Real-Time Systems Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 3 • Describing embedded system’s processing behavior – Can be extremely difficult • Complexity increasing with increasing IC capacity – Past: washing machines, small games, etc. • Hundreds of lines of code – Today: TV set-top boxes, Cell phone, etc. • Hundreds of thousands of lines of code • Desired behavior often not fully understood in beginning – Many implementation bugs due to description mistakes/omissions – English (or other natural language) common starting point • Precise description difficult to impossible • Example: Motor Vehicle Code – thousands of pages long.

Introduction Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 4 An example of trying to be precise in English • California Vehicle Code – Right-of-way of crosswalks • 21950. (a) The driver of a vehicle shall yield the right-of-way to a pedestrian crossing the roadway within any marked crosswalk or within any unmarked crosswalk at an intersection, except as otherwise provided in this chapter. • (b) The provisions of this section shall not relieve a pedestrian from the duty of using due care for his or her safety. No pedestrian shall suddenly leave a curb or other place of safety and walk or run into the path of a vehicle which is so close as to constitute an immediate hazard. No pedestrian shall unnecessarily stop or delay traffic while in a marked or unmarked crosswalk. Typing Tutor Free Download For Windows 7 32 Bit.

• (c) The provisions of subdivision (b) shall not relieve a driver of a vehicle from the duty of exercising due care for the safety of any pedestrian within any marked crosswalk or within any unmarked crosswalk at an intersection. – All that just for crossing the street (and there’s much more)! Page 5 Embedded Systems Design: A Unified Hardware/Software Introduction 1 Chapter 8: State Machine and Concurrent Process Model Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 2 Outline • Models vs.

Languages • State Machine Model – FSM/FSMD – HCFSM and Statecharts Language – Program-State Machine (PSM) Model • Concurrent Process Model – Communication – Synchronization – Implementation • Dataflow Model • Real-Time Systems Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 3 • Describing embedded system’s processing behavior – Can be extremely difficult • Complexity increasing with increasing IC capacity – Past: washing machines, small games, etc. • Hundreds of lines of code – Today: TV set-top boxes, Cell phone, etc. • Hundreds of thousands of lines of code • Desired behavior often not fully understood in beginning – Many implementation bugs due to description mistakes/omissions – English (or other natural language) common starting point • Precise description difficult to impossible • Example: Motor Vehicle Code – thousands of pages long. Introduction Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 4 An example of trying to be precise in English • California Vehicle Code – Right-of-way of crosswalks • 21950.

(a) The driver of a vehicle shall yield the right-of-way to a pedestrian crossing the roadway within any marked crosswalk or within any unmarked crosswalk at an intersection, except as otherwise provided in this chapter. • (b) The provisions of this section shall not relieve a pedestrian from the duty of using due care for his or her safety. No pedestrian shall suddenly leave a curb or other place of safety and walk or run into the path of a vehicle which is so close as to constitute an immediate hazard. No pedestrian shall unnecessarily stop or delay traffic while in a marked or unmarked crosswalk. • (c) The provisions of subdivision (b) shall not relieve a driver of a vehicle from the duty of exercising due care for the safety of any pedestrian within any marked crosswalk or within any unmarked crosswalk at an intersection.

– All that just for crossing the street (and there’s much more)! Embedded Systems Design: A Unified Hardware/Software Introduction, (c) 2000 Vahid/Givargis 5 Models and languages • How can we (precisely) capture behavior? – We may think of languages (C, C++), but computation model is the key • Common computation models: – Sequential program model • Statements, rules for composing statements, semantics for executing them – Communicating process model • Multiple sequential programs running concurrently – State machine model • For control dominated systems, monitors control inputs, sets control outputs – Dataflow model • For data dominated systems, transforms input data streams into output streams – Object-oriented model • For breaking complex software into simpler, well-defined pieces.