Re: [Tinyos-help] TinyOS -XBee Module Commuication

[Eric Decker]

what is FFD and RFD?



On Thu, Aug 29, 2013 at 11:16 PM, Bipin Kunjumon  wrote:

>  I  am  doing  a  project  related  toRadio  Stack
> Interoperability  using component  generalization.  Here  in  my
> project  i  have  to  make  a  communication  between the  TinyOS FFD
> and  XBee Module RFD,  it  tried  some  ways  that  i  got  from the  net,
> but  that  doesn't  work..  Is  there have anyone  successfully  make the
> communication between these  two ?  if  its  so.. please  help  me  to
> solve  this..
>
>
>
>
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>



-- 
Eric B. Decker
Senior (over 50 :-) Researcher
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] IO configuration

[Eric Decker]

On Thu, Aug 29, 2013 at 11:32 PM, He Dajiang (I2R)
wrote:

> I did and found HplAtm128GeneralIOPinP.nc in folder:
> tinyos-2.1.2\tos\chips\atm128\pins.
> In the file: there are two macro fucntions: SET_BIT and CLR_BIT, which do
> what I am not 100% sure. That's why I asked.
> Sorry, not very familiar with direct MCU control.
>

Here is what I did to answer the question of what does SET_BIT do...

>From the top level of the source tree...

grep -nHiR -e set_bit .

And you'll something like...After a whole bunch of places where SET_BIT
is used...

./tos/chips/m16c60/m16c60hardware.h:59:#define SET_BIT(port, bit)
 ((port) |= _BV(bit))


you can do something similar for _BV

hope that helps you learn to fish  :-)



> 
> From: Eric Decker [cire...@gmail.com]
> Sent: Friday, 30 August, 2013 12:13:47 PM
> To: He Dajiang (I2R)
> Cc: Janos Sallai; tinyos-help@millennium.berkeley.edu
> Subject: Re: [Tinyos-help] IO configuration
>
> On Thu, Aug 29, 2013 at 6:45 PM, He Dajiang (I2R)  > wrote:
> thx, Janos.
>
> I used the following low level calls to make it work:
>
> cli();
> PORTD = PORTD | 0x03;
> sei();
>
> For you suggestion, I guess it is like
>
> SensorP.IO0 -> HplAtm128GeneralIOC.PortE0;   // SCL
> SensorP.IO1 -> HplAtm128GeneralIOC.PortE1;   // SDA
>
> However, I don't quite understand what the following calls do:
> call IO.makeInput();
> call IO.set();// is it high or low
> Call IO.set(1) leads to compiling error.
>
> First I would recommend reading the source code to answer your own
> question.
>
> I don't remember how things work on the MicaZ but the Msp430 does
> something similar.
>
> A given digital I/O pin can be programmed to behave differently.  I.E. you
> can have it be an input or an output or connected to some different i/o h/w
> such as a UART or a SPI.  The call to makeInput sets the h/w up so the pin
> referenced as "IO" is configured as an input.
>
> IO.set is a call that causes the pin to be set to a particular state.
>  Typically ".set" will set the pin to a high state (set).  .clear or .clr
> will set the pin to a low value.
>
> .set does not take a parameter and this is why "call IO.set(1)" gives you
> a compilation error.
>
>
> like I said earlier you really should have taken a look at the source code
> yourself and answered these questions yourself.
>
> when you make a build you can see exactly which files are being processed
> by doing "make verbose "
>
>
> eric
>
>
>
> 
> From: sallai.ja...@gmail.com [
> sallai.ja...@gmail.com] on behalf of Janos
> Sallai [sal...@isis.vanderbilt.edu]
> Sent: Thursday, 29 August, 2013 9:22:24 PM
> To: He Dajiang (I2R)
> Cc: tinyos-help@millennium.berkeley.edu tinyos-help@millennium.berkeley.edu>
> Subject: Re: [Tinyos-help] IO configuration
>
> The best way to go is wiring the PortD interface of GeneralIOC, and
> using the commands of the interface to get/set the levels and
> directions of the pins.
>
> Janos
>
> On Thu, Aug 29, 2013 at 4:23 AM, He Dajiang (I2R)
> mailto:h...@i2r.a-star.edu.sg>> wrote:
> > Hi,
> >
> > For Micaz, what is the proper call to pull up the following two pins:
> >
> > PORTD0 and PORTD1
> >
> > Is it SET_BIT(PORTD, 0x03)?
> >
> > Best Regards
> >
> > Institute for Infocomm Research disclaimer:  "This email is confidential
> and may be privileged. If you are not the intended recipient, please delete
> it and notify us immediately. Please do not copy or use it for any purpose,
> or disclose its contents to any other person. Thank you."
> >
> > ___
> > Tinyos-help mailing list
> > Tinyos-help@millennium.berkeley.edu Tinyos-help@millennium.berkeley.edu>
> > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> >
>
> Institute for Infocomm Research disclaimer:  "This email is confidential
> and may be privileged. If you are not the intended recipient, please delete
> it and notify us immediately. Please do not copy or use it for any purpose,
> or disclose its contents to any other person. Thank you."
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu Tinyos-help@millennium.berkeley.edu>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
>
>
> --
> Eric B. Decker
> Senior (over 50 :-) Researcher
>
> Institute for Infocomm Research disclaimer:  "This email is confidential
> and may be privileged. If you are not the intended recipient, please delete
> it and notify us immediately. Please do not copy or use it for any purpose,
> or disclose its contents to any other person. Thank you."
>



