Internet of Things and Smart Cities Ph.D.

School 2013 -
University of Parma

Hands on Contiki OS and Cooja

Simulator: Exercises (Part II)

Ing. Pietro Gonizzi ([email protected])

Dr. Simon Duquennoy ([email protected])
17-09-2013

1 Introduction
Welcome to this Contiki programming course! Contiki is a state-of-the-art, open
source operating system for sensor networks and other networked embedded
devices [1].
You will look at various cool Contiki features such as the uIP stack (IPv6, RPL,
6LoWPAN), HTTP/CoAP, power profiling and others. We will use Tmote Sky
boards as our hardware target. We will also use the Cooja network simulator
which emulates Tmote Sky nodes and connects them.
You can use the Instant Contiki development environment in the exercises. In-
stant Contiki is a single-file download that contains the Contiki source code
and all necessary compilers and tools required for developing software for Con-
tiki. The Instant Contiki environment is a Ubuntu Linux installation that runs
within the VMware Player virtual machine execution environment. VMware
Player is available for free at the VMware website. If you have Contiki working
on your native machine without Instant Contiki that is of course also fine.

2 Getting Started
Before starting with the actual exercises, make sure that your development setup
works by conducting the steps below.

1
2.1 Start Instant Contiki
Open the file

instant-contiki.vmx

to start VMware and Instant Contiki.

2.2 Log In
When the login screen appears, log in to Instant Contiki:
ˆ Username: user
ˆ Password: user

2.3 Open a Terminal Window

After logging in, click on the terminal icon to start a terminal window. You
may also need to adjust the language and keyboard settings of your system.

2.4 Verify that your system works

In the terminal window, go to the hello world example directory, and compile
for the native platform (this means Contiki is compiled to linux process rather
than to a ready-to-burn image for sensor nodes):

$ cd contiki
$ cd examples/hello-world
$ make TARGET=native

Wait for the compilation to finish. Run the Hello World program in Contiki:

$ ./hello-world.native

The program should print the words “Hello, world” on the screen and then
appear to hang. In reality, Contiki is still running correctly, but will not produce
any more output because the Hello World program has finished. Press Ctrl+C
on the keyboard to quit.
Note that Contiki uses printf to issue logs and messages. This can also be
used when you have a sensor node that is connected via a serial line, e.g. USB,
to a laptop.

2.5 Run Hello World on a Tmote Sky Node

Now, run the hello-world example on real hardware. In this course, we use the
Tmote Sky, which features a 16-bit msp430 MCU, 10 kB RAM, 48 kB ROM, a
cc2420 802.15.4 radio transceiver, an external Flash memory, and temperature,
humidity and brightness sensor.

2
2.5.1 Compile Contiki for the Tmote Sky
Compile Contiki for the sky platform:

$ make hello-world.upload TARGET=sky

This triggers the cross-compilation of Contiki using msp430-gcc and including

the drivers that are specific to the sky platform. The outcome is the ELF file
hello-world.sky, a ready-to-burn firmware. Playing with objdump, nm, and
size is a good idea to get familiar with what a Contiki firmware look like.
Exercise 1.Use size to find out how much RAM and ROM the firmware needs
to run. Do you have any comments/thoughts about runtime stack usage?

2.5.2 Connect the Tmote Sky

As we are going to use the sky target a few more times, ask Contiki to remember
it by using:

$ make TARGET=sky savetarget

Put a Tmote Sky in a computer’s USB port. The Tmote Sky will appear in
the top of the Instant Contiki (VMware Player) window with the name “Future
Device” in the menu “Player/Removable Devices”. Click on the name to connect
the Tmote Sky to Instant Contiki (note this will disconnect the device from the
host OS). Run the following to find all connected sky nodes and their associated
tty file:

$ make sky-motelist

2.5.3 Upload the Firmware

Upload the firmware to your node (the argument MOTE is optional; when un-
specified, all nodes are reprogrammed):

$ make hello-world.upload MOTE=1

During the uploading the Tmote Sky should quickly flash the red LEDs next to
the USB connector.
Once the upload is terminated, connect to the USB port to view the program
output:

$ make login MOTE=1

Press the reset button on the Tmote Sky (the one further away from the USB
connector) and you should get some Contiki startup log messages followed by
Hello, world.

3
Exercise 2.Install the test-button program from the examples/sky directory.
Connect to the USB port (make login) and press the non-reset button (the one
closest to the USB connector).

2.6 Run Hello World in Cooja

