Homework #4 Wireless Sensor Network

Exercise 1. Wireless Sensor Network Development Environment

A Toshiba Satellite P25-S507 was setup in EAS 172 with TinyOS 1.1.0.
The MIB500 board can be checked out from Ganesh or Yu Cai for your experiment.
Connect the parallel cable from the PC to the MIB500. Plug in the power connector to the MIB500. When the power is plugged in, the green LED D6 will be lighted up.
Connect the expansion connector mica2 to that of MIB 500.
- The battery side of the mica2 will face up.
- The little power switch of mica2 will be on the same side of the power plug of MIB500.
- See short video.
The following picture shows the picture of a mica2 connected to a MIB500.

System and Hardware Verification.

Debugging is difficult in embedded system, we would like to make sure the tool and hardware are functioning correctly. See http://cs.uccs.edu/~cs526/mote/tinyos/tutorial/verifyhw.html for more detail.
First Click cygwin icon to open the cygwin window.
Verify tinyos related software tools.
- Type "toscheck" command
- Last line should say "toscheck completed without error."
Set Makelocal that specify the group ID (0x33) used by the sensor and the sensor frequency (433.002MHz).
- cd /opt/tinyos-1.x/apps
- Create a Makelocal file with the following content:
  # Makelocal file
  DEFAULT_LOCAL_GROUP=0x33
  PFLAGS += -DCC1K_DEF_FREQ=433002000
Verify mica2 hardware using MicaHWVerify application
- cd /opt/tinyos-1.x/apps/MicaHWVerify
- make mica2
- The following result shows successful compilation.
  $ make mica2
  compiling MicaHWVerify to a mica2 binary
  ncc -o build/mica2/main.exe -Os -board=micasb -target=mica2 -DCC1K_DEF_FREQ=4330
  02000 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x33 -Wnesc-all -finline-limit=100000 -f
  nesc-cfile=build/mica2/app.c MicaHWVerify.nc -lm
  compiled MicaHWVerify to build/mica2/main.exe
  10850 bytes in ROM
  390 bytes in RAM
  avr-objcopy --output-target=srec build/mica2/main.exe build/mica2/main.srec
- Plug in the mica2 node as shown above.
- make reinstall mica2
- The following shows the upload of code to mica2 device.
- $ make reinstall mica2
  installing mica2 binary
  uisp -dprog=dapa -dpart=ATmega128 --wr_fuse_e=ff --erase
  pulse
  Atmel AVR ATmega128 is found.
  Erasing device ...
  pulse
  Reinitializing device
  Atmel AVR ATmega128 is found.
  Fuse Extended Byte set to 0xff
  sleep 1
  uisp -dprog=dapa -dpart=ATmega128 --wr_fuse_e=ff --upload if=build/mica2/main.s
  rec
  pulse
  Atmel AVR ATmega128 is found.
  Uploading: flash
  
  Fuse Extended Byte set to 0xff
  sleep 1
  uisp -dprog=dapa -dpart=ATmega128 --wr_fuse_e=ff --verify if=build/mica2/main.s
  rec
  pulse
  Atmel AVR ATmega128 is found.
  Verifying: flash
  flash error at address 0x1752: file=0x07, mem=0x04
  flash error at address 0x17d2: file=0x44, mem=0xff
  flash error at address 0x17d3: file=0x32, mem=0xff
  
  Fuse Extended Byte set to 0xff
- Note that the above indicate there is flash error.
- Try to upload the code again.
- $ make reinstall mica2
  installing mica2 binary
  uisp -dprog=dapa -dpart=ATmega128 --wr_fuse_e=ff --erase
  pulse
  Atmel AVR ATmega128 is found.
  Erasing device ...
  pulse
  Reinitializing device
  Atmel AVR ATmega128 is found.
  Fuse Extended Byte set to 0xff
  sleep 1
  uisp -dprog=dapa -dpart=ATmega128 --wr_fuse_e=ff --upload if=build/mica2/main.s
  rec
  pulse
  Atmel AVR ATmega128 is found.
  Uploading: flash
  
  Fuse Extended Byte set to 0xff
  sleep 1
  uisp -dprog=dapa -dpart=ATmega128 --wr_fuse_e=ff --verify if=build/mica2/main.s
  rec
  pulse
  Atmel AVR ATmega128 is found.
  Verifying: flash
  
  Fuse Extended Byte set to 0xff
