Hi!

On Thu, 16 Oct 2008, Doug Palmer wrote:

> I've been trying to follow the instructions at
> http://www.tinyos.net/tinyos-2.x/doc/html/deluge-t2-manual.html to get
> Deluge T2 running.
>
> I have a CVS version of tinyos-2.x checked out on 16/10/08 and I'm using
> telosb (TMote Sky) motes.
>
> I can do steps 1-3 and 4.1. I'm programming two motes, both with
> -DDELUGE_BASESTATION, one with id 0 and one with id 1.

Only one mote needs to be compiled with -DDELUGE_BASESTATION. An important 
property of a DELUGE_BASESTATION mote will not obey the reprogramming 
commands received over the air.

> However, I'm running into trouble with dissemination across a network.
>
> There appear to be a few missing steps in section 4.2, from what I can
> gather, I need to
>
> 1. Wire DelugeC into the program

This is indicated in section 4.2:
        You need to make sure DelugeC component is included.

> 2. Include BOOTLOADER=tosboot in the Makefile, rather than TINYOS_NP=BNP

This is indicated also in section 4.2:
        In addition, the Makefile should have the following line:
          BOOTLOADER=tosboot

> 3. Probably include CFLAGS += -DDELUGE_BASESTATION in the Makefile so
> that I can interrogate the base node after the reboot

No. The -DDELUGE_BASESTATION should only be used for a basestation mote. 
If you want to be able to interrogate the motes over the serial you can use 
-DDELUGE_LIGHT_BASESTATION. I'm editing the wiki to indicate this right 
now.

> I'm using the apps/tests/deluge/Blink application as a base.
>
> I then do
>
> tos-deluge /dev/ttyUSB0 telosb -i 1 build/telosb/tos_image.xml
>
> tos-deluge /dev/ttyUSB0 telosb -p 1
> tos-deluge /dev/ttyUSB0 telosb -r 1
>
> which all seems to go OK.
>
> I then do
>
> tos-deluge /dev/ttyUSB0 telosb -d 1

A basestation has a run a program compiled with -DDELUGE_BASESTATION while 
a non-basestation doesn't. Should we remove the '-r' command in order to 
avoid this confusion?

> and, although I can see the command go into the base station and the
> green . Nothing seems to happen. After a few minutes, plugging the other
> mote into the USB connector and pinging it shows that the image hasn't
> been transmitted.

The second mote is also a DELUGE_BASESTATION and that's why it ignores the 
dissemination command.

All the best!
Razvan ME

> I've also tried using the golden image a la
> http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-June/026183.html
> without any luck.
>
> Any suggestions?
>
> I'm using Suse 11.0
> My environment variables are:
> PATH=/opt/msp430/bin:/opt/cross/bin:/opt/msp430/bin:/home/pal155/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/kde3/bin:/opt/cross/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin:/opt/msp430/bin:/usr/lib/qt3/bin
>
> TOSROOT=/home/pal155/src/tinyos-2.x
> TOSDIR=/home/pal155/src/tinyos-2.x/tos
> MAKERULES=/home/pal155/src/tinyos-2.x/support/make/Makerules
> CLASSPATH=/home/pal155/src/tinyos-2.x/support/sdk/java/tinyos.jar:.
>
>
>
>
>
>
> _______________________________________________
> Tinyos-help mailing list
> [email protected]
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to