TinyOS CSE466 Final Project Presentation

Slides:



Advertisements
Similar presentations
How to use TinyOS Jason Hill Rob Szewczyk Alec Woo David Culler An event based execution environment for Networked Sensors.
Advertisements

NesC Prepared for the Multimedia Networks Group University of Virginia.
Chapter 13 Embedded Systems
Chapter 13 Embedded Systems Patricia Roy Manatee Community College, Venice, FL ©2008, Prentice Hall Operating Systems: Internals and Design Principles,
6/9/2015B.Ramamurthy1 Process Description and Control B.Ramamurthy.
How to Code on TinyOS Xufei Mao Advisor: Dr. Xiang-yang Li CS Dept. IIT.
Page 1 Processes and Threads Chapter Processes 2.2 Threads 2.3 Interprocess communication 2.4 Classical IPC problems 2.5 Scheduling.
1 TinyOS Mohammad Rahimi CSCI599-Spring Motivation  The new class of distributed tiny devices  The new generation of software.
Processes April 5, 2000 Instructor: Gary Kimura Slides courtesy of Hank Levy.
1 EE249 Discussion System Architecture Directions for Networked Sensors (J. Hill, et al) Presented By: Sarah Bergbreiter EE249 Discussion Section October.
CSI 400/500 Operating Systems Spring 2009 Lecture #2 – Functional Parts of an Operating System Monday January 23, 2009.
Chapter 13 Embedded Operating Systems Eighth Edition By William Stallings Operating Systems: Internals and Design Principles.
Computer Organization Review and OS Introduction CS550 Operating Systems.
April 15, 2005TinyOS: A Component Based OSPage 1 of 27 TinyOS A Component-Based Operating System for Networked Embedded Systems Tom Bush Graduate College.
 What is an operating system? What is an operating system?  Where does the OS fit in? Where does the OS fit in?  Services provided by an OS Services.
Recall: Three I/O Methods Synchronous: Wait for I/O operation to complete. Asynchronous: Post I/O request and switch to other work. DMA (Direct Memory.
Overview of: System Architecture Directions for Networked Sensors John Kerwin CSE 291 Sensor Networks Paper by: Jason Hill, Robert Szewczyk, Alec Woo,
Dhanshree Nimje Smita Khartad
Simulation of Distributed Application and Protocols using TOSSIM Valliappan Annamalai.
HANBACK ELECTRONICS CO., LTD. 저자권 보호됨 TinyOS & NesC.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition, Chapter 3: Process-Concept.
System Components ● There are three main protected modules of the System  The Hardware Abstraction Layer ● A virtual machine to configure all devices.
Concurrency, Processes, and System calls Benefits and issues of concurrency The basic concept of process System calls.
System Architecture Directions for Networked Sensors.
Why does it need? [USN] ( 주 ) 한백전자 Background Wireless Sensor Network (WSN)  Relationship between Sensor and WSN Individual sensors are very limited.
Software Architecture of Sensors. Hardware - Sensor Nodes Sensing: sensor --a transducer that converts a physical, chemical, or biological parameter into.
 Operating system.  Functions and components of OS.  Types of OS.  Process and a program.  Real time operating system (RTOS).
REAL-TIME OPERATING SYSTEMS
Module 12: I/O Systems I/O hardware Application I/O Interface
Chapter 19: Real-Time Systems
Processes and threads.
TrueTime.
Process concept.
Advanced Operating Systems CIS 720
Elaine Cheong Yang Zhao December 8, 2001
Lecture Topics: 11/1 Processes Process Management
Out-of-Process Components
IS310 Hardware & Network Infrastructure Ronny L
Real-time Software Design
CSCI 315 Operating Systems Design
Chapter 4: Threads.
Threads, SMP, and Microkernels
System Structure and Process Model
I/O Systems I/O Hardware Application I/O Interface
Operating System Concepts
13: I/O Systems I/O hardwared Application I/O Interface
CS703 - Advanced Operating Systems
Mid Term review CSC345.
Lecture Topics: 11/1 General Operating System Concepts Processes
Process Description and Control
Lecture 4- Threads, SMP, and Microkernels
Processes Hank Levy 1.
Process Description and Control
Top Half / Bottom Half Processing
Processes and Process Management
Process Description and Control
Chapter 19: Real-Time Systems
Process Description and Control
Process Description and Control
Process Description and Control
Chapter 13: I/O Systems I/O Hardware Application I/O Interface
Out-of-Process Components
Chapter 2 Processes and Threads 2.1 Processes 2.2 Threads
Process.
Process Description and Control
Chapter 2 Operating System Overview
CSE 153 Design of Operating Systems Winter 2019
Processes Hank Levy 1.
Modeling Event-Based Systems in Ptolemy II EE249 Project Status Report
Module 12: I/O Systems I/O hardwared Application I/O Interface
Presentation transcript:

TinyOS CSE466 Final Project Presentation Group members: Iliana Avila-Campillo Jason Dougherty Sze Ying Kong

Motivation Real-time w/ high level of concurrency High level of modularity Low power consumption Limited memory and CPU speed

Network Sensor Processor Application Active Messaging Component Sonar App_init Processor One instance of OS Application Sonar_start_read Sonar_read_done Active Messaging Component Sonar Component Echo (from HW)

Component Frame Command Handler A Command Handler B Task A Task C Commands Signals Command Handler A Command Handler B Frame Task A Task C Event Handler A Task B Task D Event Handler B Commands Events

Frames One per component Fixed size – allocated at compile time Persists across commands, events, tasks Stores state for component

Tasks Scheduled by OS Run to completion May be pre-empted by events (interrupts) Operate on frames Perform intensive computation

Event Handlers Respond to events – HW or SW Must execute quickly Operate on frames May post tasks May call commands May signal events

Commands Must execute reasonably quickly Operate on frames May call other commands May post tasks May NOT signal events

Implementation OS is comprised of a scheduler and some macros Scheduler is implemented as a circular FIFO queue Posting a task is effected by passing a function pointer to the OS

Implementation – 2 Component interface (events, commands) is described in a *.comp file Perl script generates a C header file from component file Component is implemented in a C source file OS and components are built together

Implementation – 3 Interconnections between components are described in *.desc files A Perl script generates a top-level header file from all description files A Java program uses all description files to generate a C file which performs the dynamic event dispatch

Larry’s Objectives Macros for use with static verification tools (not yet implemented, according to their slides) Run-time checking – none Exception Handling – none Semantic Checking – none