Hi,
I'm wondering if TinyOS-1.x provides split-phase bus arbitration like in
2.x? It doesn't seem to be a good idea to do busy bus polling.
Thanks,
Sha
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
Hello everyone, I am experimenting problems with the packet structure. I'm
using the TinyOS1.x operating system.The TOS_Msg struc is intact, but i've
changed the xsensor header a bit. However i cannot recognized some bytes that
my programm is listening (and shouldn't be received). They are
The architecture (including arbiters, oer managers, etc.) that exists
in t2 for building drivers in a way that allows for bus arbitration
does NOT exist in tinyos 1, but if I remmeber correctly, there is an
interface called (surprisingly enough) BusArbitration that allows you
to do something
Hi!
I'm trying to communicate with a i2c eeprom with a telosb. What i need now
is just to communicate with the memory in i2c with the radio turned off
(avoiding in this way arbitration issues). Is there any pratical example of
how to communicate in i2c? I'm a tinyos newbeI'll be grateful for
Hello :
I have seen the TEP123 . i want to know whether there are only the two
kinds messages i received in the Basestation ? does the data frame or the
route frame is also put in the data region of message_t ? if yes , if i put
two bytes data in the CTP packet , the payload length region
Hi,
I've installed TOSSIM and NESC. I am using CYGWIN.
I've followed the steps given in the below link.
http://www.tinyos.net/tinyos-2.x/doc/html/install-tinyos.html
While I tried to run a sample code using ncc command am receiving an error
message
The procedure entry point basename could not
Whenever I've had this problem, I've solved it by
running Cygwin setup and letting it update my Cygwin.
As far as I know, this has never caused me any problems.
Eric
On Thu, Mar 13, 2008 at 7:59 AM, Arun Kumar Jayaraman
[EMAIL PROTECTED] wrote:
Hi,
I've installed TOSSIM and NESC. I am
hello om_p:
can you recommend some papers about CTP so i can understand CTP
implementation easily ?
thank you!!
2008/3/13, Omprakash Gnawali [EMAIL PROTECTED]:
On Wed, Mar 12, 2008 at 6:50 AM, jiwen zhang [EMAIL PROTECTED]
wrote:
Hello all :
as we know , ACKs is on link layer ,
Hi,
I have a question on the SACK command strobe for CC2420. As we know, the
RXFIFO can hold several packets as long as the total length is no more than
128. Hence, when the first packet is read out and then a SACK command is
issued, which packet in the RXFIFO queue is the ack for? I checked
Hi Janos,
Finally, I did it. Many thanks for your suggestions.
Ittipong
On 11/03/2008, Ittipong Khemapech [EMAIL PROTECTED] wrote:
Hi Janos,
Thanks for your reply. I'll try it.
Ittipong
On 11/03/2008, Janos Sallai [EMAIL PROTECTED] wrote:
Ittipong,
You will need to refactor
The ACK should be generated for the packet you're currently reading out of
the RXFIFO. The ACK will only be issued if the packet you're currently
reading out has a valid CRC.
-David
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Liusand
Sent:
The mystery 5D is actually an escaped 7D (hmm or 7E -- I don't remember
which off-hand). The trailing 7E's are the framing bytes at the end and
beginning of each message (thus leading to the need for escaping them
elsewhere) and the last 42 is radio message type, so your framing is
off a bit. I
Try this:
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2008-February/031395.html
Mike
On Thu, 13 Mar 2008, Arun Kumar Jayaraman wrote:
Hi,
I've installed TOSSIM and NESC. I am using CYGWIN.
I've followed the steps given in the below link.
I haven't tried low power listening, but trying to think things through,
it doesn't seem like it meets my needs. I have a sensor field where
much of the time there will be radio activity in range of all of the
sensor nodes.
However, I am keeping track of the likelihood that the sensor node needs
TEP 115 does not apply to the radio architecture unfortunately. If
you are looking into implementing a new Mac protocol, you should check
out the UPMA mac layer architecture from Washington University in St.
Louis.
I was working on this project up until about a year ago at which time
we had
Does anyone know what the speed of the SPI bus for the Tmote sky is?
I am seeing the READ/WRITE SPI speed around 44 - 45 us per byte. This is about
175 kbps. The SPI clock signal is 0.5 MHz or 500 kHz. Does my rate seem correct?
Thank you. any help will be very appreciated.
On Thu, Mar 13, 2008 at 3:54 AM, jiwen zhang [EMAIL PROTECTED] wrote:
Hello :
I have seen the TEP123 . i want to know whether there are only the two
kinds messages i received in the Basestation ? does the data frame or the
route frame is also put in the data region of message_t ? if yes ,
On Thu, Mar 13, 2008 at 4:40 AM, jiwen zhang [EMAIL PROTECTED] wrote:
hello om_p:
can you recommend some papers about CTP so i can understand CTP
implementation easily ?
CTP is inspired by previous work such as Alec Woo's paper:
http://citeseer.ist.psu.edu/woo03taming.html
We wrote a
Hi,
I noticed that, in CC2420ReceiveP.nc from TinyOS 2.0.2, the receive()
function calls RXFIFO.beginRead() without checking its return value. But as
stated in CC2420Fifo.nc, beginRead() is supposed to return status byte
returned when sending the last address byte of the SPI transaction. So
The status byte returned by the command over SPI is not important in this
particular case, so we ignore it intentionally. In order to get a receive()
event fired, the radio must be in the proper state, and therefore
beginRead() will always succeeds.
The status byte is important when the radio
Hi!
For the people interested in the simulation of CC2420: I updated the
repository to include Mike Liang's channel switching. A consequence of
this is removal of the cc2420sim+mc branch. I also removed the
cc2420sim branch because it is the master now. I will also soon remove
the
21 matches
Mail list logo
