Okay its a mess. Fortunately not too many folks have been running into
this.Or they have given up :-(
It isn't so much a problem with the msp430 toolchain but rather a problem
with how the new toolchain was deployed. I won't go into that. No point.
Here is the current situation
Hi, i'm new in TinyOS programming.
I'm facing problem when i casting a variable.
I have different types of messages. When the end point receives each
message it has to check the type of message to decide a response.
I'm using UDP.recvfrom and cast the variable void *data to a messag_hdr
where i
Hi all,
I'm working on tinyos2.x and I want to add some information(message delay) to
the acknowledgement packet. Is there any way to add a field to the ack
packet?If not, I have to implement my own ACK, in this case the Ack DSN should
be the same as the message.I tried to send the Ack in the
any body know why I get this problem.
xubuntos@xubuntos-tinyos:/opt/tinyos-2.x-contrib/hurray2x/apps/AssociationExample$
make telosb install
mkdir -p build/telosb
compiling AssociationExample to a telosb binary
ncc -o build/telosb/main.exe -Os -O
-I/opt/tinyos-2.1.0/tos/ieee802154/includes
On Wed, Mar 21, 2012 at 10:40 AM, Yusnaidi Md Yusof
yusnaid...@gmail.com wrote:
Hi,
I am a bit confuse. I am not really clear how a call to
CtpInfo.setNeighborCongested(from, congested) can set the neighbor as
congested (in the BeaconReceive.receive() event in CtpRoutingEngineP)?,
because I
On Tue, Apr 3, 2012 at 11:15 AM, Gary Lee gary.lee1...@gmail.com wrote:
Hi,
Trickle protocol is used for data dissemination. The original Trickle paper
assumes sensor nodes are always on.
I am wondering is there some paper/TinyOS implementation that is about
Trickle on low-duty-cycled
