[Tinyos-help] Logging Data to Flash Problems
Hi all, I am working on an application in which I must log data to the flash. I am using TinyOS-1.1.15 and I am using the PageEEPROMC component with the EEPROMRead and EEPROMWrite interfaces. I am able to check that the use of the write and read functions returns successfully, but when I created a PC side application to make sure the data was written correctly I get a packet that looks random in data. Questions: 1) When using write and read functions can I actually only write or read 16 bytes/a line at a time, therefore having to loop through the writes and reads? Or can I pass a (example: uint8_t * data[20]) buffer to the function. Example: uint8_t data[20]; call EEPROMWrite.write(OFFSET, (uint8_t *)data); Will this write all 20 bytes to the flash starting at the OFFSET or will it only write the first two bytes?? The same goes for reading the data off of the flash. I am at my whits end testing flash reads and writes to no avail. Thank you for your help. Greg ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Communication model
Hi Iam trying to set up a simple communication model between 2 nodes, one as a base station and another as a sensor node. My concern is the communication between the 2 nodes, i.e. sending and receiving of packets. I have manage to sent messages using Generic Comm and for the receiving part, i actually made used of TOSBase. I used Listen.Java to monitor the packet data. I realise that Generic COmm doesn't offer any kind of acknowledgment when a packet is received. The sender just keep sending the packets to the base node. I need advice/suggestions on how to implement acknowledgment before sending the next packet. Thanks ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Help with porting programs to new TinyOS
I wrote a localization application using the old tinyos (i dont know the version, it just says tinyos-1.x, but i purchased the full thing from Crossbow in June 2003). There ListenRaw was working properly.Recently about a week back, i purchased the latest professiuonal kit with a MIB510 instead of the earlier parallel ported programming board and installed the lastest tinyos. When I try and run Listen application, it reports a packet length of 0. How did this happen. The packet i want to send to the UART is 10 bytes and it worled perfectly well with the old tinyos Any help would be greatly appreciated-- regards,Aditya Bhave ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re: tossim in dev branch working?
Please send questions to tinyos-help; that way, they're archived for
people to read in the future. Answer follows.
On Apr 13, 2006, at 1:44 AM, Omprakash Gnawali wrote:
Hi Phil,
Do you know if TOSSIM in dev branch is working?
In apps/Blink/BlinkC.nc:
event void Boot.booted()
{
dbg(BlinkC, booted\n);
call Timer0.startPeriodic( 250 );
call Timer1.startPeriodic( 500 );
call Timer2.startPeriodic( 1000 );
}
Then, make micaz sim.
Then in Python:
from TOSSIM import *
t = Tossim([])
m = t.getNode(32);
m.bootAtTime(45654);
import sys
t.addChannel(Boot, sys.stdout);
t.runNextEvent()
I don't see the message but it returns 1.
Your channel is BlinkC, not Boot.
Also, the Booted event is not assured to be signaled in the first
event. The boot event represents the OS, not the node, booting. There
might be a bunch of hardware events/tasks (which are TOSSIM events)
before the Boot.booted() event is signaled.
Phil
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] TinyOS building from source: Docs.
On 4/12/06, Muthiah Annamalai [EMAIL PROTECTED] wrote: Basically all Im asking for is, Which versio! ns of Nesc, Avr library suite, Tinyos work together? Which versions are friendly to each other, and what are their dependencies? If someone from the design team could provide a small document on this, it would save lot of Questions on the ML, and many-back-and-forth things. www.tinyos.net/dist-1.1.0 (for 1.x) and www.tinyos.net/dist-2.0.0 (for 2.x) should contain a consistent set of sources (and rpms, for that matter...). Check the tinyos/source and tools/source directories, and go for the latest version of things with multiple versions... David Gay ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re: tossim in dev branch working?
Your channel is BlinkC, not Boot.
Also, the Booted event is not assured to be signaled in the first
event. The boot event represents the OS, not the node, booting. There
might be a bunch of hardware events/tasks (which are TOSSIM events)
before the Boot.booted() event is signaled.
Phil
The BlinkC vs. Boot channel was a typo in the command I sent to the
mailing list. Here is what my BlinkC looks like (the only change is
adding dbg message in booted():
event void Boot.booted()
{
dbg(BlinkC, booted\n);
call Timer0.startPeriodic( 250 );
call Timer1.startPeriodic( 500 );
call Timer2.startPeriodic( 1000 );
}
event void Timer0.fired()
{
dbg(BlinkC, Timer 0 fired @ %s.\n, sim_time_string());
call Leds.led0Toggle();
}
event void Timer1.fired()
{
dbg(BlinkC, Timer 1 fired @ %s \n, sim_time_string());
call Leds.led1Toggle();
}
event void Timer2.fired()
{
dbg(BlinkC, Timer 2 fired @ %s.\n, sim_time_string());
call Leds.led2Toggle();
}
Here is TOSSIM. I see times such as 2500045654L, 545654L,
1045654L - does that mean the timers are firing? I am still not
able to get the debug messages.
from TOSSIM import *;
t = Tossim([]);
m = t.getNode(32);
m.bootAtTime(45654);
import sys;
t.addChannel(BlinkC, sys.stdout);
m.isOn();
0
t.runNextEvent();
1
m.isOn();
1
for i in range(50):
... t.runNextEvent();
... t.time();
...
1
45754L
1
45854L
1
78170654L
1
1250045654L
1
2441451904L
1
2441452004L
1
2441452104L
1
2500045654L
1
2500045654L
1
3691451904L
1
4882858154L
1
4882858254L
1
4882858354L
1
4941451904L
1
545654L
1
6132858154L
1
7324264404L
1
7324264504L
1
7324264604L
1
7382858154L
1
7500045654L
1
8574264404L
1
9765670654L
1
9765670754L
1
9765670854L
1
9824264404L
1
1045654L
1
11015670654L
1
12207076904L
1
12207077004L
1
12207077104L
1
12265670654L
1
12500045654L
1
13457076904L
1
14648483154L
1
14648483254L
1
14648483354L
1
14707076904L
1
1545654L
1
15898483154L
1
17089889404L
1
17089889504L
1
17089889604L
1
17148483154L
1
17500045654L
1
18339889404L
1
19531295654L
1
19531295754L
1
19531295854L
1
19589889404L
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] tmote/telos security protocol development
I haven't heard of any updates, though people Tmote/Telos On 4/10/06, adina [EMAIL PROTECTED] wrote: Hi! I have read some mails from the archive, which state that TinySec was not implemented for tmote. Does anyone know, whether this has changed since last year or not? Has someone implemented something like tinysec for tmote or any kind of security protocol for tmote? Thanks -- Feel free - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] tmote/telos security protocol development
I haven't heard of any updates in this area. The CC2420 radio on Tmote/Telos has built in encryption and authentication, and it's just waiting for from security minded folks to put a sensible security API around it. - Cory On 4/10/06, adina [EMAIL PROTECTED] wrote: Hi! I have read some mails from the archive, which state that TinySec was not implemented for tmote. Does anyone know, whether this has changed since last year or not? Has someone implemented something like tinysec for tmote or any kind of security protocol for tmote? Thanks -- Feel free - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Measuring battery level
Hi all, I was wondering if there is a way to measure battery level of a sensor ? If there is, are there any modules/interfaces already developed, that one can use for that ? Any help is greatly appreciated, Demijan ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] UART address in Surge, base station code
In Surge, the base station is programmed with the ID=0 andt is installed with the same program. How does it know that a node with an ID 0 is the root node and is just supposed to send data to the UART, coz I didn't find any code which addresses the UART in the application? Is it something that is done by default in Multihop routing, like when the app knows to get the node ID from TOS_LOCAL_ADDRESS? Thanks, Avanthi. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Measuring battery level
I assume you mean that your sensor has a separate battery from the mote. If so you can use an available ADC channel with appropriate buffering or resistor ladder to measure an external voltage, e.g., your battery. See the ADC component, or any of the sensor impls that use it. MS [EMAIL PROTECTED] wrote: Hi all, I was wondering if there is a way to measure battery level of a sensor ? If there is, are there any modules/interfaces already developed, that one can use for that ? Any help is greatly appreciated, Demijan ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Surge-Reliable Running problem!???
Hi everyone, I tried to run under /opt/tinyos-1.x/contrib/xbow/apps/Surge_Reliable, but the result shows like : $ make mica2 install,1 mib510,com1mkdir -p build/mica2 compiling Surge to a mica2 binaryncc -o build/mica2/main.exe -Os -I../../tos/platform/mica2 -I../../tos/CC1000RaioAck -I../../tos/lib/ReliableRoute -I%T/lib/Queue -I%T/lib/Broadcast -I%T/lib/ttributes -finline-limit=10 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x81 -Wnesc-al -target=mica2 -fnesc-cfile=build/mica2/app.c -board=micasb -DCC1K_DEFAULT_FRE=RADIO_916BAND_CHANNEL_00 -DRADIO_XMIT_POWER=0xFF -DIDENT_PROGRAM_NAME="Surge"DIDENT_PROGRAM_NAME_BYTES="83,117,114,103,101,0" -DIDENT_USER_HASH=0xd63717c4LDIDENT_UNIX_TIME=0x443efb1aL Surge.nc -lmSurgeM.nc: In function `SendData':SurgeM.nc:124: warning: passing argument 2 of `AttrUse.getAttrValue' from incomatible pointer typeSurgeM.nc:124: warning: passing argument 3 of `AttrUse.getAttrValue' from incomatible pointer typeSurgeM.nc:125: warning: passing argument 2 of `AttrUse.getAttrValue' from incomatible pointer typeSurgeM.nc:125: warning: passing argument 3 of `AttrUse.getAttrValue' from incomatible pointer typeSurgeM.nc: At top level:SurgeM.nc:187: warning: `LightStdControl.stop' called asynchronously from `Ligh.dataReady'SurgeM.nc:188: warning: `TempStdControl.start' called asynchronously from `Ligh.dataReady'SurgeM.nc:189: warning: `TempTimer.start' called asynchronously from `Light.datReady'SurgeM.nc:205: warning: `TempStdControl.stop' called asynchronously from `Temp.ataReady'AttrMagM.nc:133: warning: non-atomic accesses to shared variable `bufr_data':AttrMagM.nc:150: warning: non-atomic r/wAttrMagM.nc:151: warning: non-atomic readAttrMagM.nc:152: warning: non-atomic writeAttrMagM.nc:156: warning: non-atomic readAttrMagM.nc:158: warning: non-atomic r/wAttrMagM.nc:166: warning: non-atomic readAttrMagM.nc:167: warning: non-atomic readAttrMagM.nc:171: warning: non-atomic writeAttrMagM.nc:172: warning: non-atomic writeAttrMagM.nc:186: warning: non-atomic writeAttrMagM.nc:246: warning: non-atomic readAttrMagM.nc:247: warning: non-atomic r/wAttrMagM.nc:250: warning: non-atomic writeAttrMagM.nc:366: warning: non-atomic writeAttrMagM.nc:367: warning: non-atomic writeAttrMagM.nc:446: warning: non-atomic writeAttrMagM.nc:446: warning: non-atomic readAttrMagM.nc:458: warning: non-atomic writeAttrMagM.nc:458: warning: non-atomic readAttrMagM.nc:482: warning: non-atomic writeAttrMagM.nc:501: warning: non-atomic writeAttrMagM.nc:502: warning: non-atomic writeAttrMagM.nc:504: warning: non-atomic writeAttrMagM.nc:505: warning: non-atomic writeAttrMagM.nc:506: warning: non-atomic writeAttrMagM.nc:509: warning: non-atomic writeAttrMagM.nc:510: warning: non-atomic writeAttrMagM.nc:135: warning: non-atomic accesses to shared variable `maxMagX':AttrMagM.nc:374: warning: non-atomic writeAttrMagM.nc:447: warning: non-atomic readAttrMagM.nc:448: warning: non-atomic writeAttrMagM.nc:525: warning: non-atomic readAttrMagM.nc:525: warning: non-atomic writeAttrMagM.nc:526: warning: non-atomic readAttrMagM.nc:528: warning: non-atomic writeAttrMagM.nc:135: warning: non-atomic accesses to shared variable `maxMagY':AttrMagM.nc:375: warning: non-atomic writeAttrMagM.nc:459: warning: non-atomic readAttrMagM.nc:460: warning: non-atomic writeAttrMagM.nc:547: warning: non-atomic readAttrMagM.nc:548: warning: non-atomic writeC:/tinyos/cygwin/opt/tinyos-1.x/contrib/xbow/tos/CC1000RadioAck/CC1000RadioIntMnc:187: warning: non-atomic accesses to shared variable `usRSSIVal':C:/tinyos/cygwin/opt/tinyos-1.x/contrib/xbow/tos/CC1000RadioAck/CC1000RadioIntMnc:953: warning: non-atomic readC:/tinyos/cygwin/opt/tinyos-1.x/contrib/xbow/tos/CC1000RadioAck/CC1000RadioIntMnc:183: warning: non-atomic accesses to shared variable `bTxPending':C:/tinyos/cygwin/opt/tinyos-1.x/contrib/xbow/tos/CC1000RadioAck/CC1000RadioIntMnc:454: warning: non-atomic readC:/tinyos/cygwin/opt/tinyos-1.x/contrib/xbow/tos/lib/ReliableRoute/MultiHopEWMAnc: In function `MultiHopEWMA$SendRouteTask':C:/tinyos/cygwin/opt/tinyos-1.x/contrib/xbow/tos/lib/ReliableRoute/MultiHopEWMAnc:444: warning: unused variable `sortTbl'SurgeM.nc: In function `SurgeM$TempTimer$fired':SurgeM.nc:194: warning: no return statement in function returning non-voidSurgeM.nc: In function `SurgeM$SendData':SurgeM.nc:124: warning: passing arg 2 of `SurgeM$AttrUse$getAttrValue' from incmpatible pointer typeSurgeM.nc:125: warning: passing arg 2 of `SurgeM$AttrUse$getAttrValue' from incmpatible pointer typeC:/tinyos/cygwin/opt/tinyos-1.x/tos/system/RealMain.nc: In function `main':C:/tinyos/cygwin/opt/tinyos-1.x/tos/interfaces/StdControl.nc:63: warning: `resut' might be used uninitialized in this function compiled Surge to build/mica2/main.exe 22502 bytes in ROM 2142 bytes in RAMavr-objcopy --output-target=srec build/mica2/main.exe build/mica2/main.srecset-mote-id build/mica2/main.srec build/mica2/main.srec.out 1 installing mica2 binary using mib510uisp -dprog=mib510 -dserial=com1 -dpart=ATmega128
Re: [Tinyos-help] tmote/telos security protocol development
Is there any documentation of the security API provided by the CC2420 radio? In particular, how to enable/disable security, how to instantiate and change keys, etc.Thanks,- Vinayak On 4/13/06, Cory Sharp [EMAIL PROTECTED] wrote: I haven't heard of any updates in this area.The CC2420 radio onTmote/Telos has built in encryption and authentication, and it's justwaiting for from security minded folks to put a sensible security APIaround it.- Cory On 4/10/06, adina [EMAIL PROTECTED] wrote: Hi! I have read some mails from the archive, which state that TinySec was not implemented for tmote. Does anyone know, whether this has changed since last year or not? Has someone implemented something like tinysec for tmote or any kind of security protocol for tmote? Thanks -- Feel free - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___Tinyos-help mailing listTinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Error message: ncc command not found
I got the latest source code of TinyOS1.1.x from CVS. I am running Cygwin 1.2a on Windows XP. When I type make in Apps/Blink, I got the error message that ncc is not found.$ make pcmake: ncc: Command not foundmkdir -p build/pc compiling Blink to a pc binaryncc -o build/pc/main.exe -g -O0 -pthread -fnesc-nido-tosnodes=1000 -fnesc-simulate -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=pc -fnesc-cfile=build/pc/app.c -board=micasb Blink.nc -lmmake: ncc: Command not foundmake: *** [exe0] Error 127I have done make in Tools folder already, and got the following output (does this mean the make in Tools has failed? "gmake is not found", is this the problem?):$ maketarget=`echo all-recursive | sed s/-recursive//`; \(cd scripts make $target); \(cd src make $target)make[1]: Entering directory `/opt/tinyos-1.x/tools/scripts'make[1]: Nothing to be done for `all'.make[1]: Leaving directory `/opt/tinyos-1.x/tools/scripts'make[1]: Entering directory `/opt/tinyos-1.x/tools/src'(cd uisp ./COMPILE)gnumake: not foundgmake: not foundmake[2]: Entering directory `/opt/tinyos-1.x/tools/src/uisp'Making all in srcmake[3]: Entering directory `/opt/tinyos-1.x/tools/src/uisp/src'c++ -DHAVE_CONFIG_H -I. -I. -I. -Wall -Werror -g -O2 -c Avr.Cc++ -DHAVE_CONFIG_H -I. -I. -I. -Wall -Werror -g -O2 -c AvrAtmel.Cc++ -DHAVE_CONFIG_H -I. -I. -I. -Wall -Werror -g -O2 -c AvrDummy.Cc++ -DHAVE_CONFIG_H -I. -I. -I. -Wall -Werror -g -O2 -c AvrStargate.Cc++ -DHAVE_CONFIG_H -I. -I. -I. -Wall -Werror -g -O2 -c DAPA.Cc++ -DHAVE_CONFIG_H -I. -I. -I. -Wall -Werror -g -O2 -c Main.Cc++ -DHAVE_CONFIG_H -I. -I. -I. -Wall -Werror -g -O2 -c MotIntl.Cc++ -DHAVE_CONFIG_H -I. -I. -I. -Wall -Werror -g -O2 -c SASA.Cc++ -DHAVE_CONFIG_H -I. -I. -I. -Wall -Werror -g -O2 -c Serial.Cc++ -DHAVE_CONFIG_H -I. -I. -I. -Wall -Werror -g -O2 -c Stk500.Cc++ -DHAVE_CONFIG_H -I. -I. -I. -Wall -Werror -g -O2 -c Terminal.Cc++ -DHAVE_CONFIG_H -I. -I. -I. -Wall -Werror -g -O2 -c cygwinp.Cc++ -Wall -Werror -g -O2 -o uisp Avr.o AvrAtmel.o AvrDummy.o AvrStargate.o DAPA.o Main.o MotIntl.o SASA.o Serial.o Stk500.o Terminal.o cygwinp.omake[3]: Leaving directory `/opt/tinyos-1.x/tools/src/uisp/src'make[3]: Entering directory `/opt/tinyos-1.x/tools/src/uisp'make[3]: Nothing to be done for `all-am'.make[3]: Leaving directory `/opt/tinyos-1.x/tools/src/uisp'make[2]: Leaving directory `/opt/tinyos-1.x/tools/src/uisp'(cd CC1000 make)make[2]: Entering directory `/opt/tinyos-1.x/tools/src/CC1000'make[2]: Nothing to be done for `all'.make[2]: Leaving directory `/opt/tinyos-1.x/tools/src/CC1000'make[1]: Leaving directory `/opt/tinyos-1.x/tools/src' Make Yahoo! Canada your Homepage Yahoo! Canada Homepage ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] tmote/telos security protocol development
Hi Vinayak, The CC2420 datasheet has this information: http://www.chipcon.com/files/CC2420_Data_Sheet_1_4.pdf - Prabal On 4/13/06, Vinayak Naik [EMAIL PROTECTED] wrote: Is there any documentation of the security API provided by the CC2420 radio? In particular, how to enable/disable security, how to instantiate and change keys, etc. Thanks, - Vinayak On 4/13/06, Cory Sharp [EMAIL PROTECTED] wrote: I haven't heard of any updates in this area. The CC2420 radio on Tmote/Telos has built in encryption and authentication, and it's just waiting for from security minded folks to put a sensible security API around it. - Cory On 4/10/06, adina [EMAIL PROTECTED] wrote: Hi! I have read some mails from the archive, which state that TinySec was not implemented for tmote. Does anyone know, whether this has changed since last year or not? Has someone implemented something like tinysec for tmote or any kind of security protocol for tmote? Thanks -- Feel free - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
