Difference between revisions of "MansOS"

From DiLab
Jump to: navigation, search
(Development with MansOS - tools and techniques)
Line 45: Line 45:
=== Development with MansOS - tools and techniques ===
=== Development with MansOS - tools and techniques ===


* [http://jupiter.cs.fmf.lu.lv/~kursi/bst/mansos/MansOS-API.pdf MansOS API (pdf)]
* MansOS [[MansOS_Ref | Reference Guide]] and [http://jupiter.cs.fmf.lu.lv/~kursi/bst/mansos/MansOS-API.pdf API (pdf)]
* [[MansOS_Apps_examples | Application examples]]
* [[MansOS_Apps_examples | Application examples]]
* [[MansOS_Makefiles | Setting up and using Makefiles]]
* [[MansOS_Makefiles | Setting up and using Makefiles]]
Line 51: Line 51:
* [[MansOS_Testing | Debugging and testing]]
* [[MansOS_Testing | Debugging and testing]]
* [[MansOS_FAQ | FAQ]]
* [[MansOS_FAQ | FAQ]]



=== Developing the MansOS - notes ===
=== Developing the MansOS - notes ===

Revision as of 14:37, 27 August 2010

MansOS is an operating system for wireless sensor networks.

MansOS = Mobile agent netted sensor Operating System

MansOS is a branch from LiteOS operating system, initially made to support TI Msp430 based platforms. Both OS share several defining characteristics. MansOS like LiteOS is designed to be easily adopted by the system designers and IT community familiar with C and C++ languages and Unix operating system concepts. The goal is to avoid the steep learning curve present in some other specialized operating systems.


Key concepts common with [LiteOS]:

  • MansOS is adopting programming in C (and eventually C++), known to many developers
  • MansOS is managing a sensor network using Unix-like concepts, command tools and resources
  • MansOS has a Unix-like file system (in development)
  • MansOS enables thread-like programming environment (in development)


Some key aspects specific to MansOS:

  • MansOS is designed to be easily portable to new platforms
  • Debugging support is integral part of MansOS: for example, Simple Sensor Management Protocol and Print Anywhere (over the serial or radio link) techniques help with debugging tasks.
  • MansOS has PC as one of the supported platforms, enabling rapid development and high-level simulation and debugging on PC and Mac class computers.
  • MansOS enforces the hardware abstraction in three layers: HPL, HAL, and HIL at a mote level, ensuring clear interface for ease of portability to other platforms
  • MansOS introduces a device concept similar to Unix systems. Access to most resources and sensors can be done through the device interface, using standard API including open, close, read, write and configure functions.
  • Future goal: The focus during the development should be the whole system - a collection of mote entities rather than a single mote


General


Access (Download)

  • MansOS SVN repository is open to public for reading. For example, to get the whole MansOS tree in the current-directory/mansos do this:
svn co http://mansos.net/svn/mansos/ mansos
  • Authenticated developers may access the MansOS_SVN repository via svn+ssh.
svn co svn+ssh://yourloginname@mansos.net/svn/mansos mansos
http://mansos.net/trac


Development with MansOS - tools and techniques

Developing the MansOS - notes


Internals


Hardware notes

Chips

Platforms


Related publications and papers