[Tinyos-2-commits] CVS: tinyos-2.x/doc/html deluge-t2-manual.html,
1.2, 1.3
Razvan Musaloiu-E.
razvanm at users.sourceforge.net
Fri Jun 1 17:09:18 PDT 2007
Update of /cvsroot/tinyos/tinyos-2.x/doc/html
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv19802/doc/html
Modified Files:
deluge-t2-manual.html
Log Message:
Add support for MicaZ to Deluge T2.
Index: deluge-t2-manual.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/deluge-t2-manual.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** deluge-t2-manual.html 25 May 2007 17:34:54 -0000 1.2
--- deluge-t2-manual.html 2 Jun 2007 00:09:16 -0000 1.3
***************
*** 23,27 ****
<div align=center>
Chieh-Jan Mike Liang<br>
! Razvan Musaloiu-E.<p>May 25, 2007</p>
</div>
<p></p>
--- 23,27 ----
<div align=center>
Chieh-Jan Mike Liang<br>
! Razvan Musaloiu-E.<p>June 1, 2007</p>
</div>
<p></p>
***************
*** 46,57 ****
<p>
Deluge T2 is still in experimental phase. One current limitation is
! platform support. Deluge T2 has been developed and tested on Tmote Sky
! (<i>telosb</i>) 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.</p>
<p>
</p>
<a name="node_sec_2"></a>
! <h1>2 Quick Start</h1>
<p></p>
<p>
--- 46,80 ----
<p>
Deluge T2 is still in experimental phase. One current limitation is
! platform support. Deluge T2 has been developed on Tmote Sky (<i>telosb</i>)
! and MicaZ only. In addition, Deluge T2 comes with 2 flash volumes by
default. However, more volumes can be added, if necessary. There are
! also some minor details that will be improved in future releases.</p>
<p>
</p>
<a name="node_sec_2"></a>
! <h1>2 Tools Installation</h1>
! <p>Deluge T2 requires a few Python scripts that not yet included in the
! official <code class=verbatim>tinyos-tools</code> RPM package. On the CVS, the scripts are
! located in <code class=verbatim>tinyos-2.x/tools/tinyos/misc</code>. The steps to install
! them are the following:</p>
! <p>
! </p>
! <pre class=verbatim> % cd $TOSROOT
! % ./Bootstrap
! ...
! % ./configure
! ...
! % cd tinyos/misc
! % make ; make install
! ...
! </pre><p></p>
! <p>
! By default, the files will be installed in <code class=verbatim>/usr/local/bin</code>. If
! desired, the <code class=verbatim>--prefix</code> parameter from <code class=verbatim>configure</code> can be
! used to indicate a different path. </p>
! <p>
! </p>
! <a name="node_sec_3"></a>
! <h1>3 Quick Start</h1>
<p></p>
<p>
***************
*** 69,73 ****
For example,
</p>
! <pre class=verbatim> % ./burn /dev/ttyUSB0
</pre><p>
This <code class=verbatim>burn</code> script programs the directly-connected mote with one
--- 92,96 ----
For example,
</p>
! <pre class=verbatim> % ./burn /dev/ttyUSB0 telosb
</pre><p>
This <code class=verbatim>burn</code> script programs the directly-connected mote with one
***************
*** 77,81 ****
provided in <code class=verbatim>tinyos-2.x/tools/tinyos/misc</code>. For example,
</p>
! <pre class=verbatim> % tos-deluge /dev/ttyUSB0 -p 0
</pre><p>
You should see something similar to the output below.
--- 100,104 ----
provided in <code class=verbatim>tinyos-2.x/tools/tinyos/misc</code>. For example,
</p>
! <pre class=verbatim> % tos-deluge /dev/ttyUSB0 telosb -p 0
</pre><p>
You should see something similar to the output below.
***************
*** 100,108 ****
<p>
The usage of <code class=verbatim>tos-deluge</code> is available by running the script without
! any arguments, and it will be discussed in section <a href="#node_sec_4">4</a>.</p>
<p>
</p>
! <a name="node_sec_3"></a>
! <h1>3 Reprogramming a Network</h1>
<p></p>
<p>
--- 123,131 ----
<p>
The usage of <code class=verbatim>tos-deluge</code> is available by running the script without
! any arguments, and it will be discussed in section <a href="#node_sec_5">5</a>.</p>
<p>
</p>
! <a name="node_sec_4"></a>
! <h1>4 Reprogramming a Network</h1>
<p></p>
<p>
***************
*** 112,117 ****
<p>
</p>
! <a name="node_sec_3.1"></a>
! <h2>3.1 Setting Up the Motes</h2>
<p>We first install both TOSBoot and a program that runs Deluge T2. For
simplicity, we use the golden image as the program. The golden image is
--- 135,140 ----
<p>
</p>
! <a name="node_sec_4.1"></a>
! <h2>4.1 Setting Up the Motes</h2>
<p>We first install both TOSBoot and a program that runs Deluge T2. For
simplicity, we use the golden image as the program. The golden image is
***************
*** 127,131 ****
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 <a href="#node_sec_2">2</a>.
Deluge T2 makes sure the mote ID remain persistent over image
reprogramming. You can test the installation by interacting with the
--- 150,154 ----
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 <a href="#node_sec_3">3</a>.
Deluge T2 makes sure the mote ID remain persistent over image
reprogramming. You can test the installation by interacting with the
***************
*** 133,138 ****
<p>
</p>
! <a name="node_sec_3.2"></a>
! <h2>3.2 Preparing Your Application</h2>
<p>In most cases, the only two files you need to modify are the top-level
wiring file and the Makefile. You need to make sure <code class=verbatim>DelugeC</code>
--- 156,161 ----
<p>
</p>
! <a name="node_sec_4.2"></a>
! <h2>4.2 Preparing Your Application</h2>
<p>In most cases, the only two files you need to modify are the top-level
wiring file and the Makefile. You need to make sure <code class=verbatim>DelugeC</code>
***************
*** 149,158 ****
<p>
</p>
! <a name="node_sec_3.3"></a>
! <h2>3.3 Injecting Your Application</h2>
<p>Before a program image is disseminated in the network, we need to first
inject it to the base station. For example,
</p>
! <pre class=verbatim> % tos-deluge /dev/ttyUSB0 -i 1 apps/Blink/build/telosb/tos_image.xml
</pre><p>
You should see something similar to the output below.</p>
--- 172,181 ----
<p>
</p>
! <a name="node_sec_4.3"></a>
! <h2>4.3 Injecting Your Application</h2>
<p>Before a program image is disseminated in the network, we need to first
inject it to the base station. For example,
</p>
! <pre class=verbatim> % tos-deluge /dev/ttyUSB0 telosb -i 1 apps/Blink/build/telosb/tos_image.xml
</pre><p>
You should see something similar to the output below.</p>
***************
*** 185,195 ****
<p>
</p>
! <a name="node_sec_3.4"></a>
! <h2>3.4 Reprogramming with New Image</h2>
<p>After you decide which program image you want to reprogram, you can
first test on the base station by issuing the reboot command. For
example,
</p>
! <pre class=verbatim> % tos-deluge /dev/ttyUSB0 -r 1
</pre><p>
After a few moments, the mote will begin quickly flashing the LEDs to
--- 208,218 ----
<p>
</p>
! <a name="node_sec_4.4"></a>
! <h2>4.4 Reprogramming with New Image</h2>
<p>After you decide which program image you want to reprogram, you can
first test on the base station by issuing the reboot command. For
example,
</p>
! <pre class=verbatim> % tos-deluge /dev/ttyUSB0 telosb -r 1
</pre><p>
After a few moments, the mote will begin quickly flashing the LEDs to
***************
*** 199,203 ****
the network. For example,
</p>
! <pre class=verbatim> % tos-deluge /dev/ttyUSB0 -d 1
</pre><p>
This command instructs the base station to notify the whole network of
--- 222,226 ----
the network. For example,
</p>
! <pre class=verbatim> % tos-deluge /dev/ttyUSB0 telosb -d 1
</pre><p>
This command instructs the base station to notify the whole network of
***************
*** 208,213 ****
<p>
</p>
! <a name="node_sec_4"></a>
! <h1>4 Deluge T2 Python Toolchain</h1>
<p></p>
<p>
--- 231,236 ----
<p>
</p>
! <a name="node_sec_5"></a>
! <h1>5 Deluge T2 Python Toolchain</h1>
<p></p>
<p>
***************
*** 217,222 ****
<p>
</p>
! <a name="node_sec_4.1"></a>
! <h2>4.1 -p -ping</h2>
<p>This command is useful for checking the status of program images on a
mote. It provides information such as program name, compile time, size
--- 240,245 ----
<p>
</p>
! <a name="node_sec_5.1"></a>
! <h2>5.1 -p -ping</h2>
<p>This command is useful for checking the status of program images on a
mote. It provides information such as program name, compile time, size
***************
*** 224,229 ****
<p>
</p>
! <a name="node_sec_4.2"></a>
! <h2>4.2 -i -inject</h2>
<p>This command creates a program image from the supplied
<code class=verbatim>tos_image.xml</code> file, and it injects the image into specified
--- 247,252 ----
<p>
</p>
! <a name="node_sec_5.2"></a>
! <h2>5.2 -i -inject</h2>
<p>This command creates a program image from the supplied
<code class=verbatim>tos_image.xml</code> file, and it injects the image into specified
***************
*** 232,237 ****
<p>
</p>
! <a name="node_sec_4.3"></a>
! <h2>4.3 -r -reboot</h2>
<p>This command sets up the mote to reprogram itself after reboot, and then
it reboots the mote. This command is applicable only to the directly
--- 255,260 ----
<p>
</p>
! <a name="node_sec_5.3"></a>
! <h2>5.3 -r -reboot</h2>
<p>This command sets up the mote to reprogram itself after reboot, and then
it reboots the mote. This command is applicable only to the directly
***************
*** 239,244 ****
<p>
</p>
! <a name="node_sec_4.4"></a>
! <h2>4.4 -d -dissemination</h2>
<p>This command instructs the directly connected mote to disseminate an
image to the network. This image is specified by the volume ID. Upon
--- 262,267 ----
<p>
</p>
! <a name="node_sec_5.4"></a>
! <h2>5.4 -d -dissemination</h2>
<p>This command instructs the directly connected mote to disseminate an
image to the network. This image is specified by the volume ID. Upon
***************
*** 247,257 ****
<p>
</p>
! <a name="node_sec_4.5"></a>
! <h2>4.5 -e -erase</h2>
<p>This command erases a flash volume on the directly connected mote.</p>
<p>
</p>
! <a name="node_sec_4.6"></a>
! <h2>4.6 -s -reset</h2>
<p>This command resets versioning information of a specific image on the
directly connected mote.</p>
--- 270,280 ----
<p>
</p>
! <a name="node_sec_5.5"></a>
! <h2>5.5 -e -erase</h2>
<p>This command erases a flash volume on the directly connected mote.</p>
<p>
</p>
! <a name="node_sec_5.6"></a>
! <h2>5.6 -s -reset</h2>
<p>This command resets versioning information of a specific image on the
directly connected mote.</p>
***************
*** 259,263 ****
</p>
<div align=right class=colophon>
! <i>Last modified: Friday, May 25th, 2007<br>
HTML conversion by <a href="http://www.ccs.neu.edu/~dorai/tex2page/tex2page-doc.html">TeX2page 2004-09-11</a></i>
</div>
--- 282,286 ----
</p>
<div align=right class=colophon>
! <i>Last modified: Friday, June 1st, 2007<br>
HTML conversion by <a href="http://www.ccs.neu.edu/~dorai/tex2page/tex2page-doc.html">TeX2page 2004-09-11</a></i>
</div>
More information about the Tinyos-2-commits
mailing list