-- 
Eric B. Decker
Senior (over 50 :-) Researcher
___
Tinyos-help mailing list
Tinyos-

Re: [Tinyos-help] IO configuration

[He Dajiang (I2R)]

I did and found HplAtm128GeneralIOPinP.nc in folder: 
tinyos-2.1.2\tos\chips\atm128\pins.
In the file: there are two macro fucntions: SET_BIT and CLR_BIT, which do what 
I am not 100% sure. That's why I asked.
Sorry, not very familiar with direct MCU control.

From: Eric Decker [cire...@gmail.com]
Sent: Friday, 30 August, 2013 12:13:47 PM
To: He Dajiang (I2R)
Cc: Janos Sallai; tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] IO configuration

On Thu, Aug 29, 2013 at 6:45 PM, He Dajiang (I2R) 
mailto:h...@i2r.a-star.edu.sg>> wrote:
thx, Janos.

I used the following low level calls to make it work:

cli();
PORTD = PORTD | 0x03;
sei();

For you suggestion, I guess it is like

SensorP.IO0 -> HplAtm128GeneralIOC.PortE0;   // SCL
SensorP.IO1 -> HplAtm128GeneralIOC.PortE1;   // SDA

However, I don't quite understand what the following calls do:
call IO.makeInput();
call IO.set();// is it high or low
Call IO.set(1) leads to compiling error.

First I would recommend reading the source code to answer your own question.

I don't remember how things work on the MicaZ but the Msp430 does something 
similar.

A given digital I/O pin can be programmed to behave differently.  I.E. you can 
have it be an input or an output or connected to some different i/o h/w such as 
a UART or a SPI.  The call to makeInput sets the h/w up so the pin referenced 
as "IO" is configured as an input.

IO.set is a call that causes the pin to be set to a particular state.  
Typically ".set" will set the pin to a high state (set).  .clear or .clr will 
set the pin to a low value.

.set does not take a parameter and this is why "call IO.set(1)" gives you a 
compilation error.


like I said earlier you really should have taken a look at the source code 
yourself and answered these questions yourself.

when you make a build you can see exactly which files are being processed by 
doing "make verbose "


eric




From: sallai.ja...@gmail.com 
[sallai.ja...@gmail.com] on behalf of Janos 
Sallai [sal...@isis.vanderbilt.edu]
Sent: Thursday, 29 August, 2013 9:22:24 PM
To: He Dajiang (I2R)
Cc: 
tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] IO configuration

The best way to go is wiring the PortD interface of GeneralIOC, and
using the commands of the interface to get/set the levels and
directions of the pins.

Janos

On Thu, Aug 29, 2013 at 4:23 AM, He Dajiang (I2R)
mailto:h...@i2r.a-star.edu.sg>> wrote:
> Hi,
>
> For Micaz, what is the proper call to pull up the following two pins:
>
> PORTD0 and PORTD1
>
> Is it SET_BIT(PORTD, 0x03)?
>
> Best Regards
>
> Institute for Infocomm Research disclaimer:  "This email is confidential and 
> may be privileged. If you are not the intended recipient, please delete it 
> and notify us immediately. Please do not copy or use it for any purpose, or 
> disclose its contents to any other person. Thank you."
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>

