From: razvanm Date: Fri, 25 May 2007 17:34:54 +0000 (+0000) Subject: Small update to document the DELUGE_BASESTATION flag. The TOSH_DATA_LENGTH limitation... X-Git-Tag: release_tools_1_2_4_1~164 X-Git-Url: https://oss.titaniummirror.com/gitweb/?a=commitdiff_plain;h=ecdf6f9c47c9684650f5775bc5d695727b1c9751;p=tinyos-2.x.git Small update to document the DELUGE_BASESTATION flag. The TOSH_DATA_LENGTH limitation was also removed. --- diff --git a/doc/html/deluge-t2-manual.html b/doc/html/deluge-t2-manual.html index a807c8bf..94b0de52 100644 --- a/doc/html/deluge-t2-manual.html +++ b/doc/html/deluge-t2-manual.html @@ -22,7 +22,7 @@ Deluge T2 - Programming Manual

Chieh-Jan Mike Liang
-Razvan Musaloiu-E.

May 18, 2007

+Razvan Musaloiu-E.

May 25, 2007

@@ -45,7 +45,7 @@ Having said that, it would be helpful to read the Deluge 2.0 manual and related documentations.

Deluge T2 is still in experimental phase. One current limitation is -platform support. Deluge T2 has been developed and tested on tmote sky +platform support. Deluge T2 has been developed and tested on Tmote Sky (telosb) only. In addition, Deluge T2 comes with 2 flash volumes by default. However, more volumes can be added, if necessary. There are also minor details that will be improved in future releases.

@@ -60,21 +60,25 @@ addition, it provides a quick test for software prerequisite. The latest TinyOS 2 CVS tree and Python 2.4 with pySerial support are recommended for running Deluge T2.

-To start the example, we run a burn script provided in -tinyos-2.x/apps/tests/deluge/Blink. For example, +To start the example, we first compile TOSBoot provided in tinyos-2.x/tos/lib/TOSBoot. +For example, +

+
   % make telosb
+

+Then, we run the burn script provided in tinyos-2.x/apps/tests/deluge/Blink. +For example, 

   % ./burn /dev/ttyUSB0

This burn script programs the directly-connected mote with one -version of blink. Then, it injects and reprograms the mote with another -version of blink. At this point, you can try to retrieve program image +version of Blink. Then, it injects and reprograms the mote with another +version of Blink. At this point, you can try to retrieve program image versioning information. The script to interface with the mote is -provided in tinyos-2.x/tools/. For example, +provided in tinyos-2.x/tools/tinyos/misc. For example,

-
   % tos-deluge.py /dev/ttyUSB0 -p 0
+
   % tos-deluge /dev/ttyUSB0 -p 0
 

-You should see something similar to the output below.

-

+You should see something similar to the output below.
 

 
   Pinging node ...
    Connected to Deluge node.
@@ -94,7 +98,7 @@ You should see something similar to the output below.

    --------------------------------------------------
 

 

-The usage of delugy.py is available by running the script without 
+The usage of tos-deluge is available by running the script without 
 any arguments, and it will be discussed in section 4.

 

 

@@ -115,22 +119,27 @@ provided in tinyos-2.x/apps/tests/deluge/GoldenImage
 nothing except initializing Deluge T2. This step can be done by 
 compiling and programming the mote normally. For example,
 

-
   % make telosb install,0 bsl,/dev/ttyUSB0
+
   % CFLAGS=-DDELUGE_BASESTATION make telosb install,0 bsl,/dev/ttyUSB0
 

+CFLAGS=-DDELUGE_BASESTATION indicates that the current mote will 
+act as a base station, which requires an additional component to accept 
+user commands from the serial port. Normally, only one mote in the 
+network needs to be the base station, and other motes are reprogrammed 
+over-the-air. If error occurs when running the command above, you might 
+need to compile TOSBoot as shown in section 2. 
 Deluge T2 makes sure the mote ID remain persistent over image 
 reprogramming. You can test the installation by interacting with the 
-mote through deluge.py.

+mote through tos-deluge.

 

 

 
 
3.2  Preparing Your Application

 
In most cases, the only two files you need to modify are the top-level
-wiring file and the Make file. You need to make sure DelugeC
-component is included. In addition, the Make file should have the
-following lines:
+wiring file and the Makefile. You need to make sure DelugeC
+component is included. In addition, the Makefile should have the
+following line:
 

 
   TINYOS_NP=BNP
-   CFLAGS += -DTOSH_DATA_LENGTH=100
 

 Finally, compile your application without installing it on the mote. For 
 example,
@@ -144,7 +153,7 @@ example,
 
Before a program image is disseminated in the network, we need to first 
 inject it to the base station. For example,
 

-
   % tos-deluge.py /dev/ttyUSB0 -i 1 apps/Blink/build/telosb/tos_image.xml
+
   % tos-deluge /dev/ttyUSB0 -i 1 apps/Blink/build/telosb/tos_image.xml
 

 You should see something similar to the output below.

 

@@ -181,7 +190,7 @@ You should see something similar to the output below.

 first test on the base station by issuing the reboot command. For 
 example,
 

-
   % tos-deluge.py /dev/ttyUSB0 -r 1
+
   % tos-deluge /dev/ttyUSB0 -r 1
 

 After a few moments, the mote will begin quickly flashing the LEDs to 
 signify the reprogramming process.

@@ -189,7 +198,7 @@ signify the reprogramming process.

 Now, you can have the base station disseminate a program image to the rest of 
 the network. For example,
 

-
   % tos-deluge.py /dev/ttyUSB0 -d 1
+
   % tos-deluge /dev/ttyUSB0 -d 1
 

 This command instructs the base station to notify the whole network of 
 the availablility of a new program image. This notification is currently 
@@ -249,7 +258,7 @@ directly connected mote.

 

 

 

-Last modified: Friday, May 18th, 2007

+Last modified: Friday, May 25th, 2007

 HTML conversion by TeX2page 2004-09-11
 

 
diff --git a/doc/pdf/deluge-t2-manual.pdf b/doc/pdf/deluge-t2-manual.pdf
index d3262951..e50622d9 100644
Binary files a/doc/pdf/deluge-t2-manual.pdf and b/doc/pdf/deluge-t2-manual.pdf differ