[Tinyos-help] Swapping TOS message buffer Problem
Hi every one,
I have a problem with swapping tos
message buffer
I have to develop an application which has to receive a TOS
Message through air and then Broad cast the message.
The code is
TOS_MsgPtr msg_buff;
event TOS_MsgPtr ReceiveMsg.receive(TOS_MsgPtr m)
{
TOS_MsgPtr tmp=msg_buff;
msg_buff=m;
call Leds.greenToggle();
post SendData();
return tmp;
}
Basically im performing the buffer swap operation. But the
problem is I can receive only the first Message.
I think there is some problem with the buffer swap. Can any
one please help me regarding this.
Thanking you in advance
R.Hari Hara Sudhan
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Make error for cygwin
Hi, after updating form version 1.x to 2.x, I am trying to compile one of the applications (Blink), either with make micaz sim or make micaz and ann error repoted and cygwin generate this error message: The procedure entry point __getreent could not be located in the dynamic link library cygwin1.dll Any help please -- Firas Daghmash ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] Swapping TOS message buffer Problem
First I think you have to return m in the end of the event. And think about
they are pointers,so for example:
void swap (int *px, int *py){
int temp;
temp=*px;
*px=*py;
*py=temp;
}
before you were swapping the copies of the elements.
cheers
Daniele
-Original Message-
From: Hari Hara Sudhan [mailto:[EMAIL PROTECTED]
Sent: Wed 9/6/2006 9:56 AM
To: tinyos-help@Millennium.Berkeley.EDU
Cc:
Subject: [Tinyos-help] Swapping TOS message buffer Problem
Hi every one,
I have a problem with swapping tos message buffer
I have to develop an application which has to receive a TOS Message
through air and then Broad cast the message.
The code is
TOS_MsgPtr msg_buff;
event TOS_MsgPtr ReceiveMsg.receive(TOS_MsgPtr m)
{
TOS_MsgPtr tmp=msg_buff;
msg_buff=m;
call Leds.greenToggle();
post SendData();
return tmp;
}
Basically im performing the buffer swap operation. But the problem is I
can receive only the first Message.
I think there is some problem with the buffer swap. Can any one please
help me regarding this.
Thanking you in advance
R.Hari Hara Sudhan
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re: Error Compiling Nucleus enabled application in Cygwin for PC platform
Adding to the problem, it seems that there is a problem with tinyos-1.x/tos/platform/pc/hpl.c file. Please look into it. Also, I hve seen a suggestion posted at http://mail.millennium.berkeley.edu/pipermail/tinyos-commits/2005-June/006162.html Making change in it because of simulation problem mentioned on it. Should we do it? Please send me the correct hpl.c file as I am incapable of fixing this error. Regards, SumitOn 9/6/06, Sumit Gupta <[EMAIL PROTECTED]> wrote: Hi, I installed nucleus on cygwin and I am having some problem while compiling an application /tinyos-1.x/apps/CntToLeds. I followed instructions given in Nucleus Manual but I am Getting following errors only when I am trying to compile it with PC platform. (make pc nucleus) but it compiled fine when I tried to compile it with platform mica2 (make mica2 nucleus). Please help me in sorting this problem. $ make pc nucleus mkdir -p build/pc ** Removing old generated files prior to compilation rm -f build/pc/AttrGenC.nc build/pc/EventGenC.nc rm -f build/pc/nucleusSchema.xml ** Generating nesC interface dump for CntToLeds on pc ncc -fsyntax-only -fnesc-dump=interfaces -fnesc-dump=tags -g -O0 -pthread -I%T/l ib/Counters -I -fnesc-nido-tosnodes=1000 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=pc -fnesc-cfile=build/pc/app.c -board=micasb -I/opt/tinyos-1 .x/tos/../beta/Drip -I/opt/tinyos-1.x/tos/../beta/Drain -I/opt/tinyos-1.x/tos/.. /contrib/nucleus/tos/lib/Nucleus -I%T/../beta/Drip -I%T/../beta/Drain -I%T/../co ntrib/nucleus/tos/lib/Nucleus -I%T/../contrib/nucleus/tos/lib/NucleusExamples -D IDENT_PROGRAM_NAME="CntToLeds" -DIDENT_PROGRAM_NAME_BYTES="67,110,116,84,111,76, 101,100,115,0" -DIDENT_USER_ID="Sumit" -DIDENT_USER_ID_BYTES="83,117,109,105,116 ,0" -DIDENT_HOSTNAME="superComp" -DIDENT_HOSTNAME_BYTES="115,117,112,101,114,67, 111,109,112,0" -DIDENT_USER_HASH=0x85ed13fbL -DIDENT_UNIX_TIME=0x44fe76b3L CntTo Leds.nc -lm > build/pc/nesc.xml In file included from /opt/tinyos-1.x/tos/platform/pc/hardware.h:43, from /opt/tinyos-1.x/tos/system/tos.h:144: /opt/tinyos-1.x/tos/platform/pc/nido.h:63: `TOSH_NUM_NODES' undeclared here (not in a function) /opt/tinyos-1.x/tos/platform/pc/nido.h:63: enumerator value for `TOSNODES' not i nteger constant In file included from /opt/tinyos-1.x/tos/platform/pc/hardware.h:110, from /opt/tinyos-1.x/tos/system/tos.h:144: /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_set_interval': /opt/tinyos-1.x/tos/platform/pc/hpl.c:65: warning: implicit declaration of funct ion `event_clocktick_invalidate' /opt/tinyos-1.x/tos/platform/pc/hpl.c:80: warning: implicit declaration of funct ion `event_clocktick_create' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_set_rate': /opt/tinyos-1.x/tos/platform/pc/hpl.c:94: warning: implicit declaration of funct ion `event_clocktick_invalidate' /opt/tinyos-1.x/tos/platform/pc/hpl.c:105: warning: implicit declaration of func tion `event_clocktick_create' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_int_disable': /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: (Each undeclared identifier is report ed only once /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: for each function it appears in.) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_int_enable': /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_clocktick_handle': /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_clocktick_create': /opt/tinyos-1.x/tos/platform/pc/hpl.c:194: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:194: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_clocktick_invalidate': /opt/tinyos-1.x/tos/platform/pc/hpl.c:212: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:212: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_adc_sample_port': /opt/tinyos-1.x/tos/platform/pc/hpl.c:248: warning: implicit declaration of func tion `event_adc_create' /opt/tinyos-1.x/tos/platform/pc/hpl.c:253: warning: implicit declaration
[Tinyos-help] Re: Error Compiling Nucleus enabled application in Cygwin for PC platform
I just noticed that I cannot even compile a normal pc application i.e. without nucleus. Is it because I forgot to add any path or somthing. I just want to inform that I tried to install Nucleus before this and followed all the steps successfully mentioned in its manual. I installed it on cygwin, however, I couldnot installed it on Debian as there was some other problem with it. Please give a look. Regards, SumitOn 9/6/06, Sumit Gupta <[EMAIL PROTECTED]> wrote: Adding to the problem, it seems that there is a problem with tinyos-1.x/tos/platform/pc/hpl.c file. Please look into it. Also, I hve seen a suggestion posted at http://mail.millennium.berkeley.edu/pipermail/tinyos-commits/2005-June/006162.html Making change in it because of simulation problem mentioned on it. Should we do it? Please send me the correct hpl.c file as I am incapable of fixing this error. Regards, SumitOn 9/6/06, Sumit Gupta < [EMAIL PROTECTED]> wrote: Hi, I installed nucleus on cygwin and I am having some problem while compiling an application /tinyos-1.x/apps/CntToLeds. I followed instructions given in Nucleus Manual but I am Getting following errors only when I am trying to compile it with PC platform. (make pc nucleus) but it compiled fine when I tried to compile it with platform mica2 (make mica2 nucleus). Please help me in sorting this problem. $ make pc nucleus mkdir -p build/pc ** Removing old generated files prior to compilation rm -f build/pc/AttrGenC.nc build/pc/EventGenC.nc rm -f build/pc/nucleusSchema.xml ** Generating nesC interface dump for CntToLeds on pc ncc -fsyntax-only -fnesc-dump=interfaces -fnesc-dump=tags -g -O0 -pthread -I%T/l ib/Counters -I -fnesc-nido-tosnodes=1000 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=pc -fnesc-cfile=build/pc/app.c -board=micasb -I/opt/tinyos-1 .x/tos/../beta/Drip -I/opt/tinyos-1.x/tos/../beta/Drain -I/opt/tinyos-1.x/tos/.. /contrib/nucleus/tos/lib/Nucleus -I%T/../beta/Drip -I%T/../beta/Drain -I%T/../co ntrib/nucleus/tos/lib/Nucleus -I%T/../contrib/nucleus/tos/lib/NucleusExamples -D IDENT_PROGRAM_NAME="CntToLeds" -DIDENT_PROGRAM_NAME_BYTES="67,110,116,84,111,76, 101,100,115,0" -DIDENT_USER_ID="Sumit" -DIDENT_USER_ID_BYTES="83,117,109,105,116 ,0" -DIDENT_HOSTNAME="superComp" -DIDENT_HOSTNAME_BYTES="115,117,112,101,114,67, 111,109,112,0" -DIDENT_USER_HASH=0x85ed13fbL -DIDENT_UNIX_TIME=0x44fe76b3L CntTo Leds.nc -lm > build/pc/nesc.xml In file included from /opt/tinyos-1.x/tos/platform/pc/hardware.h:43, from /opt/tinyos-1.x/tos/system/tos.h:144: /opt/tinyos-1.x/tos/platform/pc/nido.h:63: `TOSH_NUM_NODES' undeclared here (not in a function) /opt/tinyos-1.x/tos/platform/pc/nido.h:63: enumerator value for `TOSNODES' not i nteger constant In file included from /opt/tinyos-1.x/tos/platform/pc/hardware.h:110, from /opt/tinyos-1.x/tos/system/tos.h:144: /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_set_interval': /opt/tinyos-1.x/tos/platform/pc/hpl.c:65: warning: implicit declaration of funct ion `event_clocktick_invalidate' /opt/tinyos-1.x/tos/platform/pc/hpl.c:80: warning: implicit declaration of funct ion `event_clocktick_create' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_set_rate': /opt/tinyos-1.x/tos/platform/pc/hpl.c:94: warning: implicit declaration of funct ion `event_clocktick_invalidate' /opt/tinyos-1.x/tos/platform/pc/hpl.c:105: warning: implicit declaration of func tion `event_clocktick_create' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_int_disable': /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: (Each undeclared identifier is report ed only once /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: for each function it appears in.) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_int_enable': /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_clocktick_handle': /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_clocktick_create': /opt/tinyos-1.x/tos/platform/pc/hpl.c:194: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:194: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_cl
Re: [Tinyos-help] Documentation for tmote
I don't think that is a problem about mixing 1.x code with 2.x code, because it happens with all the applications included with tinyos-1.x under /apps. Moreover, if I try to generate the documentation for the platform mica I get no error, but if I do the same with the same application for tmote I get the 'generic components' error described previously. I'm working under linux (ubuntu 6.06) and installed the software for the tmotes following the guide in [1].[1]: http://www.chadmetcalf.com/tinyos-1x-on-ubuntu/Philip Levis <[EMAIL PROTECTED]> escribió: On Sep 5, 2006, at 7:26 AM, Pablo Gil Montaño wrote:> Hi,>> I have a problem with nesdoc: everytime I try to generate > documentation with 'make tmote docs' I get the following error:>> nesc1: documentation system does not yet support generic components > and interfaces> make: *** [mot_docs_] Error 1>> It happens with programs included in tinyos-1.x/apps that work > allright on my tmotes. If I try to generate documentation for > another platform (e.g.: make mica docs,here), it works perfectly. > The problem is that I want to do it with a platform-specific > application which won't compile for either mica or telos. Any > suggestions?>It sounds like you're using a 1.x toolchain on code that has 2.x abstractions. You need to install the 2.x toolchain.Do you know what code is causing this problem? In theory, no 1.x code should have generic components, and any that does should be removed from the 1.x tree.Phil LLama Gratis a cualquier PC del Mundo.Llamadas a fijos y móviles desde 1 céntimo por minuto.http://es.voice.yahoo.com___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Documentation for tmote
The problem is that I am using Linux (Ubuntu 6.06) and I can't just install the .exe provided by moteiv. I've followed the guide in [1], and apart from the problem with the documentation, everything seems to be working.[1]: http://www.chadmetcalf.com/tinyos-1x-on-ubuntu/ Joe Polastre <[EMAIL PROTECTED]> escribió: Try installing Boomerang 2.0.4. It includes all the necessary toolsand configuration for nesdoc to work correctly.-JoeOn 9/5/06, Pablo Gil Montaño <[EMAIL PROTECTED]> wrote:> Hi,>> I have a problem with nesdoc: everytime I try to generate documentation with> 'make tmote docs' I get the following error:>> nesc1: documentation system does not yet support generic components and> interfaces> make: *** [mot_docs_] Error 1>> It happens with programs included in tinyos-1.x/apps that work allright on> my tmotes. If I try to generate documentation for another platform (e.g.:> make mica docs,here), it works perfectly. The problem is that I want to do> it with a platform-specific application which won't compile for either mica> or telos. Any suggestions?>> Bye!>>> >> LLama Gratis a cualquier PC del Mundo.> Llamadas a fijos y móviles desde 1 céntimo por minuto.> http://es.voice.yahoo.com>>> ___> Tinyos-help mailing list> Tinyos-help@Millennium.Berkeley.EDU> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help>> LLama Gratis a cualquier PC del Mundo.Llamadas a fijos y móviles desde 1 céntimo por minuto.http://es.voice.yahoo.com___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] TOSComm vs RXTX in Linux?
Perhaps these installation guides will help you. I've followed [2] and everything seems to work ok except for the documentation generation. I have Ubuntu 6.06 and I had to change the link /usr/bin/java to the sun executable instead of the one included with ubuntu, but apart form that, I followed the steps in [2]. I don't know up to which extent this will be applicable to gentoo, but ubuntu isn't RPM-based either.[1]: http://www.moteiv.com/community/Tmote_Linux_install[2]: http://www.chadmetcalf.com/tinyos-1x-on-ubuntu/Andy Dalton <[EMAIL PROTECTED]> escribió: Greetings,I'm wondering what is the status of TOSComm? I'm currently usingrxtx-2.1-7pre17 in Linux and I frequently get the following error whentrying to send a message to a Tmote Sky over USB via MoteIF:## An unexpected error has been detected by HotSpot Virtual Machine:## SIGSEGV (0xb) at pc=0xa841873a, pid=17051, tid=2820193184## Java VM: Java HotSpot(TM) Client VM (1.5.0_05-b05 mixed mode)# Problematic frame:# C [librxtxSerial-2.1-7pre17.so+0x773a] initialise_event_info_struct+0x18a## An error report file with more information is saved as hs_err_pid17051.log## If you would like to submit a bug report, please visit:# http://java.sun.com/webapps/bugreport/crash.jsp#Will TOSComm do everything (i.e. support all the TinyOS tools) thatRXTX does? If not, does anyone have any idea what might be causingthat error?Also, I'm not on an RPM-based Linux system (I'm running Gentoo), wherecan I find an install guide for TinyOS?Thanks in advance,Andy___Tinyos-help mailing listTinyos-help@Millennium.Berkeley.EDUhttps://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help LLama Gratis a cualquier PC del Mundo.Llamadas a fijos y móviles desde 1 céntimo por minuto.http://es.voice.yahoo.com___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] I2C Driver for MSP430
I'm trying to solve a problem which is rose with the i2c driver for msp430. Shortly, I call a I2C read operation and get the readDone signal. If i call another I2C read or write command, i don't get any signal (readDone or Writedone) back. All these operations are called with the I2C_START|I2C_STOP flag. I've seen that no interrupt is generated by the micro when the second command stop condition is transmitted. I'm using the current develop version. Any suggestion? - Max ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] mica2 programming problems
I am having problems programming a mica2 mote. when i use the make install... command the load seems to be successfully. however, the program does not seem to be running. i am trying to load the blink app onto the mote but the led does not blink. when the mote is powered all three LEDs light, then power off one at a time (yellow, green, red), after which there is no output. If anyone has had similar problems or can provide any advice, that would be great. Thanks, Sam ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
AW: [Tinyos-help] "undefined reference" during "make micaz sim"
Hi Phil, thank you. For my problem there was a work-aroung from you (i guess) by e-mail earlier: TOSSIM for TinyOS 2.0 currently does not work under Cygwin. It turns out to be a really nasty problem: in Windows, shared objects cannot have undefined references. The way most python modules work is that they link against the interpreter (e.g., for functions to manipulate basic data types). There are ways around it, but it's going to be some work (you have to create an importlib that the shared object can link against). It'll definitely be there for the full release. Until then, you can still run TOSSIM as a C++ program. The latter parts of the tutorial go into how to do this. Alternatively, you can run Linux inside VMWare or Xen. Scratch that. Kaisen Lin and I just figured it out. It looks like CVS is down right now, so I've put a fix up on the web: http://csl.stanford.edu/~pal/tinyos/sim-cygwin.extra Download this file and put it in your tinyos-2.x/support/make directory. Instead of typing 'make micaz sim' type 'make micaz sim-cygwin'. You'll still get some warnings about shadowed declarations (I'll clean those up when I can), but you should be able to compile and use TOSSIM under cygwin. I'll eventually fold this stuff into the basic sim.extra so it acts conditionally on whether you're under Cygwin. This file assumes that you have Python 2.3; if you have a different version, you might need to change the file a bit. Eventually, the 2.x install might detect this sort of thing, but for now you might need to tweak files a bit. Phil On Aug 25, 2006, at 2:23 PM, Alexander Gäßler wrote: > I newly installed MS Windows XP Pro SP2 with German MUI package. > I newly installed Cygwin 1.5.21-1 release. > I newly installed and configured TinyOS 2.0 beta2 as described on > www.tinyos.net. > Everything works fine, tos-check-env too. > > But there was one problem during the make of TOSSIM files. > I run "make micaz sim" when error messages appear concerning > "undefined reference to ". > I could not found any suggestion. Did one of you have? > > Thanks, > Alex It looks like the version of Python you have is different than what the TOSSIM compilation sequence expects. The beta2 RPM currently does not automatically determine what Python version you have and adjust accordingly (it should). Type python -V Then go to support/make/sim.extra And change the variable PYTHON_VERSION to be the first two digits of your python. E.g., if you have 2.4.1, change it to be PYTHON_VERSION=2.4 Also, check that you have a directory /usr/lib/pythonX.Y If you don't, you might need to download a python-devel RPM. Phil ___ 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] why do i get this warning... no new line at end of file
hello everybody In many of my programs when i compile there is warning stating xyz.nc:9:2: warning: no new line at end of file Regards Primeballerina ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] why do i get this warning... no new line at end offile
Sometimes you need one more linespace after the end of the program. Try it -Original Message- From: primalfear 69 [mailto:[EMAIL PROTECTED] Sent: Wed 9/6/2006 2:36 PM To: tinyos-help Cc: Subject: [Tinyos-help] why do i get this warning... no new line at end offile hello everybody In many of my programs when i compile there is warning stating xyz.nc:9:2: warning: no new line at end of file Regards Primeballerina ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] PrintBigMsgs.java
hello I need one program Called PrintBigMsgs , if anyone cai help me feel free to answer back thanks ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] why do i get this warning... no new line at end of file
just place the cursor at the end of the file in any editor, insert a new line by pressing enter, save the file and end of the warning.primalfear 69 <[EMAIL PROTECTED]> escribió: hello everybody In many of my programs when i compile there is warning stating xyz.nc:9:2: warning: no new line at end of file Regards Primeballerina ___Tinyos-help mailing listTinyos-help@Millennium.Berkeley.EDUhttps://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help LLama Gratis a cualquier PC del Mundo.Llamadas a fijos y móviles desde 1 céntimo por minuto.http://es.voice.yahoo.com___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Documentation for tmote
[1] uses nesC 1.2.4. Upgrade to 1.2.7. -Joe On 9/6/06, Pablo Gil Montaño <[EMAIL PROTECTED]> wrote: The problem is that I am using Linux (Ubuntu 6.06) and I can't just install the .exe provided by moteiv. I've followed the guide in [1], and apart from the problem with the documentation, everything seems to be working. [1]: http://www.chadmetcalf.com/tinyos-1x-on-ubuntu/ Joe Polastre <[EMAIL PROTECTED]> escribió: Try installing Boomerang 2.0.4. It includes all the necessary tools and configuration for nesdoc to work correctly. -Joe On 9/5/06, Pablo Gil Montaño wrote: > Hi, > > I have a problem with nesdoc: everytime I try to generate documentation with > 'make tmote docs' I get the following error: > > nesc1: documentation system does not yet support generic components and > interfaces > make: *** [mot_docs_] Error 1 > > It happens with programs included in tinyos-1.x/apps that work allright on > my tmotes. If I try to generate documentation for another platform (e.g.: > make mica docs,here), it works perfectly. The problem is that I want to do > it with a platform-specific application which won't compile for either mica > or telos. Any suggestions? > > Bye! > > > > > LLama Gratis a cualquier PC del Mundo. > Llamadas a fijos y móviles desde 1 céntimo por minuto. > http://es.voice.yahoo.com > > > ___ > Tinyos-help mailing list > Tinyos-help@Millennium.Berkeley.EDU > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] power management with a telosb
Hello, I´m trying to put a telosb mote into the CPU sleep mode in order to power save. How can I do this ? Are there any examples ? And how does the power management works with a telosb ? Thank you in advance ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Swapping TOS message buffer Problem
Do you every initialize msg_buffer to point to an actual message?
You need something like:
TOS_Msg buffer;
TOS_MsgPtr msg_buffer;
command result_t StdControl.init() {
msg_buffer = &buffer;
}
On 9/6/06, Hari Hara Sudhan <[EMAIL PROTECTED]> wrote:
Hi every one,
I have a problem with swapping tos message buffer
I have to develop an application which has to receive a TOS Message through
air and then Broad cast the message.
The code is
TOS_MsgPtr msg_buff;
event TOS_MsgPtr ReceiveMsg.receive(TOS_MsgPtr m)
{
TOS_MsgPtr tmp=msg_buff;
msg_buff=m;
call Leds.greenToggle();
post SendData();
return tmp;
}
Basically im performing the buffer swap operation. But the problem is I can
receive only the first Message.
I think there is some problem with the buffer swap. Can any one please help
me regarding this.
Thanking you in advance
R.Hari Hara Sudhan
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Documentation for tmote
I've upgraded but I still have the same problem. The versions I'm using now are (ncc --version):ncc: 1.2alpha5nescc: 1.2.7aavr-gcc: avr-gcc (GCC) 3.4.3However, I have tried exactly the same under windows (with the tools provided by moteiv) and I can build the documentation for tmote without any problem. In linux, however, I cannot build documentation for tmote (although I can do it for the other platforms in those applications that do not depend on moteiv-specific components).Joe Polastre <[EMAIL PROTECTED]> escribió: [1] uses nesC 1.2.4. Upgrade to 1.2.7.-JoeOn 9/6/06, Pablo Gil Montaño <[EMAIL PROTECTED]> wrote:> The problem is that I am using Linux (Ubuntu 6.06) and I can't just install> the .exe provided by moteiv. I've followed the guide in [1], and apart from> the problem with the documentation, everything seems to be working.>> [1]: http://www.chadmetcalf.com/tinyos-1x-on-ubuntu/>>> Joe Polastre <[EMAIL PROTECTED]> escribió:> Try installing Boomerang 2.0.4. It includes all the necessary tools> and configuration for nesdoc to work correctly.>> -Joe>> On 9/5/06, Pablo Gil Montaño wrote:> > Hi,> >> > I have a problem with nesdoc: everytime I try to generate documentation> with> > 'make tmote docs' I get the following error:> >> > nesc1: documentation system does not yet support generic components and> > interfaces> > make: *** [mot_docs_] Error 1> >> > It happens with programs included in tinyos-1.x/apps that work allright on> > my tmotes. If I try to generate documentation for another platform (e.g.:> > make mica docs,here), it works perfectly. The problem is that I want to do> > it with a platform-specific application which won't compile for either> mica> > or telos. Any suggestions?> >> > Bye!> >> >> > > >> > LLama Gratis a cualquier PC del Mundo.> > Llamadas a fijos y móviles desde 1 céntimo por minuto.> > http://es.voice.yahoo.com> >> >> > ___> > Tinyos-help mailing list> > Tinyos-help@Millennium.Berkeley.EDU> >> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help> >> >> >> LLama Gratis a cualquier PC del Mundo.> Llamadas a fijos y móviles desde 1 céntimo por minuto.> http://es.voice.yahoo.com>> LLama Gratis a cualquier PC del Mundo.Llamadas a fijos y móviles desde 1 céntimo por minuto.http://es.voice.yahoo.com___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] power management with a telosb
I'm not sure, but I think that TinyOS automatically puts the CPU into sleep when there are no tasks to be done by the CPU.harun <[EMAIL PROTECTED]> escribió: Hello, I´m trying to put a telosb mote into the CPU sleep mode in order to power save. How can I do this ? Are there any examples ? And how does the power management works with a telosb ? Thank you in advance___Tinyos-help mailing listTinyos-help@Millennium.Berkeley.EDUhttps://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help LLama Gratis a cualquier PC del Mundo.Llamadas a fijos y móviles desde 1 céntimo por minuto.http://es.voice.yahoo.com___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Documentation for tmote
Have you installed tinyos-tools from tinyos-2.x/tools/ On 9/6/06, Pablo Gil Montaño <[EMAIL PROTECTED]> wrote: I've upgraded but I still have the same problem. The versions I'm using now are (ncc --version): ncc: 1.2alpha5 nescc: 1.2.7a avr-gcc: avr-gcc (GCC) 3.4.3 However, I have tried exactly the same under windows (with the tools provided by moteiv) and I can build the documentation for tmote without any problem. In linux, however, I cannot build documentation for tmote (although I can do it for the other platforms in those applications that do not depend on moteiv-specific components). Joe Polastre <[EMAIL PROTECTED]> escribió: [1] uses nesC 1.2.4. Upgrade to 1.2.7. -Joe On 9/6/06, Pablo Gil Montaño wrote: > The problem is that I am using Linux (Ubuntu 6.06) and I can't just install > the .exe provided by moteiv. I've followed the guide in [1], and apart from > the problem with the documentation, everything seems to be working. > > [1]: http://www.chadmetcalf.com/tinyos-1x-on-ubuntu/ > > > Joe Polastre escribió: > Try installing Boomerang 2.0.4. It includes all the necessary tools > and configuration for nesdoc to work correctly. > > -Joe > > On 9/5/06, Pablo Gil Montaño wrote: > > Hi, > > > > I have a problem with nesdoc: everytime I try to generate documentation > with > > 'make tmote docs' I get the following error: > > > > nesc1: documentation system does not yet support generic components and > > interfaces > > make: *** [mot_docs_] Error 1 > > > > It happens with programs included in tinyos-1.x/apps that work allright on > > my tmotes. If I try to generate documentation for another platform (e.g.: > > make mica docs,here), it works perfectly. The problem is that I want to do > > it with a platform-specific application which won't compile for either > mica > > or telos. Any suggestions? > > > > Bye! > > > > > > > > > > LLama Gratis a cualquier PC del Mundo. > > Llamadas a fijos y móviles desde 1 céntimo por minuto. > > http://es.voice.yahoo.com > > > > > > ___ > > Tinyos-help mailing list > > Tinyos-help@Millennium.Berkeley.EDU > > > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > > > > > > > > > > LLama Gratis a cualquier PC del Mundo. > Llamadas a fijos y móviles desde 1 céntimo por minuto. > http://es.voice.yahoo.com > > LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Make error for cygwin
On Sep 5, 2006, at 10:43 PM, Firas Daghmash wrote: Hi, after updating form version 1.x to 2.x, I am trying to compile one of the applications (Blink), either with make micaz sim or make micaz and ann error repoted and cygwin generate this error message: The procedure entry point __getreent could not be located in the dynamic link library cygwin1.dll Any help please It looks like you have installed the incorrect version of nesc. There are two versions for cygwin, depending on what cygwin install you have. The upgrade and install pages go into this. Phil ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Documentation for tmote
On Sep 6, 2006, at 8:13 AM, Joe Polastre wrote: Have you installed tinyos-tools from tinyos-2.x/tools/ Right. As I said before, the issue is that you have a 1.x toolchain (read: nesdoc), but for some reason the 1.x source tree has code in it that you need the 2.x toolchain for (read: generic components). In the short term, the solution is to install the 2.x toolchain, as Joe pointed out. In the long term, there either needs to be a 1.1 release that includes the 2.x tools or that code needs to be cut out of the RPMs. Phil ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Documentation for tmote
Phil, No, you only need to install the 2.x "tools", which really are nesC tools more than anything else and should be equally applied to anyone running nesC 1.2.x regardless of which TinyOS version they are running. He is using Boomerang, which has both 1.x and 2.x features, thus the need for nesC 1.2.x and the tools/src/ncc part of the tinyos 2.x toolchain (for lack of a better word) -Joe On 9/6/06, Philip Levis <[EMAIL PROTECTED]> wrote: On Sep 6, 2006, at 8:13 AM, Joe Polastre wrote: > Have you installed tinyos-tools from tinyos-2.x/tools/ > Right. As I said before, the issue is that you have a 1.x toolchain (read: nesdoc), but for some reason the 1.x source tree has code in it that you need the 2.x toolchain for (read: generic components). In the short term, the solution is to install the 2.x toolchain, as Joe pointed out. In the long term, there either needs to be a 1.1 release that includes the 2.x tools or that code needs to be cut out of the RPMs. Phil ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Errors in compiling NesC compiler.
Hi, I had following four errors while compiling nesc-1.2.7 package. When I gave make command, I got following errors in the end. Can anyone help me in removing them? ava Xvariables.java Xwire.java Xwiring.java Location.java: In class `net.tinyos.nesc.dump.xml.Location': Location.java: In method `net.tinyos.nesc.dump.xml.Location.decode(java.lang.String)': Location.java:54: error: Can't find method `matches()' in type `java.util.regex.Matcher'. if (!m.matches()) ^ Location.java:58: error: Can't find method `group(I)' in type `java.util.regex.Matcher'. String numS = m.group(1); ^ Location.java:59: error: Can't find method `group(I)' in type `java.util.regex.Matcher'. String instance = m.group(2); ^ Location.java:60: error: Can't find method `group(I)' in type `java.util.regex.Matcher'. String filename = m.group(3); ^ 4 errors make[7]: *** [CDefinition.class] Error 1 make[7]: Leaving directory `/home/sgupta/nesc-1.2.7a/tools/java/net/tinyos/nesc/dump/xml' make[6]: *** [all-recursive] Error 1 make[6]: Leaving directory `/home/sgupta/nesc-1.2.7a/tools/java/net/tinyos/nesc/dump' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/home/sgupta/nesc-1.2.7a/tools/java/net/tinyos/nesc' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/sgupta/nesc-1.2.7a/tools/java/net/tinyos' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/sgupta/nesc-1.2.7a/tools/java/net' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/sgupta/nesc-1.2.7a/tools/java' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/sgupta/nesc-1.2.7a/tools' make: *** [all-recursive] Error 1 Regards, Sumit ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Error Compiling Nucleus enabled application in Cygwin for PC platform
Hi, I installed nucleus on cygwin and I am having some problem while compiling an application /tinyos-1.x/apps/CntToLeds. I followed instructions given in Nucleus Manual but I am Getting following errors only when I am trying to compile it with PC platform. (make pc nucleus) but it compiled fine when I tried to compile it with platform mica2 (make mica2 nucleus). Please help me in sorting this problem. $ make pc nucleus mkdir -p build/pc ** Removing old generated files prior to compilation rm -f build/pc/AttrGenC.nc build/pc/EventGenC.nc rm -f build/pc/nucleusSchema.xml ** Generating nesC interface dump for CntToLeds on pc ncc -fsyntax-only -fnesc-dump=interfaces -fnesc-dump=tags -g -O0 -pthread -I%T/l ib/Counters -I -fnesc-nido-tosnodes=1000 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=pc -fnesc-cfile=build/pc/app.c -board=micasb -I/opt/tinyos-1 .x/tos/../beta/Drip -I/opt/tinyos-1.x/tos/../beta/Drain -I/opt/tinyos-1.x/tos/.. /contrib/nucleus/tos/lib/Nucleus -I%T/../beta/Drip -I%T/../beta/Drain -I%T/../co ntrib/nucleus/tos/lib/Nucleus -I%T/../contrib/nucleus/tos/lib/NucleusExamples -D IDENT_PROGRAM_NAME="CntToLeds" -DIDENT_PROGRAM_NAME_BYTES="67,110,116,84,111,76, 101,100,115,0" -DIDENT_USER_ID="Sumit" -DIDENT_USER_ID_BYTES="83,117,109,105,116 ,0" -DIDENT_HOSTNAME="superComp" -DIDENT_HOSTNAME_BYTES="115,117,112,101,114,67, 111,109,112,0" -DIDENT_USER_HASH=0x85ed13fbL -DIDENT_UNIX_TIME=0x44fe76b3L CntTo Leds.nc -lm > build/pc/nesc.xml In file included from /opt/tinyos-1.x/tos/platform/pc/hardware.h:43, from /opt/tinyos-1.x/tos/system/tos.h:144: /opt/tinyos-1.x/tos/platform/pc/nido.h:63: `TOSH_NUM_NODES' undeclared here (not in a function) /opt/tinyos-1.x/tos/platform/pc/nido.h:63: enumerator value for `TOSNODES' not i nteger constant In file included from /opt/tinyos-1.x/tos/platform/pc/hardware.h:110, from /opt/tinyos-1.x/tos/system/tos.h:144: /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_set_interval': /opt/tinyos-1.x/tos/platform/pc/hpl.c:65: warning: implicit declaration of funct ion `event_clocktick_invalidate' /opt/tinyos-1.x/tos/platform/pc/hpl.c:80: warning: implicit declaration of funct ion `event_clocktick_create' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_set_rate': /opt/tinyos-1.x/tos/platform/pc/hpl.c:94: warning: implicit declaration of funct ion `event_clocktick_invalidate' /opt/tinyos-1.x/tos/platform/pc/hpl.c:105: warning: implicit declaration of func tion `event_clocktick_create' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_int_disable': /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: (Each undeclared identifier is report ed only once /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: for each function it appears in.) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_int_enable': /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_clocktick_handle': /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_clocktick_create': /opt/tinyos-1.x/tos/platform/pc/hpl.c:194: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:194: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_clocktick_invalidate': /opt/tinyos-1.x/tos/platform/pc/hpl.c:212: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:212: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_adc_sample_port': /opt/tinyos-1.x/tos/platform/pc/hpl.c:248: warning: implicit declaration of func tion `event_adc_create' /opt/tinyos-1.x/tos/platform/pc/hpl.c:253: warning: implicit declaration of func tion `event_adc_update' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_adc_sample_again': /opt/tinyos-1.x/tos/platform/pc/hpl.c:263: `adc_tick_data_t' undeclared (first u se in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:263: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_adc_sample_stop': /opt/tinyos-1.x/tos/platform/pc/hpl.c:274: `adc_tick_data_t' undeclared (first u se in this function)
[Tinyos-help] Error Compiling Nucleus enabled application in Cygwin for PC platform
Hi, I installed nucleus on cygwin and I am having some problem while compiling an application /tinyos-1.x/apps/CntToLeds. I followed instructions given in Nucleus Manual but I am Getting following errors only when I am trying to compile it with PC platform. (make pc nucleus) but it compiled fine when I tried to compile it with platform mica2 (make mica2 nucleus). Also, I noticed tht I couldnot even compile for normal pc platform without including nucleus (i.e. make pc). It gave same errors but only related to nido.h. Please help as I need to make it run to proceed further in my project. Please help me in sorting this problem. $ make pc nucleus mkdir -p build/pc ** Removing old generated files prior to compilation rm -f build/pc/AttrGenC.nc build/pc/EventGenC.nc rm -f build/pc/nucleusSchema.xml ** Generating nesC interface dump for CntToLeds on pc ncc -fsyntax-only -fnesc-dump=interfaces -fnesc-dump=tags -g -O0 -pthread -I%T/l ib/Counters -I -fnesc-nido-tosnodes=1000 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=pc -fnesc-cfile=build/pc/app.c -board=micasb -I/opt/tinyos-1 .x/tos/../beta/Drip -I/opt/tinyos-1.x/tos/../beta/Drain -I/opt/tinyos-1.x/tos/.. /contrib/nucleus/tos/lib/Nucleus -I%T/../beta/Drip -I%T/../beta/Drain -I%T/../co ntrib/nucleus/tos/lib/Nucleus -I%T/../contrib/nucleus/tos/lib/NucleusExamples -D IDENT_PROGRAM_NAME="CntToLeds" -DIDENT_PROGRAM_NAME_BYTES="67,110,116,84,111,76, 101,100,115,0" -DIDENT_USER_ID="Sumit" -DIDENT_USER_ID_BYTES="83,117,109,105,116 ,0" -DIDENT_HOSTNAME="superComp" -DIDENT_HOSTNAME_BYTES="115,117,112,101,114,67, 111,109,112,0" -DIDENT_USER_HASH=0x85ed13fbL -DIDENT_UNIX_TIME=0x44fe76b3L CntTo Leds.nc -lm > build/pc/nesc.xml In file included from /opt/tinyos-1.x/tos/platform/pc/hardware.h:43, from /opt/tinyos-1.x/tos/system/tos.h:144: /opt/tinyos-1.x/tos/platform/pc/nido.h:63: `TOSH_NUM_NODES' undeclared here (not in a function) /opt/tinyos-1.x/tos/platform/pc/nido.h:63: enumerator value for `TOSNODES' not i nteger constant In file included from /opt/tinyos-1.x/tos/platform/pc/hardware.h:110, from /opt/tinyos-1.x/tos/system/tos.h:144: /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_set_interval': /opt/tinyos-1.x/tos/platform/pc/hpl.c:65: warning: implicit declaration of funct ion `event_clocktick_invalidate' /opt/tinyos-1.x/tos/platform/pc/hpl.c:80: warning: implicit declaration of funct ion `event_clocktick_create' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_set_rate': /opt/tinyos-1.x/tos/platform/pc/hpl.c:94: warning: implicit declaration of funct ion `event_clocktick_invalidate' /opt/tinyos-1.x/tos/platform/pc/hpl.c:105: warning: implicit declaration of func tion `event_clocktick_create' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_int_disable': /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: (Each undeclared identifier is report ed only once /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: for each function it appears in.) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_int_enable': /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_clocktick_handle': /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_clocktick_create': /opt/tinyos-1.x/tos/platform/pc/hpl.c:194: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:194: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_clocktick_invalidate': /opt/tinyos-1.x/tos/platform/pc/hpl.c:212: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:212: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_adc_sample_port': /opt/tinyos-1.x/tos/platform/pc/hpl.c:248: warning: implicit declaration of func tion `event_adc_create' /opt/tinyos-1.x/tos/platform/pc/hpl.c:253: warning: implicit declaration of func tion `event_adc_update' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_adc_sample_again': /opt/tinyos-1.x/tos/platform/pc/hpl.c:263: `adc_tick_data_t' undeclared (first u se in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:26
[Tinyos-help] Re: Error Compiling Nucleus enabled application in Cygwin for PC platform
I just want to add that before this i just installed nesC compileter, Simple::XML and updated the CVS tree for TinyOS. and I before doing all this I could compile normal applications for all platforms but now it's not working for PC platform at all. Please advice. SumitOn 9/6/06, Sumit Gupta <[EMAIL PROTECTED]> wrote: Hi, I installed nucleus on cygwin and I am having some problem while compiling an application /tinyos-1.x/apps/CntToLeds. I followed instructions given in Nucleus Manual but I am Getting following errors only when I am trying to compile it with PC platform. (make pc nucleus) but it compiled fine when I tried to compile it with platform mica2 (make mica2 nucleus). Also, I noticed tht I couldnot even compile for normal pc platform without including nucleus (i.e. make pc). It gave same errors but only related to nido.h. Please help as I need to make it run to proceed further in my project. Please help me in sorting this problem. $ make pc nucleus mkdir -p build/pc ** Removing old generated files prior to compilation rm -f build/pc/AttrGenC.nc build/pc/EventGenC.nc rm -f build/pc/nucleusSchema.xml ** Generating nesC interface dump for CntToLeds on pc ncc -fsyntax-only -fnesc-dump=interfaces -fnesc-dump=tags -g -O0 -pthread -I%T/l ib/Counters -I -fnesc-nido-tosnodes=1000 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=pc -fnesc-cfile=build/pc/app.c -board=micasb -I/opt/tinyos-1 .x/tos/../beta/Drip -I/opt/tinyos-1.x/tos/../beta/Drain -I/opt/tinyos-1.x/tos/.. /contrib/nucleus/tos/lib/Nucleus -I%T/../beta/Drip -I%T/../beta/Drain -I%T/../co ntrib/nucleus/tos/lib/Nucleus -I%T/../contrib/nucleus/tos/lib/NucleusExamples -D IDENT_PROGRAM_NAME="CntToLeds" -DIDENT_PROGRAM_NAME_BYTES="67,110,116,84,111,76, 101,100,115,0" -DIDENT_USER_ID="Sumit" -DIDENT_USER_ID_BYTES="83,117,109,105,116 ,0" -DIDENT_HOSTNAME="superComp" -DIDENT_HOSTNAME_BYTES="115,117,112,101,114,67, 111,109,112,0" -DIDENT_USER_HASH=0x85ed13fbL -DIDENT_UNIX_TIME=0x44fe76b3L CntTo Leds.nc -lm > build/pc/nesc.xml In file included from /opt/tinyos-1.x/tos/platform/pc/hardware.h:43, from /opt/tinyos-1.x/tos/system/tos.h:144: /opt/tinyos-1.x/tos/platform/pc/nido.h:63: `TOSH_NUM_NODES' undeclared here (not in a function) /opt/tinyos-1.x/tos/platform/pc/nido.h:63: enumerator value for `TOSNODES' not i nteger constant In file included from /opt/tinyos-1.x/tos/platform/pc/hardware.h:110, from /opt/tinyos-1.x/tos/system/tos.h:144: /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_set_interval': /opt/tinyos-1.x/tos/platform/pc/hpl.c:65: warning: implicit declaration of funct ion `event_clocktick_invalidate' /opt/tinyos-1.x/tos/platform/pc/hpl.c:80: warning: implicit declaration of funct ion `event_clocktick_create' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_set_rate': /opt/tinyos-1.x/tos/platform/pc/hpl.c:94: warning: implicit declaration of funct ion `event_clocktick_invalidate' /opt/tinyos-1.x/tos/platform/pc/hpl.c:105: warning: implicit declaration of func tion `event_clocktick_create' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_int_disable': /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: (Each undeclared identifier is report ed only once /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: for each function it appears in.) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:138: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_clock_int_enable': /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:145: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_clocktick_handle': /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:160: syntax error before `)' /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_clocktick_create': /opt/tinyos-1.x/tos/platform/pc/hpl.c:194: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:194: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `event_clocktick_invalidate': /opt/tinyos-1.x/tos/platform/pc/hpl.c:212: `clock_tick_data_t' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c:212: `data' undeclared (first use in this function) /opt/tinyos-1.x/tos/platform/pc/hpl.c: In function `TOSH_adc_sample_port': /opt/tinyos-1.x/tos/platform/pc/hpl.c:248: warning: implicit declaration of func tion `event_adc_create' /o
[Tinyos-help] Debug statements in Tossim 2.x
Hi all, I am working on Tinyos 2.x. In Chapter 11 of tinyos2.x tutorial for TOSSIM, I get the debug statements of the RadioCountToLeds application, when simulated using python, but i dont get any debug statements when i use a C++ script. Can anyone help me in this issue ?? Thanks and Regards,Venkatesh.S ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Errors in compiling NesC compiler.
On 9/5/06, Sumit Gupta <[EMAIL PROTECTED]> wrote: Hi, I had following four errors while compiling nesc-1.2.7 package. When I gave make command, I got following errors in the end. Can anyone help me in removing them? ava Xvariables.java Xwire.java Xwiring.java Location.java: In class `net.tinyos.nesc.dump.xml.Location': Location.java: In method `net.tinyos.nesc.dump.xml.Location.decode(java.lang.String)': Location.java:54: error: Can't find method `matches()' in type `java.util.regex.Matcher'. if (!m.matches()) ^ Location.java:58: error: Can't find method `group(I)' in type `java.util.regex.Matcher'. String numS = m.group(1); ^ Location.java:59: error: Can't find method `group(I)' in type `java.util.regex.Matcher'. String instance = m.group(2); ^ Location.java:60: error: Can't find method `group(I)' in type `java.util.regex.Matcher'. String filename = m.group(3); ^ 4 errors These are standard methods of the java.util.regex.Matcher class. Offhand, you either don't have Java 1.4 (or later), or you have an incomplete java class library. David Gay ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] how to measure power consumption in tmote sky
At this point, the best way is probably hook up a small shunt resistor (1-50Ohm depending on your load and oscilloscope accuracy) in series between the battery and the board, either on the ground side or the Vdd side. Then use an oscilloscope to measure it. Also pay attention to the waveform you capture, if you see relatively high current, you want to swap the resistor for a smaller value, and vice versa. What you might get at the end is two sets of current traces corresponding to the two resistor values. You can combine them by using the smaller resistor trace for the bigger current and larger res for the smaller current (and scale appropriately). Multiply by the voltage to get the power. Integrate and divide to get average power (feed to matlab or some sort). If oscilloscope has low resolution, you will need to build some sort of amplifier circuit. -Fred On Sep 5, 2006, at 3:14 AM, 박판근 wrote: Hi.i'm working with tmote sky and i want to measure the power that the board consumes, Do you have some tools ? or Could you give advices to measure power consumption? thanks a lot ___ 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] Fuse bits and power management
Back in 2004, This was posted to the tinyos-users mailing list.> Sometimes -- for a wide range of reasons -- the fuse bits become set improperly. This can lead to really weird behavior which is very hard to debug or figure out[1]. Among other > things, it leads to lots of cries for help on tinyos-help. Resetting them to the proper values every time removes the problem and saves a lot of people's time. > Phil > [1] E.g., seeing timer skew/missed timers with power management when the wakeup latency fuse is set incorrectly. Some motes work fine, others don't...I am experiencing these symptoms (timer skew and missed timers) when using power management; however, I haven't been able to find anywhere how to set the wakeup latency fuse or what it should be set to. I read the fuse bits from my mote (mica2dot). They are low = 0xffhigh = 0xd8extended = 0xffIs this incorrect. I tried to looking at the Atmega128's data sheet, but it was unclear to me what values I should be using. Any help would be great.Thanks, Jacob Sorber ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Measuring end to end delay
Hello everyone. I want to measure end to end delay using sky tmote. I will sychronise nodes, then source node sends local time to destination node. So, destination can get end to end delay using difference local time in receiver and received time value. Is this proper way to measure end to end delay? When nodes send packet, I add local time (4 bytes) on packet using TimerC.LocalTime(). But when i checked the local time at the receiver, the local time was sometimes decreased. For instance, the local time (4 bytes) change from [ 22 00 BD 00 ] to [22 00 02 01]. Could somebody explain this one? How can i change these 4 byte to second ? Do they use tick unit (32768tick = 1sec)? Thanks your very much. Best regards. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] ASSEMBLER ERROR, make micaz sim, McuSleepC
Good evening, When I try to use McuSleepC and Tossim I obtain the following compilation error: /tmp/ccTyOEVj.s: Assembler messages: /tmp/ccTyOEVj.s:34478: Error: no such instruction: `sleep' I haven't any problem when I try to compile it for micaz platform, instead. Have a good night ! bye. -- Mutui a tassi scontati da 30 banche. Richiedi online e risparmia...Servizio gratuito. http://click.libero.it/mutuionline6 ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] How to program mica2 (Thermal)
Hi,I am involved in an assignment to program the mica2 sensors to send back a message once a thermal reading of 35C and 40C is detected. Can this program be written in nesC? Please give some pointers in order to create this program and also errors to be vary of as I am still in the beginning phase. Thanks a lot. Rgds,Sun. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Interrupts and async events question
Hello everybody, In tinyos, usually, an interrupt signals an async event. When an interrupt routine is executed, all the interrupts are masked and cannot interrupt the current interrupt routine. If this interrupt routine jumps to a signalled event, are the other interrupts disabled until this event (and every routine called from this event) finish it execution and return the control to the interrupt routine? Thanks, José __ Preguntá. Respondé. Descubrí. Todo lo que querías saber, y lo que ni imaginabas, está en Yahoo! Respuestas (Beta). ¡Probalo ya! http://www.yahoo.com.ar/respuestas ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Questions regarding concurrency in TinyOS 1.x
(1) Inside the tinyOS event-driven concurrency system, does the atomic section (including called function) occupy the CPU
and run until completion, such that even an async event (interrupt) can not
preempt it? -- even assume the protected variables has nothing related with the
async event functions?(I just read app.c, seems like that's the
way how __nesc_atomic_start implemented, please confirm!)static inline
__nesc_atomic_t __nesc_atomic_start(void ){ __nesc_atomic_t result
= are_interrupts_enabled();#line 222
__nesc_disable_interrupt(); return result;}(2) I have
tried to compare SurgeM.nc with app.c under build/telosb. I notice this "atomic" section is not atomic in app.c --
is this a bug? Or when the
atomic keyword will be ignored? async event
result_t Sensor.dataReady(uint16_t data)
{ atomic { if (!gfSendBusy)
{ gfSendBusy =
TRUE;
gSensorData = data; post
SendData(); }
} return SUCCESS; }
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] Interrupts and async events question
It is a great question - I am looking at build/telosb/app.c and has a complementary question: I notice an async event is actually implemented by __attribute((interrupt(xx))) function: void __attribute((wakeup)) __attribute((interrupt(14))) sig_ADC_VECTOR(void) Can another interuption interupt this routine? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jose m Sent: Wednesday, September 06, 2006 1:22 PM To: tinyos-help@Millennium.Berkeley.EDU Subject: [Tinyos-help] Interrupts and async events question Hello everybody, In tinyos, usually, an interrupt signals an async event. When an interrupt routine is executed, all the interrupts are masked and cannot interrupt the current interrupt routine. If this interrupt routine jumps to a signalled event, are the other interrupts disabled until this event (and every routine called from this event) finish it execution and return the control to the interrupt routine? Thanks, José __ Preguntá. Respondé. Descubrí. Todo lo que querías saber, y lo que ni imaginabas, está en Yahoo! Respuestas (Beta). ¡Probalo ya! http://www.yahoo.com.ar/respuestas ___ 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] Questions regarding concurrency in TinyOS 1.x
Interrupts are disabled within async{} blocks. Therefore, no events can be fired, and nothing will happen except for what's in your async code (unless the batteries die or your mote falls into a pool of molten lava).
- ConorOn 9/6/06, Adam <[EMAIL PROTECTED]> wrote:
(1) Inside the tinyOS event-driven concurrency system, does the atomic section (including called function) occupy the CPU
and run until completion, such that even an async event (interrupt) can not
preempt it? -- even assume the protected variables has nothing related with the
async event functions?(I just read app.c, seems like that's the
way how __nesc_atomic_start implemented, please confirm!)static inline
__nesc_atomic_t __nesc_atomic_start(void ){ __nesc_atomic_t result
= are_interrupts_enabled();#line 222
__nesc_disable_interrupt(); return result;}(2) I have
tried to compare SurgeM.nc with app.c under build/telosb. I notice this "atomic" section is not atomic in app.c --
is this a bug? Or when the
atomic keyword will be ignored? async event
result_t Sensor.dataReady(uint16_t data)
{ atomic { if (!gfSendBusy)
{ gfSendBusy =
TRUE;
gSensorData = data; post
SendData(); }
} return SUCCESS; }
___Tinyos-help mailing listTinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
-- "Thought is only a flash in the middle of a long night, but the flash that means everything."- Poincaré-=-=-=-=-=-=-=-=-I'm going to run the Houston Marathon, but finishing's not my only goal: help me raise money for cancer research!
http://www.active.com/donate/tnttxgc/tnttxgcCToddThanks!
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Interrupts and async events question
No. The only way to break out of the async nature of interrupt handlers (and functions called by them) is to post a task, thus allowing the synchronous interrupt-handling call tree to terminate. - C On 9/6/06, Adam <[EMAIL PROTECTED]> wrote: It is a great question - I am looking at build/telosb/app.c and has acomplementary question:I notice an async event is actually implemented by__attribute((interrupt(xx))) function:void __attribute((wakeup)) __attribute((interrupt(14))) sig_ADC_VECTOR(void)Can another interuption interupt this routine?-Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of jose mSent: Wednesday, September 06, 2006 1:22 PMTo: tinyos-help@Millennium.Berkeley.EDUSubject: [Tinyos-help] Interrupts and async events questionHello everybody,In tinyos, usually, an interrupt signals an async event. When an interruptroutine is executed, all the interrupts are masked and cannot interrupt the current interrupt routine. If this interrupt routine jumps to a signalledevent, are the other interrupts disabled until this event (and every routinecalled from thisevent) finish it execution and return the control to the interrupt routine? Thanks,José__Preguntá. Respondé. Descubrí.Todo lo que querías saber, y lo que ni imaginabas, está en Yahoo! Respuestas(Beta). ¡Probalo ya!http://www.yahoo.com.ar/respuestas___Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDUhttps://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help___ Tinyos-help mailing listTinyos-help@Millennium.Berkeley.EDUhttps://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- "Thought is only a flash in the middle of a long night, but the flash that means everything."- Poincaré-=-=-=-=-=-=-=-=-I'm going to run the Houston Marathon, but finishing's not my only goal: help me raise money for cancer research! http://www.active.com/donate/tnttxgc/tnttxgcCToddThanks! ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problem in Sourceforge CVS tree update
Regarding earlier problem, I have noticed that it appeared after I update my tinyos Tree. By giving following command: cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/tinyos co -P tinyos-1.x Well now tree is updated and a lot of file has been replaced and/or stored. Now I am wondering which file I should fix. The problems are mainly for compling applications in pc platform. Hope to hear back. Regards, Sumit ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Questions regarding concurrency in TinyOS 1.x
On Sep 6, 2006, at 10:14 PM, Conor Todd wrote:
Interrupts are disabled within async{} blocks. Therefore, no
events can be fired, and nothing will happen except for what's in
your async code (unless the batteries die or your mote falls into a
pool of molten lava).
- Conor
You mean atomic{} blocks, right?
In terms of language semantics, the promise is that code within an
atomic block will run atomically. In terms of implementations on
simple microcontrollers, this often means disabling all interrupts.
With interrupt priority levels one could, however, use some
intelligent compiler tricks to determine what IPL to disable. E.g.,
if the variables in the atomic section are only accessed by interrupt
priorities 1 and 3, you could set the IPL at 3.
Phil
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Make error for cygwin
I've followed the same instructions in upgrade page, and after completed successfully, I've tried tos-check-env which also passed without errors or warnings. Then I've followed the check for ncc version in lesson 1 of the new tutorial and issue the same commands for updating the ncc path .. Can you please suggest exactly what should I do? installing all from scratch or make some modifications, which I pref ere ... > On Sep 5, 2006, at 10:43 PM, Firas Daghmash wrote: > >> >> Hi, >> >> after updating form version 1.x to 2.x, I am trying to compile one >> of the >> applications (Blink), either with make micaz sim or make micaz and ann >> error repoted and cygwin generate this error message: >> >> The procedure entry point __getreent could not be located in the >> dynamic >> link library cygwin1.dll >> >> Any help please > > It looks like you have installed the incorrect version of nesc. There > are two versions for cygwin, depending on what cygwin install you > have. The upgrade and install pages go into this. > > Phil > -- Firas Daghmash Network Administrator/Instructor Cisco Netowrking Academy Queen Noor Civil Aviation Technical College www.qnac.edu.jo Tel. +962-6-4892484 Ext. 177 Mobile:+962-79-5977826 P.O.Box 341020 Zip code 11134 Amman- Jordan ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
