TinyOS is a chargeless and accessible antecedent component-based operating arrangement and belvedere targeting wireless sensor networks (WSNs). TinyOS is an anchored operating arrangement accounting in the nesC programming accent as a set of allied tasks and processes. It is advised to be congenital into smartdust. TinyOS started as a accord amid the University of California, Berkeley in co-operation with Intel Research and Crossbow Technology, and has back developed to be an all-embracing consortium, the TinyOS Alliance.
Thursday 8 December 2011
Implementation
TinyOS applications are accounting in nesC, a accent of the C accent optimized for the anamnesis banned of sensor networks. Its added accoutrement are mainly in the anatomy of Java and carapace calligraphy front-ends. Associated libraries and tools, such as the NesC compiler and Atmel AVR binutils toolchains, are mostly accounting in C.
TinyOS programs are congenital out ofcomputer application components, some of which present accouterments abstractions. Apparatus are affiliated to anniversary added application interfaces. TinyOS provides interfaces and apparatus for accepted abstractions such as packet communication, routing, sensing, actuation and storage.
TinyOS is absolutely non-blocking: it has one stack. Therefore, all I/O operations that aftermost best than a few hundred microseconds are asynchronous and accept a callback. To accredit the built-in compiler to more good optimize beyond alarm boundaries, TinyOS uses nesC's appearance to articulation these callbacks, alleged events, statically. While actuality non-blocking enables TinyOS to advance aerial accommodation with one stack, it armament programmers to address circuitous argumentation by bond calm abounding baby accident handlers. To abutment beyond computations, TinyOS provides tasks, which are agnate to a Deferred Procedure Alarm and arrest abettor basal halves. A TinyOS basic can column a task, which the OS will agenda to run later. Tasks are non-preemptive and run in FIFO order. This simple accommodation archetypal is about acceptable for I/O axial applications, but its adversity with CPU-heavy applications has led to the development of a cilia library for the OS, called TOSThreads.
TinyOS cipher is statically affiliated with affairs code, and aggregate into a baby binary, application a custom GNU toolchain. Associated utilities are provided to complete a development belvedere for alive with TinyOS
TinyOS programs are congenital out ofcomputer application components, some of which present accouterments abstractions. Apparatus are affiliated to anniversary added application interfaces. TinyOS provides interfaces and apparatus for accepted abstractions such as packet communication, routing, sensing, actuation and storage.
TinyOS is absolutely non-blocking: it has one stack. Therefore, all I/O operations that aftermost best than a few hundred microseconds are asynchronous and accept a callback. To accredit the built-in compiler to more good optimize beyond alarm boundaries, TinyOS uses nesC's appearance to articulation these callbacks, alleged events, statically. While actuality non-blocking enables TinyOS to advance aerial accommodation with one stack, it armament programmers to address circuitous argumentation by bond calm abounding baby accident handlers. To abutment beyond computations, TinyOS provides tasks, which are agnate to a Deferred Procedure Alarm and arrest abettor basal halves. A TinyOS basic can column a task, which the OS will agenda to run later. Tasks are non-preemptive and run in FIFO order. This simple accommodation archetypal is about acceptable for I/O axial applications, but its adversity with CPU-heavy applications has led to the development of a cilia library for the OS, called TOSThreads.
TinyOS cipher is statically affiliated with affairs code, and aggregate into a baby binary, application a custom GNU toolchain. Associated utilities are provided to complete a development belvedere for alive with TinyOS
History
TinyOS began as a activity at UC Berkeley as allotment of the DARPA NEST program. It has back developed to absorb bags of bookish and bartering developers and users worldwide. (list in about-face archival order)
April 2010: TinyOS 2.1.1 released.
August 2008: TinyOS 2.1.0 released.
July 2007: TinyOS 2.0.2 released. Assignment on TinyOS 2.1, which involves slight changes to a few interfaces, begins.
April 2007: TinyOS 2.0.1 appear at the 4th TinyOS Technology Exchange in Cambridge, MA.
November 2006: TinyOS 2.0 appear at the SenSys appointment in Boulder, CO.
July 2006: TinyOS 2.0 beta2 released.
February 2006: TinyOS 2.0 beta1 appear at the 3rd TinyOS Technology Exchange in Stanford, CA.
December 2005: TinyOS 1.1.15, the aftermost 1.1 version, is released.
July 2005: NEST activity concludes.
June 2004: Working accumulation forms on abutting accomplish for TinyOS, based on adventures porting to fresh platforms. Accumulation agrees to alpha assignment on 2.0.
September 2003 – December 2005: TinyOS begins a alternate accessory absolution process.
August 2003: TinyOS adaptation 1.1 is released, which includes fresh nesC appearance including abstracts chase detection.
September 2002: TinyOS adaptation 1.0, implemented in nesC, is released.
April 2002: Assignment on the nesC programming accent begins as a accord amid Intel Research and UC Berkeley.
February 2002: Berkeley distributes 1000 mica nodes to added participants in the NEST project.
2001: Berkeley develops the mica belvedere and releases TinyOS adaptation 0.6.
2000: Berkeley designs the rene belvedere and ally with Crossbow, Inc., who accumulation produces the hardware. TinyOS adaptation 0.43 is fabricated accessible to the accessible via SourceForge. Pre-1.0 versions of TinyOS are a mix of C and Perl scripts.
1999: First TinyOS belvedere (WeC) and OS implementations are developed at Berkeley.
April 2010: TinyOS 2.1.1 released.
August 2008: TinyOS 2.1.0 released.
July 2007: TinyOS 2.0.2 released. Assignment on TinyOS 2.1, which involves slight changes to a few interfaces, begins.
April 2007: TinyOS 2.0.1 appear at the 4th TinyOS Technology Exchange in Cambridge, MA.
November 2006: TinyOS 2.0 appear at the SenSys appointment in Boulder, CO.
July 2006: TinyOS 2.0 beta2 released.
February 2006: TinyOS 2.0 beta1 appear at the 3rd TinyOS Technology Exchange in Stanford, CA.
December 2005: TinyOS 1.1.15, the aftermost 1.1 version, is released.
July 2005: NEST activity concludes.
June 2004: Working accumulation forms on abutting accomplish for TinyOS, based on adventures porting to fresh platforms. Accumulation agrees to alpha assignment on 2.0.
September 2003 – December 2005: TinyOS begins a alternate accessory absolution process.
August 2003: TinyOS adaptation 1.1 is released, which includes fresh nesC appearance including abstracts chase detection.
September 2002: TinyOS adaptation 1.0, implemented in nesC, is released.
April 2002: Assignment on the nesC programming accent begins as a accord amid Intel Research and UC Berkeley.
February 2002: Berkeley distributes 1000 mica nodes to added participants in the NEST project.
2001: Berkeley develops the mica belvedere and releases TinyOS adaptation 0.6.
2000: Berkeley designs the rene belvedere and ally with Crossbow, Inc., who accumulation produces the hardware. TinyOS adaptation 0.43 is fabricated accessible to the accessible via SourceForge. Pre-1.0 versions of TinyOS are a mix of C and Perl scripts.
1999: First TinyOS belvedere (WeC) and OS implementations are developed at Berkeley.
Subscribe to:
Posts (Atom)