Difference between revisions of "MansOS Platforms"
(→Platforms) |
(→Platforms) |
||
(19 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{TocRight}} |
|||
== Files == |
== Files == |
||
The executable and the object files are created by issuing a platform specific make and stored in build/platform directory. |
The executable and the object files are created by issuing a platform specific make and stored in build/*platform* directory. |
||
For example, |
|||
⚫ | |||
make telosb |
|||
⚫ | |||
make telosb upload |
|||
== Platforms == |
== Platforms == |
||
Line 9: | Line 13: | ||
Currently, MansOS supports the following platforms: |
Currently, MansOS supports the following platforms: |
||
* '''telosb''' - |
* '''[[Platforms_telosb | telosb]]''' - TelsoB, Tmote Sky, Taroko mote, and clones based on MSP430F1611 controller and CC2420 radio transceiver |
||
* '''[[Platforms_atmega | atmega]]''' - Atmega328 based platforms, such as Arduino |
|||
* '''[[Platforms_telosb | Z1]]''' - [http://www.zolertia.com/ti Zolertia Z1] mote |
|||
* '''[[Platforms_telosb | XM1000]]''' - [http://www.advanticsys.com/wiki/index.php?title=XM1000 Advanticsys XM1000] mote |
|||
* MSP430 Launchpad platform |
|||
<!-- * '''[[Platforms_msp430 | msp430]]''' - A generic platform supporting devices based on TI's MSP430 microcontrollers --> |
|||
<!-- * '''[[mansos:nrf | nrf]]''' - Nordic Semiconductors nRF24... devices --> |
|||
* '''[[Platforms_pc | pc]]''' - Used for simulation, a.k.a. virtual mote. |
|||
* '''[[Platforms_pcapp | pcapp]]''' - For executable applications running on a PC platform. |
|||
* Several other custom mote platforms, e.g. MSP430F1611-based SADmote, MSP430F2252-based Farmmote, and MSP430F2618-based TestBed mote. |
|||
* [[Platforms_Santa | santa]] - mote for steerable antenna array, telosb compatible. |
|||
<!-- |
|||
== 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 [[MansOS_configuration_options | 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 |
|||
* '''pc''' - 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. |
|||
* '''quiet''' - provide less verbose messages during the build process |
|||
* '''optimize''' - turn code optimization on if possible |
Latest revision as of 10:26, 11 April 2014
Contents |
Files
The executable and the object files are created by issuing a platform specific make and stored in build/*platform* directory. For example,
make telosb
will create a directory build/telosb with all the object files and the executable in it. Once it is successfully compiled, you may upload it to the target device with:
make telosb upload
Platforms
Currently, MansOS supports the following platforms:
- telosb - TelsoB, Tmote Sky, Taroko mote, and clones based on MSP430F1611 controller and CC2420 radio transceiver
- atmega - Atmega328 based platforms, such as Arduino
- Z1 - Zolertia Z1 mote
- XM1000 - Advanticsys XM1000 mote
- MSP430 Launchpad platform
- pc - Used for simulation, a.k.a. virtual mote.
- pcapp - For executable applications running on a PC platform.
- Several other custom mote platforms, e.g. MSP430F1611-based SADmote, MSP430F2252-based Farmmote, and MSP430F2618-based TestBed mote.
- santa - mote for steerable antenna array, telosb compatible.
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