point not found" issue with nesc1.
Update TEP125 to include reservation of AM type.
<body>
<div class="title">Installing TinyOS 2.0</div>
-<div class="subtitle">Last updated 5 November 2006</div>
+<div class="subtitle">Last updated 8 April 2007</div>
<p>If you already have a 1.x tree or an existing 2.x tree, you are better off
following the <i>upgrade</i> instructions at
in these install
instructions, you should install the "Recommended" Windows/Cygwin
nesC RPM.
-Try installing it and if it does not work (e.g., you
-get strange errors when you try to execute it), this may be due
+If you
+get strange errors when you try to compile TinyOS programs,
+such as the error message "the procedure entry point basename could not be located
+in the dynamic link library cygwin1.dll", this is likely due
to a Cygwin version incompatibility: try the "Other" Windows/Cygwin
-RPM (1.2.7a). If you are using Cygwin and installing the nesC RPM
+RPM (1.2.7a).
+If you are using Cygwin and installing the nesC RPM
causes an error that the RPM was built for Cygwin,
add the <code>--ignoreos</code> option.
to identify this as a TinyOS packet. At this time, the exact value of
this code has not been determined. To inform 6lowpan that this is not
a 6lowpan packet, the code used MUST be in the range of 192-55.</p>
+<p>The AM type 6lowpan is reserved. A TinyOS program MUST NOT use it.</p>
</div>
<div class="section">
<h1><a id="implementation" name="implementation">4. Implementation</a></h1>
<body>
<div class="title">Lesson 1: Getting Started with TinyOS and nesC</div>
-<div class="subtitle">Last updated June 24 2006</div>
+<div class="subtitle">Last updated April 8 2007</div>
<h1>Introduction</h1>
as building TOSSIM requires several steps, such as building shared
libraries and scripting support.</p>
+ <p>If you are running Cygwin and see the error message "The procedure entry point basename could not be located in the dynamic link library cygwin1.dll" then you need to install the other Cygwin nesC RPM (step 4 of the <A HREF="../install-tinyos.html">install instructions</A> or step 2 of the <A HREF="../upgrade-tinyos.html">upgrade instructions</A>)</p>
+
<h2>Making sure you're invoking the right version of the nesC compiler</h2>
<p>If you see an error message along the lines of this:</p>
<body>
<div class="title">Upgrading from TinyOS 1.x to TinyOS 2.x</div>
- <div class="subtitle">Last updated 5 November 2006</div>
+ <div class="subtitle">Last updated 8 April 2007</div>
<p>
This document describes how to upgrade your TinyOS 1.x environment to
a TinyOS 2.x environment. This requires that you not only install the
If you using the Cygwin version recommended
in these install
instructions, you should install the "Recommended" Windows/Cygwin
-nesC RPM.
-Try installing it and if it does not work (e.g., you
-get strange errors when you try to execute it), this may be due
+nesC RPM.
+If you
+get strange errors when you try to compile TinyOS programs,
+such as the error message "the procedure entry point basename could not be located
+in the dynamic link library cygwin1.dll", this is likely due
to a Cygwin version incompatibility: try the "Other" Windows/Cygwin
-RPM (1.2.7a).
+RPM (1.2.7a).
<p>
protocol dispatch. This document describes the two TinyOS 2.0 frame format
for 802.15.4 networks. The first format is for isolated TinyOS networks;
the second format is for networks that share the spectrum with 6lowpan
-networks[1_].
+networks[1]_.
2. 802.15.4
====================================================================
802.15.4 supports several different source and destination addressing
-modes, and so has a variable sized packet header.[2_] A TinyOS device MUST
+modes, and so has a variable sized packet header.[2]_ A TinyOS device MUST
support packet frames with 16-bit short source and destination addresses.
A TinyOS device MAY support additional 802.15.4 frame formats.
this code has not been determined. To inform 6lowpan that this is not
a 6lowpan packet, the code used MUST be in the range of 192-55.
+The AM type 6lowpan is reserved. A TinyOS program MUST NOT use it.
4. Implementation
====================================================================