Institute for Infocomm Research disclaimer:  "This email is confidential and 
may be privileged. If you are not the intended recipient, please delete it and 
notify us immediately. Please do not copy or use it for any purpose, or 
disclose its contents to any other person. Thank you."

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help



--
Eric B. Decker
Senior (over 50 :-) Researcher

Institute for Infocomm Research disclaimer:  "This email is confidential and 
may be privileged. If you are not the intended recipient, please delete it and 
notify us immediately. Please do not copy or use it for any purpose, or 
disclose its contents to any other person. Thank you."

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] TinyOS -XBee Module Commuication

[Bipin Kunjumon]

 I  am  doing  a  project  related  toRadio  Stack
Interoperability  using component  generalization.  Here  in  my
project  i  have  to  make  a  communication  between the  TinyOS FFD
and  XBee Module RFD,  it  tried  some  ways  that  i  got  from the  net,
but  that  doesn't  work..  Is  there have anyone  successfully  make the
communication between these  two ?  if  its  so.. please  help  me  to
solve  this..
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] IO configuration

[Eric Decker]

On Thu, Aug 29, 2013 at 6:45 PM, He Dajiang (I2R) wrote:

> thx, Janos.
>
> I used the following low level calls to make it work:
>
> cli();
> PORTD = PORTD | 0x03;
> sei();
>
> For you suggestion, I guess it is like
>
> SensorP.IO0 -> HplAtm128GeneralIOC.PortE0;   // SCL
> SensorP.IO1 -> HplAtm128GeneralIOC.PortE1;   // SDA
>
> However, I don't quite understand what the following calls do:
> call IO.makeInput();
> call IO.set();// is it high or low
> Call IO.set(1) leads to compiling error.
>

First I would recommend reading the source code to answer your own question.

I don't remember how things work on the MicaZ but the Msp430 does something
similar.

A given digital I/O pin can be programmed to behave differently.  I.E. you
can have it be an input or an output or connected to some different i/o h/w
such as a UART or a SPI.  The call to makeInput sets the h/w up so the pin
referenced as "IO" is configured as an input.

IO.set is a call that causes the pin to be set to a particular state.
 Typically ".set" will set the pin to a high state (set).  .clear or .clr
will set the pin to a low value.

.set does not take a parameter and this is why "call IO.set(1)" gives you a
compilation error.


like I said earlier you really should have taken a look at the source code
yourself and answered these questions yourself.

when you make a build you can see exactly which files are being processed
by doing "make verbose "


eric




> 
> From: sallai.ja...@gmail.com [sallai.ja...@gmail.com] on behalf of Janos
> Sallai [sal...@isis.vanderbilt.edu]
> Sent: Thursday, 29 August, 2013 9:22:24 PM
> To: He Dajiang (I2R)
> Cc: tinyos-help@millennium.berkeley.edu
> Subject: Re: [Tinyos-help] IO configuration
>
> The best way to go is wiring the PortD interface of GeneralIOC, and
> using the commands of the interface to get/set the levels and
> directions of the pins.
>
> Janos
>
> On Thu, Aug 29, 2013 at 4:23 AM, He Dajiang (I2R)
>  wrote:
> > Hi,
> >
> > For Micaz, what is the proper call to pull up the following two pins:
> >
> > PORTD0 and PORTD1
> >
> > Is it SET_BIT(PORTD, 0x03)?
> >
> > Best Regards
> >
> > Institute for Infocomm Research disclaimer:  "This email is confidential
> and may be privileged. If you are not the intended recipient, please delete
> it and notify us immediately. Please do not copy or use it for any purpose,
> or disclose its contents to any other person. Thank you."
> >
> > ___
> > Tinyos-help mailing list
> > Tinyos-help@millennium.berkeley.edu
> > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> >
>
> Institute for Infocomm Research disclaimer:  "This email is confidential
> and may be privileged. If you are not the intended recipient, please delete
> it and notify us immediately. Please do not copy or use it for any purpose,
> or disclose its contents to any other person. Thank you."
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>



-- 
Eric B. Decker
Senior (over 50 :-) Researcher
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] IO configuration

[He Dajiang (I2R)]

thx, Janos.

I used the following low level calls to make it work:

cli();
PORTD = PORTD | 0x03;
sei();

For you suggestion, I guess it is like

