Tinyos操作系统简介.docVIP

Tinyos操作系统简介 Tinyos简介 最近看了篇关于TinyOS简介的文章，摘录出来保存下，介绍tinyos编程入门的资料不少，但从操作系统 的角度分析tinyos是有必要的，毕竟TinyOS做为无线传感网络操作系统中最重要的一种，也是最常用的 一种，分析它的实现机制有助于以后改进针对无线传感网络的操作系统，也是嵌入式操作系统的一类。 An open-source operating system designed for wireless embedded sensor network. More specifically, it is designed to support the concurrency intensive operations required by networked sensors with minimal hardware requirements. TinyOS Features ? No Kernel: Direct hardware manipulation. ? No Process Management: Only one process on the fly. ? No Virtual Memory: Single linear physical address space. ? No S/w Signal or Exception: Function call instead. ? No User Interface, power constrained. ? Unusually application specific H/w and S/w. ? Multiple flows, concurrency intensive bursts. ? Extremely passive vigilance (power saving). ? Tightly coupled with the application. ? Simulator: TOSSIM, PowerTOSSIM ? Written in “nesC” Language, a dialect of the ?C? language. TinyOS uses multi-hop routing instead of point-to-point connections to save transmission power. Route discovery is done by 2-hop broadcast and topology discovery is based on shortest path from each node to the base station. ? The paradigm for network transmissions in TinyOS is active messaging. Messages contain a handler address and on arrival this handler is called. ? TinyOS Architecture ? Component Based Architecture: enables rapid innovation and implementation while minimizing code size as required by the severe memory constraints inherent in sensor networks. ? Small footprint: fits in 178 Bytes of memory. ? Event based instead of threaded architecture. start and stop are commands. fired is a event invoked by Timer. The interface specifies: Timer must implement startand stop, Application must implement fired. o Propagates events in time it takes to copy 1.25 Bytes. o Switches context in the time to copy 6 Bytes ofMemory. ? Radio and Clock have interrupts. ? Non-blocking/Non-preemptive Scheduling: Tasks will not pre