DOC PREVIEW
UB CSE 321 - LecSept2

This preview shows page 1-2-14-15-29-30 out of 30 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Slide 1OutlineDefining RTOSLets define realtime systemsRTOS Definition (contd.)RTOS Definition (contd.)Types of RTOSMicroprocessorEmbedded SystemsEmbedded SystemsEmbedded Systems (contd.)ExamplesRealtime Embedded SystemsClass work #1Embedded SystemsDesigning RTOSFunctional and non-functional requirementsHardware RequirementsSoftware requirementsSoftware Quality AssuranceDesign RepresentationDesign ConsiderationsClass work #2Finite State Machine (FSM)Design methods: Finite state machinesDrone aircraft avionics (simplified)State Transition tableLets design a simple embedded/ realtime systemSummaryRecitations & Course workB . R A M A M U R T H YU N I V E R S I T Y AT B U F FA L OB I N A @ B U F FA L O. E D U01/14/20191CSE321: Realtime and Embedded SystemsCSE321-2015-1Outline01/14/20192What is a realtime system?What is an embedded system?What is a realtime embedded system?Embedded system but not a realtime systemRealtime system but not an embedded systemWhy realtime&/embedded system?How do realtime embedded systems differ from regular computational systems?Lets define and identify some examples of realtime embedded systems in your school/work/home environment.We will attempt a simple design process.CSE321-2015-101/14/20193Defining RTOSCSE321-2015-101/14/20194Lets define realtime systemsTiming: RT systems (RTOS) are required to compute and deliver correct results within a specified period of time. Ex: traffic light controllerInterrupt driven: event-driven preemption; RTOS are often involved with handling events. Events manifest themselves in terms of interrupt signals arising from the arrival data at an input port or ticking of a hardware clock, or an error status alarm.CSE321-2015-101/14/20195RTOS Definition (contd.)Low-level programming: RTOS often deal with devices; C language is still a favorite for writing device drivers for new hardware.Specialized hardware: Most RTOS work within, or at least close beside, specialized electronic and mechanical devices. Often closed loop systems. Volatile data IO: Variables that change their value from moment to moment. RTOS software must be structured to check for changes at the correct rate, so as not to miss a data update.CSE321-2015-101/14/20196RTOS Definition (contd.)Multi-tasking: RTOS are often multitasking. Several processes cooperate to carry out the overall job. Divide RTOS problem into tasks as a design strategy.Run-time scheduling: Separation of activities into tasks leads to question of task sequencing or scheduling. Moreover the external events and required response to these lead to run-time scheduling or dynamic scheduling.Unpredictability in inputs/stimulus: Being event-driven, RTOS are at the mercy of unpredictable changes in their environment.Predictability response requirement!Life-critical code: failure to run correctly may result in death or at least injury to the user and/or others. Life-critical systems requires extra testing, documentation and acceptance trials.CSE321-2015-101/14/20197Types of RTOSHard RTOS: tight limits on response time, so that a delayed result is a wrong result.Ex: jet fuel controller and camera shutter unitSoft RTOS: need to meet only time-average performance target. As long as most results are available before deadline the system will run successfully. Ex: audio and video transmission, single frame skip is fine, but repeated loss is unacceptableFirm RTOS: somewhere between the two.Ex: Space station solar panel unitCSE321-2015-101/14/20198MicroprocessorExamples: vending machines, mobiles phones, alarm systems, washing machines, motor car engine controllers, heart monitors, microwave ovens all operate using embedded microcontrollers running dedicated software.“Microprocessor” is one of the critical enabling hardware for realtime systems.CSE321-2015-1Embedded Systems01/14/20199Dedicated functionallySpecial purposeOptimized for a certain operationsSmall (typically)Lower power consumptionEmbedded within other large systemsCSE321-2015-1Embedded Systems•Embedded systems are computing systems with tightly coupled hardware and software integration.•Designed to perform dedicated function•Embedded means that the system is a integral part of a larger system•Multiple embedded systems can co-exist in a single system.•General purpose processor are typically not aware of the applications.•An embedded processor is application-aware.01/14/201910CSE321-2015-1Embedded Systems (contd.)•Hardware and software co-design: hardware and software for the embedded system are developed in parallel.•Cross-platform development: Both embedded system and its application use the cross-platform development method.–Software is developed on one platform but runs on another.•Software storage will have to be chosen to allow for upgradeability.•Of course, the SoC (system on a chip), PoE (Power on Ethernet), etc.01/14/201911CSE321-2015-1Examples01/14/201912From everyday applicationsFrom automotive domain: Electronic Control Unit (ECU)Any examples?CSE321-2015-1Realtime Embedded Systems01/14/201913RTOS EMBRTEMBRailway monitoring and scheduling : RTOSCell phone: EMBHeart pacemaker: RTSEMBCSE321-2015-1Class work #101/14/201914Lets identify 10 embedded systems, realtime systems and realtime/embedded systemI will begin with Arduino Uno Example Type; justificationCSE321-2015-1Embedded Systems01/14/201915CSE321-2015-1W H E R E D O Y O U B E G I N ?A N S : R E Q U I R E M E N T S01/14/201916Designing RTOSCSE321-2015-1Functional and non-functional requirements01/14/201917Functional: Describes the explicit operations to be performed by the RTOS.If you consider the climate control system in an automobile:Sense temperature: T1Compare with user set temperature: TsetIf T1 > Tset, start cold air fan Else if T1 < Tset, start hot air fanNon-functional: describes the quality of the operationsExample: Need to control temperature within 0.5 degree errorAccuracy PrecisionReliabilitySafetyResponse timeResponsivenessPredictabilityDeadlinesCSE321-2015-1Hardware Requirements01/14/201918Hardware support for functional requirementsHardware support for non-functional requirementsSize of the device Power of the processorPower consumptionSpeed of the deviceSupport for devices, interruptsElectronic Control Units (ECU): typical modern automobile


View Full Document

UB CSE 321 - LecSept2

Documents in this Course
Anomaly1

Anomaly1

48 pages

ProcSept9

ProcSept9

17 pages

CRCNov23

CRCNov23

14 pages

Load more
Download LecSept2
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view LecSept2 and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view LecSept2 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?