DiLab - User contributions [en]

MansOS Makefiles

2008-04-02T06:42:40Z

Samofals: /* Creating the application Makefile */

'''MansOS''' has a makefile system to speed up the development of
your applications and the development of MansOS itself

== For application developers ==
==== Running the make ====

The common targets of the makefile are as follows:
* '''build''' - (optional, default) build the module or application
* '''upload''' - upload the application via hard wire (USB or COM). Make will upload to the first attached mote it finds.
* '''''<target>''''' - targed platform, such as '''telosb'''
* '''clean''' - clear the generated object and other files.
* '''cleanall''' - clear everything from the output (build/) directory

* '''objs''' - compile only, generate all object files
* '''printenv''' - print the major variables (for debugging make)

For example, if you want to build your system and then upload it to the telos mote:
make telosb
make telosb upload

==== Creating the application Makefile ====

You need just one Makefile in your project directory.
Examples can be found in the apps directory.
This makefile must define the following variables:

* '''SOURCES''' - a space-delimited list of source (.c) files. It is assumed that the include files reside in the same directory
* '''MODULE''' - the module name being developed. This could be the application name.
* '''PROJDIR''' - most likely the current directory $(CURDIR) containing the application files.

For example:
# My makefile
SOURCES = main.c
MODULE = MySystem
PROJDIR = $(CURDIR)

Optional:
* '''INCLUDES''' - space-delimited list of include file directories. The project directory itself is included by default.

The makefile must end with the definition of path to MansOS system MOSROOT and include of the main MansOS Makefile, like this:

ifndef MOSROOT
MOSROOT = /home/elo/c/elo/WSN/projects/MansOS/svn
endif

# Include the main makefile
include ${MOSROOT}/mos/make/Makefile

Another way to setup MOSROOT, is to write in bash before executing make:
export MOSROOT=/home/raimonds/MansOS_Work

== For MansOS developers ==

Add path(s) to the source files in the platform makefile.

== Makefile basics ==

For a general info on how to work with makefiles look here:

* [http://www.cs.cmu.edu/cgi-bin/info2www?(make.info)Top (make.info) at CMU]

Here is an example of a makefile system for Java development:

* [http://geosoft.no/development/javamake.html Javamake at Geosoft]

MansOS FAQ

2008-03-27T20:05:29Z

Samofals: New page: '''Q: Ubuntu vidē mote pēc laika atslēdzas no /dev/ttyUSB0 , un palaižot motelist mēs redzam, ka CommPort ir none''' $ motelist Reference CommPort Description ---------...

'''Q: Ubuntu vidē mote pēc laika atslēdzas no /dev/ttyUSB0 , un palaižot motelist mēs redzam, ka CommPort ir none'''
$ motelist
Reference CommPort Description
---------- ---------- ----------------------------------------
UCC89MXV (none) Telos (Rev B 2004-09-27)

'''A: Jānoņem(jāatinstalē) brltty '''
sudo apt-get remove brltty

Informācija ņemta no šejienes: http://mail.millennium.berkeley.edu/pipermail/tinyos-devel/2007-June/001669.html

Thought that folks might find this useful.

Some may have noticed that Ubuntu Feisty Fawn has problems talking to
TMote Sky nodes. The problem is that the Braille TTY driver wants to
claim any device with the FTDI USB chipset. The fix is to run:

sudo apt-get remove brltty

Which clears this out and removes the dependencies.

Matt

MansOS

2008-03-27T19:59:19Z

Samofals: /* Development tools and techniques */

MansOS is an operating system for wireless sensor networks. It can be considered a branch of LiteOS operating system because it shares several defining characteristics. MansOS like LiteOS is designed to be easily adopted by system designers by avoiding the steep learning curve, because it is based on the concepts that are familiar to the majority of IT community.

Key concepts common with LiteOS:
* MansOS is adopting programming in C and (eventually) C++, known to many people
* MansOS is treating a sensor network using Unix-like command tools and resources
* MansOS enables thread-like programming environment

Additional key aspects specific to MansOS:
* MansOS is designed to be easily portable to new platforms
* MansOS enforces the structured HPL-HAL-HIL architecture at a mote level, ensuring clear interface for portability
* The focus during the development should be the whole system - a collection of mote entities rather than a single mote

=== General ===

* [[MansOS_Philosophy | Philosophy]]
* [[MansOS_Architecture | Architecture]]
* [[MansOS_Directory_Structure | Directory structure]]

=== Internals ===

* [[MansOS_Kernel | Kernel]]
* [[MansOS_File_System | File system]]

=== Development tools and techniques ===

* [[MansOS_Apps_examples | Application examples]]
* [[MansOS_Eclipse | Eclipse setup]]
* [[MansOS_Testing | Debugging and testing]]
* [[MansOS_FAQ | FAQ]]

=== Hardware notes ===

Chips
* [[Chips_msp430 | MCU: MSP430]]
* [[Chips_cc2420 | Radio: CC2420]]

Platforms
* [[Platforms_telosb | telosb: Tmote Sky, Mini, etc.]]