Cooja is a network simulator that is able to emulate Tmote Sky (and other)
nodes. The code executed by the node is the exact same firmware you may
upload to physical nodes.
Start Cooja by using the desktop icon or running ant run from the directory
tools/Cooja. Now that Cooja is up and running, you can try it out with an
example simulation. Click the File menu and click New simulation. Cooja now
opens up the Create new simulation dialog. In this dialog, you may choose to
give your simulation a new name, e.g., Hello-world.
After clicking the Create button, Cooja brings up the new simulation. The
Network window, at the top left of the screen, shows all the motes in the
simulated network - it is empty now, since you have no motes in your simulation.
The Timeline window, at the bottom of the screen, shows all communication
events in the simulation over time - very handy for understanding what goes
on in the network. The Mote output window, on the right side of the screen,
shows all serial port printouts from all the motes. The Notes window on the
top right is where you can put notes for your simulation. And the Simulation
control window is where you start, pause, and reload your simulation.
Before you can simulate your network, you must add one or more motes. You
do this via the Motes menu, where you click on Add motes. Since this is the
first mote you add, you must first create a mote type to add. Click Create new
mote type and select one of the available mote types. In this course, you click
Sky mote to create an emulated Tmote Sky mote type.
Cooja opens the Create Mote Type dialog, in which you can choose a name
for your mote type as well as the Contiki application that your mote type will
run. Give a name to your mote type and click on the Browse button on the
right hand side to choose your Contiki application. Go to the directory /home/
user/contiki/examples/hello-world and select the hello-world.c source
file. Now Cooja will verify that the selected Contiki application compiles for
the platform that we have selected. Click the Compile button. The compilation
output will show up in the white panel at the bottom of the window. If the
compilation is fine, click the Create button. You will be asked to enter the
number of motes of your simulation. Once you are done, click the Start button
in the Simulation control window to start the simulation.

2.6.1 Save, Load and Reload in Cooja

Cooja allows for saving and loading simulation configurations. When a simu-
lation is saved, all active plugins are also stored with the configuration. The

4
 Figure 2.1: The Cooja simulator

state of a current simulation is however not saved; all nodes are reset when the
simulation is loaded again. To save your current simulation:

ˆ Click menu item: File, Save simulation.

Simulations are stored with the file extensions “.csc”. To later load a simulation:

ˆ Click menu item: File, Open simulation, Browse.... Select a simula-

tion configuration.

When a simulation is loaded, all simulated Contiki applications are recompiled.

A functionality similar to saving and loading simulations, is reloading a simula-
tion. Reloading can be used to reset the simulation – to restart all nodes. More
importantly, reloading a simulation will recompile all Contiki code, useful while
developing Contiki programs. To reload your current simulation:
ˆ Click menu item: File, Reload simulation, or press Ctrl+R

2.6.2 Radio model in Cooja

Once you have added nodes, you may want to check if they can communicate
with each other. From the Network window, left-click on the View textbox

5
and tick Radio Environment (UDGM) in the text window that pops up. If
you now left-click on one of the nodes, you will see a green circle around the
selected node. The green circle presents the transmission range of the node,
i.e. the selected node can communicate with all other nodes within that circle.
You may also see a grey circle around the green circle. This circle represents
the interference range. That is when the selected nodes transmits packets,
a node in the grey area cannot receive packets correctly but it is interferred
which means that it is not able to receive packets from other nodes when the
selected node communicates simultaneously. The areas that are not covered by
the green or grey circle are white; communication in that areas is not affected
at all by transmission from the selected nodes.

3 Single-Node Exercises
You will now extend the hello-world example to add more complex stuff. Create
a folder in an easy-to-access location. This folder will contain all the projects of
this course. Copy+paste the contiki/examples/hello-world folder in your
new folder. Use an editor that works for you (Eclipse is pre-installed).

3.1 Sensors, LEDs and Button

We will extend the Hello World program to let it print sensor data and toggle
the leds when the button is pressed. Use the hello-world.c as a starting point.
For the button, leds and sensors you need to include some files (see also examples/
sky/test-button.c from where you can copy code lines:

#include "dev/button-sensor.h"
#include "dev/light-sensor.h"
#include "dev/leds.h"
#include <stdio.h> /* For printf() */

Contiki uses protothreads [3] to provide thread-like abstractions on top of a

lightweight event-driven kernel. Protothreads are non-preemptive, but provide
pseudo-blocking functions to e.g. wait for events, such as PROCESS WAIT EVENT().
In hello-world.c, the main protothread is called hello_world_process. The
code of this main process is in the function PROCESS_THREAD(hello_world_
process,ev,data), between PROCESS_BEGIN(); and PROCESS_END();.
Sensors needs to be activated in the main process:

SENSORS_ACTIVATE(button_sensor);
SENSORS_ACTIVATE(light_sensor);

To print out the current light sensor value:

printf("Light: \%u\n", light_sensor.value(0));

6
To wait for an event and check if this event is a button press:

PROCESS_WAIT_EVENT();
if(ev == sensors_event && data == &button_sensor) {
..
}

Or, more directly:

PROCESS_WAIT_EVENT_UNTIL(ev == sensors_even
&& data == &button_sensor);

To toggle LEDs:

leds_toggle(LEDS_ALL);

Exercise 3.Write a program that loops indefinitely, checks if a button has been
pressed, and if so, toggles LEDs and prints out (printf) a message. Test it on
your mote.

3.2 Local Variables

We now extend the Hello World program by adding a counter that counts the
number of button press events since bootup.
Exercise 4.Add a local counter variable, increment it every time the button is
pressed, and print out the current counter in addition to the light sensor data.
Test it on your mote.

Do you get the expected result? If not, then you have experienced one pecu-
liarity of protothreads: local variables are not stored across a blocking wait. A
workaround consists in declaring your variable as static. Doing so, the variable
is stored in the data segment rather than the runtime stack.
Exercise 5.Fix your counter program accordingly, and test it on your mote.