Hi all,
Sorry, we have found the error. It was a hardware problem.
Thanks,
Andres
From: "Andres Aberasturi" <[EMAIL PROTECTED]>
To: tinyos-help@Millennium.Berkeley.EDU
Subject: [Tinyos-help] TinyOS 1.1.15 Timer help
Date: Wed, 05 Jul 2006 08:28:45 +0200
Hi all,
We are working with micaz
Hi,
by the way I'm interesting about tinyos 2.x
you've had wrote:
"Interrupts, however, can preempt tasks. All code that an interrupt handler
calls must be async. The hardware takes care of pushing some context on the
stack, and the compiler takes care of spilling registers to memory. The
questio
Is it possible to port tinyos on 8051
microcontroller??
if yes then how it goes
plzz reply i would be very thankful
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_
Hi!
On Tue, 4 Jul 2006, Avinash Sridharan wrote:
> The ncc --version output is :
> ncc: 1.2
> nescc: 1.2.2
> gcc: gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)
> Copyright (C) 2005 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty;
Hi all,
is there a fast and easy way to receive all messages arriving from the
network?
Because if i only use
event TOS_MsgPtr ReceiveDataNC.receive(TOS_MsgPtr m){
Datagram *dg=(Datagram *)m->data;
[..]
.
.
[..]
return m;
}
i see in TOSSIM that some packets too close with each other (i
Hi all,
i'm working on Tmote Sky.
I experienced some event loss in my application (or i think this is the problem..) and i want to increment the queue size.
I have a master that polls many slave in a round robin fashion and
after a few minutes the timer that rules master's polling seems to fail.
(i
Gaba,
The link below is the working group of tinyos 8051. Maybe you would
find something helpful
http://www.tinyos.net/scoop/special/working_group_tinyos_8051
--
Alex Junyan Ma
A804 Aviation Building
Northwestern Polytechnical University
Xi'an, Shaanxi, China P.R.
EMAIL: alexmajy at gmail dot
For some reason it isn't finding %T/lib/MultiHopLQI
On 7/4/06, Ming <[EMAIL PROTECTED]> wrote:
Hi everyone
When I try to compile the SurgeTelos on the Telos verB, I get the following
error. How can I solve it?
> # make telosb
> mkdir -p build/telosb
> compiling Surge to a telosb binary
> n
If you use Boomerang, then you use the new TinyOS 2.x task queue that
doesn't have this problem. The 1.x task queue still has the
possibility of overflowing.
-Joe
On 7/5/06, giovanni gamba <[EMAIL PROTECTED]> wrote:
Hi all,
i'm working on Tmote Sky.
I experienced some event loss in my applic
Friends,We have some source code & algorithms from our experiments on MICA2 moteusing TinyOS. People working on source coding in WSN can benefit.Source is licensed under GPL. Check with the website for code & docs.http://students.uta.edu/mx/mxa6471/WSNSrcCoding/Thanks for help on the TinyOS lists
Hello All,
I am trying to simulate sensing events in TOSSIM. As an example:
Consider 10 nodes deployed. Each node is sensing for sound. One node at
random will start chirping. The neighboring nodes sensing this event
send out a message announcing the sound detected. I dont know how to
generate the
On Jul 5, 2006, at 6:44 AM, gagan gaba wrote:
Is it possible to port tinyos on 8051
microcontroller??
if yes then how it goes
plzz reply i would be very thankful
Please read TEP 121.
Phil
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berk
On Jul 5, 2006, at 2:24 AM, Frigging wrote:
Hi,
by the way I'm interesting about tinyos 2.x
you've had wrote:
"Interrupts, however, can preempt tasks. All code that an interrupt
handler
calls must be async. The hardware takes care of pushing some
context on the
stack, and the compiler take
On 7/5/06, Razvan Musaloiu-E. <[EMAIL PROTECTED]> wrote:
Hi!
On Tue, 4 Jul 2006, Avinash Sridharan wrote:
> The ncc --version output is :
> ncc: 1.2
> nescc: 1.2.2
> gcc: gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8)
> Copyright (C) 2005 Free Software Foundation, Inc.
> This is free software; see
I notice GenericComm has this following function:
TOS_MsgPtr handleReceived(TOS_MsgPtr packet) __attribute__ ((C,
spontaneous))
I am curious that what's the difference if we use __attribute__ ((C,
spontaneous)) or not to define an global function? I have written several
global function without u
export TOSMAKE_PATH=/opt/tinyos-1.x/contrib/moteiv/tools/make
Should solve this.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Joe
Polastre
Sent: Wednesday, July 05, 2006 9:19 AM
To: Ming
Cc: tinyos-help@Millennium.Berkeley.EDU
Subject: Re: [TinyOS-help
On Jul 5, 2006, at 11:24 AM, Adam wrote:
I notice GenericComm has this following function:
TOS_MsgPtr handleReceived(TOS_MsgPtr packet) __attribute__ ((C,
spontaneous))
I am curious that what's the difference if we use __attribute__ ((C,
spontaneous)) or not to define an global function? I ha
Hello all,
My mica2 application requires a lot of RAM for radio
messages. The mote is connected to a GPS, and must
initialize this one. For initialization purposes, the
system sends to the GPS a NMEA protocol ASCII string.
This string never changes, so is a constant string,
and needs several bytes
Thanks. Does this mean it is recommended to add this attibute to all global
C functions? For my case, I write some buffer manage functions -- multiple
modules can call those functions -- I added "atomic" in each of those
functions, will it be removed by compiler (since atomic is not a c KEYWORD)
i
Again, if these functions will be called inside nesC code only, is it not
necessary ? -- I just wan to confirm it is not related to byte order or
parameter order issues -- like between C and Fortran.
-Original Message-
From: Adam [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 05, 2006 1
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:tinyos-help-
> [EMAIL PROTECTED] On Behalf Of Philip Levis
> Sent: Thursday, June 29, 2006 14:06
> To: [EMAIL PROTECTED]
> Cc: tinyos-help@Millennium.Berkeley.EDU
> Subject: RE: [Tinyos-help] Mate and send_lqi on Telosb/tmote
>
> On
Hi
I recently bought some Moteiv Invent motes.
After doing a clean install from the provided CD, I tried to compile the Ditto program in /invent/Ditto
However, I get a very long error message starting with
Error : no such architecture: `msp430x1611'
Error: jucnk at end of line, first unre
On Wed, 2006-07-05 at 14:53, Ben Kelley wrote:
>
> I finally got it to work, I have no idea how.
>
> I ended up going with
>
> typedef struct MateRouteMsg {
> uint16_t sourceaddr;
> uint16_t originaddr;
> int16_t seqno;
> int16_t originseqno;
> uint16_t hopcount;
> uint8_t data[];
>
Thanks for all your help. There is still one thing which does not let me go on working.
I understand that any async function can preemp other async function and task (from your manual).
My question is the follow:
when an async function is interrupt because an other async function comes, is it corr
On Wed, 2006-07-05 at 15:40, frigging frigging wrote:
> Thanks for all your help. There is still one thing which does not let
> me go on working.
> I understand that any async function can preemp other async function
> and task (from your manual).
> My question is the follow:
> when an async funct
Philip Levis wrote:
On Jul 5, 2006, at 11:24 AM, Adam wrote:
I notice GenericComm has this following function:
TOS_MsgPtr handleReceived(TOS_MsgPtr packet) __attribute__ ((C,
spontaneous))
I am curious that what's the difference if we use __attribute__ ((C,
spontaneous)) or not to define an
On 7/5/06, Adam <[EMAIL PROTECTED]> wrote:
Thanks. Does this mean it is recommended to add this attibute to all global
C functions? For my case, I write some buffer manage functions -- multiple
modules can call those functions -- I added "atomic" in each of those
functions, will it be removed by
Hi all,
I found that TOSSIM Mica1 and Mica2 radios lose packets in a particular
scenario even when there is no lossy model used. The scenario is one
mote broadcasts a request message and all the receivers sends a reply
message to the sender. In this scenario, some of the reply messages sent
b
1. Naturally, "send done (success)" does not imply "receive (crc = pass)".
What you see is not a bug.
2. The lossy model applies bit errors probabilistically (emulating a lossy
PHYSICAL channel) outside of any MAC issues you might introduce in your
simulation by having/allowing >=2 nodes transmit
Thank you for you kind reply.I have tried to export TOSMARK_PATH, but the problem is still appear. Are there any other problem cause the Error?On 7/5/06,
Adam <[EMAIL PROTECTED]> wrote:export TOSMAKE_PATH=/opt/tinyos-
1.x/contrib/moteiv/tools/makeShould solve this.-Original Message-From: [
Hi,
In tinyos-2.x to include a header file, at certain places we use includes, while at other places we use #include.
Is there any difference between the two? Are there any scenarios or conditions, where we should use one over the other
thanks,
Manju.
_
Hi,I'm confused with the following code from enqueue_receive_event from UscGainInterfaerenceModelC.nc. The condition at label 1 is understandable. It checks if the power is large enough against the destination noise plus all the other transmissions to the destination. What I don't understand is the
Hi folks,
Ravi, You're right man!
Although I use the boomerang distribution, the UserButtonM is a bit different.So I use the MSP430InterruptC to receive interrupt from the hard-button instead and "the event preempt that infinite task" now.
Thanks,
Chalermphol
On 7/5/06, Ravi Prasad <[EMAIL P
That error seems to indicate that TOS_MSG
somehow has been defined twice, but they don’t match.
Have you modified these files at all?
I don’t think either TOSMAKE_PATH
matters, either the moteiv one, if you have boomerang installed or just plain
tinyos, without one.
What version
On Jul 5, 2006, at 6:55 PM, Manju wrote:
Hi,
In tinyos-2.x to include a header file, at certain places we use
includes, while at other places we use #include.
Is there any difference between the two? Are there any scenarios or
conditions, where we should use one over the other
The basic
On Jul 5, 2006, at 8:08 PM, Liu Haibin wrote:
Hi,
I'm confused with the following code from enqueue_receive_event
from UscGainInterfaerenceModelC.nc. The condition at label 1 is
understandable. It checks if the power is large enough against the
destination noise plus all the other transm
But I still don't understand why there is a difference between first case (label 1) and second case (label 2)? label 2 is without sensitivity and other transmissions compared with label 1.Can I say that label 1 is to receive a packet, but label 2 is to detect preamble? So does it mean that power le
On Jul 5, 2006, at 10:55 PM, Liu Haibin wrote:
But I still don't understand why there is a difference between
first case (label 1) and second case (label 2)? label 2 is without
sensitivity and other transmissions compared with label 1.
Can I say that label 1 is to receive a packet, but labe
38 matches
Mail list logo