SensorP.IO0 -> HplAtm128GeneralIOC.PortE0;   // SCL
SensorP.IO1 -> HplAtm128GeneralIOC.PortE1;   // SDA

However, I don't quite understand what the following calls do:
call IO.makeInput();
call IO.set();// is it high or low
Call IO.set(1) leads to compiling error.

From: sallai.ja...@gmail.com [sallai.ja...@gmail.com] on behalf of Janos Sallai 
[sal...@isis.vanderbilt.edu]
Sent: Thursday, 29 August, 2013 9:22:24 PM
To: He Dajiang (I2R)
Cc: tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] IO configuration

The best way to go is wiring the PortD interface of GeneralIOC, and
using the commands of the interface to get/set the levels and
directions of the pins.

Janos

On Thu, Aug 29, 2013 at 4:23 AM, He Dajiang (I2R)
 wrote:
> Hi,
>
> For Micaz, what is the proper call to pull up the following two pins:
>
> PORTD0 and PORTD1
>
> Is it SET_BIT(PORTD, 0x03)?
>
> Best Regards
>
> Institute for Infocomm Research disclaimer:  "This email is confidential and 
> may be privileged. If you are not the intended recipient, please delete it 
> and notify us immediately. Please do not copy or use it for any purpose, or 
> disclose its contents to any other person. Thank you."
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>

Institute for Infocomm Research disclaimer:  "This email is confidential and 
may be privileged. If you are not the intended recipient, please delete it and 
notify us immediately. Please do not copy or use it for any purpose, or 
disclose its contents to any other person. Thank you."

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] SPIN MODEL CHECKER

[David Blubaugh]

Spin model checker is a validation and verification open source toolset to 
verify algorithms for trace errors etc.  
 
spinroot.com
 
Would you like to know more?
 
David
 
 
 
 



From: Eric Decker 
To: David Blubaugh  
Cc: "tinyos-help@millennium.berkeley.edu"  
Sent: Wednesday, August 28, 2013 8:37 PM
Subject: Re: [Tinyos-help] SPIN MODEL CHECKER





what is a spin model checker?  reference?




On Wed, Aug 28, 2013 at 12:11 PM, David Blubaugh  
wrote:

Has anyone ever used the spin model checker for verifying and validating 
designs within TinyOS???  
> 
>Also, can the designs with tinyos be of any large complexity or is there a 
>limit to the complexity of design???

how do you define  complexity?   how do you measure it?

