Difference between revisions of "MansOS Platforms"
(→Files) |
(→Platforms) |
||
| (11 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 |
For example, |
||
make telosb |
make telosb |
||
will create a directory '''build/telosb''' with all the object files and the executable in it. |
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 == |
== Platforms == |
||
| Line 10: | 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_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 |
|||
* '''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. |
|||
* MSP430 Launchpad platform |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
* '''[[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 == |
== Modules == |
||
| Line 29: | Line 41: | ||
* '''TextLcd''' - a text LCD, such as 2x8 characters (in development) |
* '''TextLcd''' - a text LCD, such as 2x8 characters (in development) |
||
--> |
|||
== Options == |
== 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: |
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 |
make pc verbose |
||
The following command line options override the configuration file: |
The following command line options override the configuration file: |
||
Latest revision as of 11: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
