Difference between revisions of "The simplest TinyOS program"

From TinyOS Wiki
Jump to: navigation, search
Line 13: Line 13:
  
 
which produces the executable file <tt>a.out</tt>, which of course does nothing!
 
which produces the executable file <tt>a.out</tt>, which of course does nothing!
 +
 +
In TinyOS, to get the same thing, you need to create three files. Suppose the program we create is called <tt>Simple</tt>.
 +
 +
0. Create a new directory to put the files. We can name this directory ''Simple'':
 +
 +
<code bash>
 +
$ mkdir Simple
 +
$ cd Simple
 +
</code>
 +
 +
1. You need to create a ''Configuration'' file SimpleAppC.nc (following the suggested naming convention).
 +
<code>
 +
configuration SimpleAppC{
 +
}
 +
implementation{
 +
components SimpleC, MainC;
 +
 +
SimpleC.Boot -> MainC.Boot;
 +
}
 +
</code>
 +
There are two components in this program: your component called SimpleC and the ''Main'' component <tt>MainC</tt>. The MainC component provides the Boot.booted signal which essentially is the entry point of the application.
 +
 +
2. You need to create the ''Component'' file SimpleC.nc. This has definition (implementation) of the component SimpleC.
 +
 +
<code>
 +
module SimpleC{
 +
uses interface Boot;
 +
}
 +
 +
implementation{
 +
event void Boot.booted()
 +
{
 +
}
 +
}
 +
</code>
 +
 +
3. Now you need to create a ''Makefile'' so that the compiler can compile it. Create the file called <tt>Makefile</tt> with the following two lines:
 +
 +
<code>
 +
COMPONENT=SimpleAppC
 +
include $(MAKERULES)
 +
</code>
 +
 +
I.e., you put the name of the top level configuration in the ''COMPONENT'' field.
 +
 +
 +
Now you are ready to compile:
 +
 +
<code bash>
 +
$ make micaz
 +
</code>
 +
 +
which should work successfully provided you have set up the environment properly.

Revision as of 22:13, 9 September 2008

There is some value in knowing the the simplest code that can be compiled without errors. The C equivalent is

int main () {

  return 0;

}


which is written in a file, say, simple.c and compiled with the command

$ gcc test.c

which produces the executable file a.out, which of course does nothing!

In TinyOS, to get the same thing, you need to create three files. Suppose the program we create is called Simple.

0. Create a new directory to put the files. We can name this directory Simple:

$ mkdir Simple $ cd Simple

1. You need to create a Configuration file SimpleAppC.nc (following the suggested naming convention). configuration SimpleAppC{ } implementation{ components SimpleC, MainC;

SimpleC.Boot -> MainC.Boot; } There are two components in this program: your component called SimpleC and the Main component MainC. The MainC component provides the Boot.booted signal which essentially is the entry point of the application.

2. You need to create the Component file SimpleC.nc. This has definition (implementation) of the component SimpleC.

module SimpleC{ uses interface Boot; }

implementation{ event void Boot.booted() { } }

3. Now you need to create a Makefile so that the compiler can compile it. Create the file called Makefile with the following two lines:

COMPONENT=SimpleAppC include $(MAKERULES)

I.e., you put the name of the top level configuration in the COMPONENT field.


Now you are ready to compile:

$ make micaz

which should work successfully provided you have set up the environment properly.