tinyos programs are typically limited by RAM and code size.

 
>David Blubaugh
> 
> 
> 
> 
> 
> 
> 
>
>
>From: "tinyos-help-requ...@millennium.berkeley.edu" 
>
>To: tinyos-help@millennium.berkeley.edu 
>Sent: Wednesday, August 28, 2013 3:00 PM
>Subject: Tinyos-help Digest, Vol 124, Issue 26
>
>
>Send Tinyos-help mailing list submissions to
>    tinyos-help@millennium.berkeley.edu
>
>To subscribe or unsubscribe via the World Wide Web, visit
>    https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
>or, via email, send a message with subject or body 'help' to
>    tinyos-help-requ...@millennium.berkeley.edu
>
>You can reach the person managing the list at
>    tinyos-help-ow...@millennium.berkeley.edu
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Tinyos-help digest..."
>
>
>Today's Topics:
>
>  1.  LEAP+ Protocol (Syed Abdul basir)
>  2. Help:Telosb BaseStation (Nilavra Pathak)
>
>
>--
>
>Message: 1
>Date: Wed, 28 Aug 2013 04:19:20 -0700 (PDT)
>From: Syed Abdul basir 
>Subject: [Tinyos-help]  LEAP+ Protocol
>To: "tinyos-help@millennium.berkeley.edu"
>    
>Message-ID:
>    <1377688760.98794.yahoomail...@web162405.mail.bf1.yahoo.com>
>Content-Type: text/plain; charset="iso-8859-1"
>
>I am trying to compile leap+ code. getting the following error. can any one 
>help me thanks.? the red highlightederrors. thanks. 
>
>
>
>In file included from myLeapAppC.nc:17:
>In component `myLeapP':
>myLeapP.nc:31: interface MYA not found
>In file included from myLeapAppC.nc:17:
>myLeapP.nc:55: syntax error before `uint32_t'
>myLeapP: `ReceiveHello.receive' not implemented
>myLeapP: `TimerLed1Toggle.fired' not implemented
>myLeapP: `AMControl.startDone' not implemented
>myLeapP: `AMControl.stopDone' not implemented
>myLeapP: `TimerTimeStamp.fired' not implemented
>myLeapP: `Boot.booted' not implemented
>myLeapP: `AMSendTimeStamp.sendDone' not implemented
>myLeapP: `TimerHello.fired' not implemented
>myLeapP: `ReceiveStart.receive' not implemented
>myLeapP: `TimerMsgs.fired' not implemented
>myLeapP: `AMSendAck.sendDone' not implemented
>myLeapP: `TimerMain.fired' not implemented
>myLeapP: `TimerACK.fired' not implemented
>myLeapP: `AMSendTimeKeys.sendDone' not implemented
>myLeapP: `TimerHelloCount.fired' not implemented
>myLeapP: `TimerLed2Toggle.fired' not implemented
>myLeapP: `AMSendHello.sendDone' not implemented
>myLeapP: `TimeTimeKeys.fired' not implemented
>myLeapP: `ReceiveAck.receive' not implemented
>myLeapP: `TimerLed0Toggle.fired' not implemented
>In file included from 
>/opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketC.nc:25,
> from 
>/opt/tinyos-2.1.0/tos/chips/cc2420/csma/sim/CC2420CsmaC.nc:16,
> from 
>/opt/tinyos-2.1.0/tos/chips/cc2420/sim/CC2420RadioC.nc:63,
> from 
>/opt/tinyos-2.1.0/tos/chips/cc2420/sim/CC2420ActiveMessageC.nc:75,
> from 
>/opt/tinyos-2.1.0/tos/platforms/micaz/sim/ActiveMessageC.nc:61,
> from myLeapAppC.nc:18:
>In component `CC2420PacketP':
>/opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketP.nc: In function 
>`getNetwork':
>/opt/tinyos-2.1.0/tos/chips/cc2420/packet/sim/CC2420PacketP.nc:66: warning: 
>initialization from incompatible pointer type
>/opt/tinyos-2.1.0/tos/chips/cc2420/lpl/DummyLplC.nc:39:2: warning: #warning 
>"*** LOW POWER COMMUNICATIONS DISABLED ***"
>make: *** [sim-exe] Error 1
>-- next part --
>An HTML attachment was scrubbed...
>URL: 
>https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20130828/fdb9aaad/attachment-0001.htm
>
>--
>
>Message: 2
>Date: Wed, 28 Aug 2013 09:04:38 -0400
>From: Nilavra Pathak 
>Subject: [Tinyos-help] Help:Telosb BaseStation
>To: tinyos-help@millennium.berkeley.edu,
>    tinyos-help-requ...@millenniym.berkeley.edu
>Message-ID:
>    
>Content-Type: text/plain; charset="iso-8859-1"
>
>Hey Guys,
>
>I have tried to make  the BaseStation program run in the Telosb mote. I am
>using Ubuntu 13.04 for this .
>
>But every-time I try running the program nothing happens.
>
>To test whether the mo

Re: [Tinyos-help] IO configuration

[Janos Sallai]

The best way to go is wiring the PortD interface of GeneralIOC, and
using the commands of the interface to get/set the levels and
directions of the pins.

Janos

On Thu, Aug 29, 2013 at 4:23 AM, He Dajiang (I2R)
 wrote:
> Hi,
>
> For Micaz, what is the proper call to pull up the following two pins:
>
> PORTD0 and PORTD1
>
> Is it SET_BIT(PORTD, 0x03)?
>
> Best Regards
>
> Institute for Infocomm Research disclaimer:  "This email is confidential and 
> may be privileged. If you are not the intended recipient, please delete it 
> and notify us immediately. Please do not copy or use it for any purpose, or 
> disclose its contents to any other person. Thank you."
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] TUNIT help

[Mohammad Jamal Mohiuddin]

Anyone have good manual on TUNIT.

If yes mail me
---

This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
---

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] IO configuration

[He Dajiang (I2R)]

Hi,

For Micaz, what is the proper call to pull up the following two pins:

PORTD0 and PORTD1

Is it SET_BIT(PORTD, 0x03)?

Best Regards

Institute for Infocomm Research disclaimer:  "This email is confidential and 
may be privileged. If you are not the intended recipient, please delete it and 
notify us immediately. Please do not copy or use it for any purpose, or 
disclose its contents to any other person. Thank you."

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help