- This time there is no flash error and the upload is successful.
- After the upload, you will see the three LED on the MIB500 flashes with certain pattern. It supposed to be a binary counting pattern, from 0 to 7, with red LED with weight of 2^0, Green LED with weight of 2^1, and Yellow LED with weight of 2^2. Unfortunately the order of LEDs is Green, Yellow, and Red on MIB500, unlike the LEDs on the mica2 which is Yellow, Green, and Red. When attached to the MIB500, you need to tilt the MIB500 to see the LEDs of mica2 which is on the other side of the battery.
- To verify the Mica2 is actually installed with the blinking binary counting program. We detach the Mica2 from MIB500 by holding the mica2 and slow wiggle it out from the expansion connector.
- Turn on the little power switch on the oppositie side of the antenna. The on/off label is on the circuit board at either side of theh switch.
- You should see the binary counting pattern on the LEDs (D2-D3-D4). That is an indication that the blinking program was successfully uploaded and executed by the mica2.
- Turn off the power to save the battery.
Verify mica2dot hardware
- Attach mica2dot on MIB500. It will connect to 19 pins, which form a circle, on the bottom side of MIB500. Make sure you line up them right. You do not have to push them all the way in. So long as the pins are firmly connected, you are ok.
- make mica2dot
- $ make mica2dot
  mkdir -p build/mica2dot
  compiling MicaHWVerify to a mica2dot binary
  ncc -o build/mica2dot/main.exe -Os -board=basicsb -target=mica2dot -DCC1K_DEF_FR
  EQ=433002000 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x33 -Wnesc-all -finline-limit=10
  0000 -fnesc-cfile=build/mica2dot/app.c MicaHWVerify.nc -lm
  C:/tinyos/cygwin/opt/tinyos-1.x/tos/platform/mica2dot/SerialId.nc:47:2: warning:
  #warning "SERIALID NOT SUPPORTED ON MICA2DOT PLATFORM!"
  compiled MicaHWVerify to build/mica2dot/main.exe
  11650 bytes in ROM
  390 bytes in RAM
  avr-objcopy --output-target=srec build/mica2dot/main.exe build/mica2dot/main.srec

$ make reinstall mica2dot
installing mica2dot binary
uisp -dprog=dapa -dpart=ATmega128 --wr_fuse_e=ff --erase
pulse
Atmel AVR ATmega128 is found.
Erasing device ...
pulse
Reinitializing device
Atmel AVR ATmega128 is found.
Fuse Extended Byte set to 0xff
sleep 1
uisp -dprog=dapa -dpart=ATmega128 --wr_fuse_e=ff --upload if=build/mica2dot/mai
n.srec
pulse
Atmel AVR ATmega128 is found.
Uploading: flash

Fuse Extended Byte set to 0xff
sleep 1
uisp -dprog=dapa -dpart=ATmega128 --wr_fuse_e=ff --verify if=build/mica2dot/mai
n.srec
pulse
Atmel AVR ATmega128 is found.
Verifying: flash

Fuse Extended Byte set to 0xff

Edward Chow@scold /opt/tinyos-1.x/apps/MicaHWVerify

You will see Red LED on the mica2dot blinks.
Detach mica2dot from MIB500.
Insert the Panasonic CR2354 nickle size battery.
Verify if the Red LED blinks after battery is attached.

Lesson 1: Getting Started with TinyOS and nesC.

This covers basic nesC language concepts: Component, Interface, task, hardware event handler.
Two types of components: Modules and Configurations.
.nc file extension for all source files.
It uses Blink application as an example.
BlinkM.nc is the module.
Blink.nc is the configuration file.
graphical representation of the component relationships is availble at
C:\tinyos\cygwin\opt\tinyos-1.x\doc\nesdoc\mica\index.html C:\tinyos\cygwin\opt\tinyos-1.x\doc\nesdoc\mica\apps.Blink.Blink.nc.html
Exercises:
1. Modify Blink to display red, green, yellow in sequence every second.
2. Create an application BlinkDot for mica2dot with the blink patterns starting at once per second, twice per second, ..., to 7 per seconds and then repeat.
  Note that Mica2dot only has one LED.