MansOS Platforms

Files

The executable and the object files are created by issuing a platform specific make and stored in build/platform directory. For instance,

make telosb

will create a directory build/telosb with all the object files and the executable in it.

Platforms

Currently, MansOS supports the following platforms:

• telosb - aka Tmote Sky, Taroko mote, and clones based on msp430F1611 controller and cc2420 transceiver

• atmega - Atmega328 based platforms, such as Arduino

• msp430 - a generic platform supporting devices based on TI's MSP430 microcontrollers

• nrf - Nordic Semiconductors nRF24... devices

• pc - used for simulation, a.k.a. virtual mote. Any PC platform that has a working gcc compiler for it. We have successfully compiled applications on Ubuntu and Mac systems, some work has been done in Windows-Cygwin environment.

• pcapp - For executable applications running on any PC platform that has a working gcc compiler for it. We have successfully compiled applications on Ubuntu and Mac systems, some work has been done in Windows-Cygwin environment.

Modules

MansOS may include a module in the build. A module is a sensor board or any other module that extends the platform in some way and has appropriate software written for it. The following modules are supported by MansOS;

• SeePoga - a color graphics LCD (in development)

• TextLcd - a text LCD, such as 2x8 characters (in development)

Options

You may configure the build process using the 'configure' file. In addition, some of the options may be included in the command line. For example:

make pc verbose

The following command line options override the configuration file:

• verbose - provide more verbose messages during the build process
• quiet - provide less verbose messages during the build process
• optimize - turn code optimization on if possible