If you already have a 1.x tree or an existing 2.x tree, you are better off following the upgrade instructions at @@ -228,10 +228,13 @@ also installed using rpms. 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 +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 --ignoreos option. diff --git a/doc/html/tep125.html b/doc/html/tep125.html index 738d23d0..d606bb6b 100644 --- a/doc/html/tep125.html +++ b/doc/html/tep125.html @@ -370,6 +370,7 @@ for "Interoperable Frame."

4. Implementation

diff --git a/doc/html/tutorial/lesson1.html b/doc/html/tutorial/lesson1.html index b4df6952..0f861638 100644 --- a/doc/html/tutorial/lesson1.html +++ b/doc/html/tutorial/lesson1.html @@ -8,7 +8,7 @@

Lesson 1: Getting Started with TinyOS and nesC

Last updated June 24 2006

Last updated April 8 2007

Introduction

@@ -107,6 +107,8 @@ msp430-objcopy --output-target=ihex build/telosb/main.exe build/telosb/main.ihex as building TOSSIM requires several steps, such as building shared libraries and scripting support.

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 install instructions or step 2 of the upgrade instructions)

Making sure you're invoking the right version of the nesC compiler

If you see an error message along the lines of this:

diff --git a/doc/html/upgrade-tinyos.html b/doc/html/upgrade-tinyos.html index bc799923..dd44d1de 100644 --- a/doc/html/upgrade-tinyos.html +++ b/doc/html/upgrade-tinyos.html @@ -8,7 +8,7 @@

Upgrading from TinyOS 1.x to TinyOS 2.x

Last updated 5 November 2006

Last updated 8 April 2007

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 @@ -157,11 +157,13 @@ only installing a 2.x tree, you can use rpm -Uvh. 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).

diff --git a/doc/txt/tep125.txt b/doc/txt/tep125.txt index dc7cc0af..8fcb50a9 100644 --- a/doc/txt/tep125.txt +++ b/doc/txt/tep125.txt @@ -36,13 +36,13 @@ The TinyOS 2.0 active message layer adds a packet field for higher-level 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. @@ -81,6 +81,7 @@ 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. +The AM type 6lowpan is reserved. A TinyOS program MUST NOT use it. 4. Implementation ====================================================================