Re: [Tinyos-help] Installation help

[Nilesh Mishra]

Hi,
   I suppose the USART is multiplexed between the radio and the SPI so
connecting it won't be a problem, you will need to acquire the bus though
using the proper arbiter before calling SPI functions. Another way can be to
use the I2C pins on the header and using a I2C to SPI converter (it is
commonly available I suppose).
Thanks,
Nilesh

On Tue, Mar 11, 2008 at 4:02 AM, miriam herraiz <[EMAIL PROTECTED]>
wrote:

>
>
>  Hi all,
> >
> > My doubt is about the SPI interface of tmote sky. I going to use a power
> > meter which have also SPI interface, so I pretend to connect both using
> > that, but I am not sure if I can use the SPI of tmote because I read this is
> > used by the radio. anybody knows if there is a free pin in tmote to connect
> > the power meter??
> > thanks,
> > Miriam
> >
>
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>



-- 
Regards
Nilesh

Nilesh Mishra
Embedded Networks Laboratory
University of Southern California,
3710 S. McClintock Avenue, Ronald Tutor Hall (RTH) 418
Los Angeles, CA 90089
mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
ph: (213) 821-5627 (lab)
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] USART1 at IRIS mote under TinyOS-2.x

[Miles Tegson]

Janos,

thanks for your quick answer.

The sensor board MTS420 use the UART1 of mica bus, therefore it isn't possible 
to switch to UART0 of mica bus. At tinyOS 1.x it works with UART1 well.

I'm not sure what you mean with
"USART1 is used by the radio (in SPI mode)"
I thought the communication between atm1281 and rf230 happen about SPI-bus. 

Use the IRIS mote the USART1 interface for SPI? 
I ask because the atm1281 have a seperate SPI port, therefore I thought it 
should exist any restrictions for using UART1 and SPI from the hardware layer.

Exists any possibility in tinyos 2.x to use SerialActiveMessage (UART0), USART1 
(raw data) and SPI for radio together?

Or, where can I find more information about communication by UART1 in SPI mode?

Thanks a lot,
Miles

Janos Sallai wrote:
> Miles,
>
> USART1 is used by the radio (in SPI mode), so you should use USART0 instead. 
> Just make sure that you don't use SerialActiveMessageC in your application, 
> this way, no other higher level components will be calling HplAtm128UartC 
> other than your GPS driver.
>
> Janos
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Miles Tegson
> Sent: Friday, March 14, 2008 6:35 AM
> To: tinyos-help@millennium.berkeley.edu
> Subject: [Tinyos-help] USART1 at IRIS mote under TinyOS-2.x
>
> Hi,
>
> I'm new here. I hope somebody could help me.
>
> I like to use USART1 at the IRIS mote under TinyOS-2.x to receive raw data 
> for example from GPS-device at MTS420 sensor board. Because 
> SerialActiveMessage use UART0 I wrote my own configuration to connect 
> HplAtm128UartC.Uart1 like at Atm128Uart0C with SerialP to get an UartStream.
>
> At time the UartStream.receive execute, but unfortunately with byte equal 
> 0x00. I'm not sure where could be my failure, in code, baudrate or anywhere 
> else. The GPS-device communicat with 9600 baud.
> I use "make iris install baud,9600 mib510,/dev/ttyUSB0"
>
> Thanks a lot,
> Miles
>
> configuration Atm128Uart1C {
> provides interface StdControl;
>   provides interface UartByte;
>   provides interface UartStream;
>   uses interface Counter;
> }
>
> implementation
> {
> components new Atm128UartP() as UartP;
>   StdControl = UartP;
>   UartByte = UartP;
>   UartStream = UartP;
>   UartP.Counter = Counter;
> components HplAtm128UartC as HplUartC;
>   UartP.HplUartTxControl -> HplUartC.Uart1TxControl;
>   UartP.HplUartRxControl -> HplUartC.Uart1RxControl;
>   UartP.HplUart -> HplUartC.HplUart1;
> components MainC;
>   MainC.SoftwareInit -> UartP; }
>
>




-- 
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED]
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Tinyos2 mica2 rssi value reading

[Dimas Abreu Dutra]

Hi,


try looking past messages from this list or googling it. In a quick search I
found the following threads that might help you. When I used it was
something like that.

http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2004-August/005027.html
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2005-November/013154.html

~Dimas~
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Mac layer

[funofnet Funofnet]

Hi for every one,
I have 2 very "tiny "questions:

Which are the components representing mac layer in tinyos-1.x invoked when 
running a tossim simulation.
How is it done the synchronisation between motes so?
I applogize if these questions are asked before but I didn't find precise 
answers.

Thanks a lot.


  
_ 
Envoyez avec Yahoo! Mail. La boite email la plus appreciée au monde. 
http://mail.yahoo.fr___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] SACK

[David Moss]

>From the datasheet:

 

Two command strobes, SACK and

SACKPEND are defined to transmit

acknowledge frames with the frame

pending field cleared or set, respectively.

The acknowledge frame is only

transmitted if the CRC is valid.

 

 

The CRC is checked in hardware before the acknowledgment frame is
transmitted.


-David

 

 

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of renjie
huang
Sent: Sunday, March 16, 2008 2:12 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [Tinyos-help] SACK

 

It seems that in TinyOS-2.x for CC2420 SACK strobe is issued when
SACK_HEADER_LENGTH bytes of data is received and address check is passed. In
this way it does not check crc before issuing SACK. Is it reliable enough?
Why don't we wait until the whole packet is received from RXFIFO?  If I want
to issue SACK strobe only after receiving the whole packet from RXFIFO, is
there something I should be careful? Thanks.

-- 
 
  Renjie 

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] Can anyone help me clarify the MicaZ (CC2420) radiostack?

[David Moss]

The CC1000 and CC2420 radios are completely different, with no relation to
each other.

 

Disabling CCA is easy to do in TinyOS 2.x: you just capture requestCca()
event in the RadioBackoff interface, provided by CC2420CsmaC, and call back
within that event to setCca(FALSE).

 

TinyOS 1.x is no longer supported; however, you will be able to disable the
CCA backoffs by searching and replacing any instance of "STXONCCA" with
"STXON" in any CC2420 source code.

 

-David

 

 

 

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ruoshui
Liu
Sent: Sunday, March 16, 2008 4:56 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [Tinyos-help] Can anyone help me clarify the MicaZ (CC2420)
radiostack?

 

Dear all,

Currently I am working on the MicaZ using CC2420 radio stack, and I am
trying to completely disable the CCA function implemented by CC2420 radio
stack. However, I did not find the right function to do so. Therefore, I
went through the Mica High Speed Radio Stack and the Mica2 (CC1000) Radio
Stack stated on the web: http://www.tinyos.net/tinyos-1.x/doc/. 

The question is what is the difference between the Mica2 (CC1000) Radio
Stack and the Mica High Speed Radio Stack. Is the Mica2 (CC1000) Radio Stack
totally different deign from the Mica High Speed Radio Stack, or interleaved
design with it? They really confuse me!

The other question is that where I can find the detail of MicaZ (CC2420)
Radio Stack implemented with TinyOS 1.1.15. I know there is an article
describing the MicaZ (CC2420) Radio Stack, but all the functions stated in
that are implemented in TinyOS 2.0 which is not my case. 

I really need to find the right function to disable the CCA in CC2420
regardless whether the channel is busy or not by using TinyOS 1.1.15. 

Many thanks!

Ruoshui 

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] TXFIFO underflow not taken care of in TinyOS 2.0.2?

[David Moss]

Hi Sha -

You're right, we are missing a check for RXFIFO overflow.  Right now the
maximum default CC2420 packet size in TinyOS is 41 bytes (including CRC).
The RXFIFO is 128 bytes, which means you'd be able to fit 3 full packets in
the RXFIFO before an overflow occurs.  Although I think it may be unlikely
that you'd spontaneously receive 3+ full packets in the RXFIFO due to CSMA
backoffs and transmit delays, it can still happen.  

But imagine this scenario: you receive 3 maxed-out packets that are valid,
and get a fourth packet that causes an RXFIFO overflow, and is therefore
corrupted.  Do you flush the RXFIFO at that point and lose the 3 valid
packets that are already in there?  Or do you wait until you're reading out
the fourth packet that is corrupted before flushing it?  In the current
scenario, you read out the amount of data as specified by the fourth packet
and see that the CRC doesn't check out.  Upon reading the next packet, the
length is found to be invalid and the RXFIFO is flushed.  

Putting in an explicit check for RXFIFO overflow may be more desirable, but
the question is, when is the best time to flush the RXFIFO?  Right when the
error occurs? Or after you get any remaining valid packets out?

-David



-Original Message-
From: Liusand [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 14, 2008 10:33 PM
To: David Moss; tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] TXFIFO underflow not taken care of in TinyOS
2.0.2?

Thanks, David.

I have some questions concerning RXFIFO overflow. In CC2420ReceiveP.nc, 
RXFIFO is flushed only when the length byte is invalid. So where is RXFIFO 
overflow taken care of? Can reading bytes from RXFIFO automatically clear 
the overflow status?

Also, in CC2420TransmitP, RXFIFO overflow status is not checked before 
issuing the STXONCCA or STXON strobe. So if RXFIFO has already overflowed, 
there will be no more space for ack frame. TinyOS 1.1.15 does do this check 
before sending and flush RXFIFO accordingly even though I'm not sure if it 
is for this purpose.

Thanks,

-Sha


--
From: "David Moss" <[EMAIL PROTECTED]>
Sent: Friday, March 14, 2008 5:26 PM
To: "'Liusand'" <[EMAIL PROTECTED]>; 
Subject: RE: [Tinyos-help] TXFIFO underflow not taken care of in TinyOS 
2.0.2?

> The TX FIFO is preloaded with data.  The data is not being transmitted to
> the CC2420 as the transmission is taking place, unlike other chips. 
> Because
> of the preload, it is impossible for the CC2420 to produce a TXFIFO
> UNDERFLOW. All the data to send is available on the chip when transmit
> occurs.
>
> Due to the rules of the CSMA and Transmit modules, a new packet cannot be
> uploaded to the TX FIFO until the previous packet in the TX FIFO was
> transmitted.  This should guarantee that the TX FIFO be empty when the 
> next
> transmit occurs.  If a cancel occurs, a quick SFLUSHTX empties the 
> contents
> of the TX FIFO.
>
> -David
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Liusand
> Sent: Friday, March 14, 2008 12:45 PM
> To: tinyos-help@millennium.berkeley.edu
> Subject: [Tinyos-help] TXFIFO underflow not taken care of in TinyOS 2.0.2?
>
> Hi,
>
> When I was studying CC2420TransmitP.nc, I noticed that TXFIFO is never
> flushed and underflow status is never checked. In CC2420RadioM.nc from
> TinyOS 1.1.15, TXFIFO is flushed in startSend() every time before it is
> written data to.
>
> It might be too conservative in TinyOS 1.1.15, but why overflow is never
> taken care of in TinyOS 2.0.2?
>
> Another related question is, in which situations TXFIFO underflow may
> happen?
>
> Thanks,
>
> Sha
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
>
> 


___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] tinyos-2.X packet size

[Boushra MAALA]

hi, i now that in tinyos1, the paket size is limited to 29 bytes.is this the same thing in tinyos2.Boushra
  Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] [help] wiring CC2420Config, CC2420Packet, CC2420PacketBody etc to my codes

[Ittipong Khemapech]

Not sure whether you've already figured it out.

CC2420Config is provided by CC2420Control component.

Ittipong

On 11/03/2008, Baozhi Chen <[EMAIL PROTECTED]> wrote:
>
> Thank you a lot. How about CC2420Config?
>
> Philip
>
> On Tue, Mar 11, 2008 at 10:20 AM, Ittipong Khemapech <
> [EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > Actually, the CC2420Packet is interface provided by CC2420ActiveMessageC
> > component.
> >
> > Assume that you rename your own component as App, just do this...
> >
> > App.CC2420Packet -> CC2420ActiveMessageC;
> >
> > Ittipong
> >
> > On 11/03/2008, Baozhi Chen <[EMAIL PROTECTED]> wrote:
> >
> > > Hi,
> > >
> > > I want to wire components like CC2420Config, CC2420Packet,
> > > CC2420PacketBody, CC2420ControlC in my code.
> > > For example, in my configuration, I do the following
> > >
> > > configuration ABC{
> > > }implementation{
> > >   components CC2420ControlC;
> > >
> > > 
> > > }
> > >
> > >
> > > However, the compiler always reports not find them. How do I configure
> > > the options so that they can be found?
> > >
> > > Thanks.
> > >
> > > Philip
> > >
> > >
> > > ___
> > > Tinyos-help mailing list
> > > Tinyos-help@millennium.berkeley.edu
> > >
> > > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> > >
> >
> >
>
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] TXFIFO underflow not taken care of in TinyOS 2.0.2?

[Liusand]

Hi David,

Thanks for the explanation.

The treatment of packets already in the RXFIFO queue is definitely 
reasonable to the receiver. But if we use SACK to issue acknowledgements 
like in CC2420ReceiveP.nc, the 3rd packet may wait quite some time before 
the ack for it is sent, and hence the deadline at sender side may have been 
missed. The delay before ack timer fires is CC2420_ACK_WAIT_DELAY = 256, so 
does it take the delay in reading RXFIFO into consideration? What is the SPI 
speed in TelosB or TmoteSky?


Thanks,

Sha


--
From: "David Moss" <[EMAIL PROTECTED]>
Sent: Monday, March 17, 2008 10:21 AM
To: "'Liusand'" <[EMAIL PROTECTED]>; 
Subject: RE: [Tinyos-help] TXFIFO underflow not taken care of in TinyOS 
2.0.2?



Hi Sha -

You're right, we are missing a check for RXFIFO overflow.  Right now the
maximum default CC2420 packet size in TinyOS is 41 bytes (including CRC).
The RXFIFO is 128 bytes, which means you'd be able to fit 3 full packets 
in

the RXFIFO before an overflow occurs.  Although I think it may be unlikely
that you'd spontaneously receive 3+ full packets in the RXFIFO due to CSMA
backoffs and transmit delays, it can still happen.

But imagine this scenario: you receive 3 maxed-out packets that are valid,
and get a fourth packet that causes an RXFIFO overflow, and is therefore
corrupted.  Do you flush the RXFIFO at that point and lose the 3 valid
packets that are already in there?  Or do you wait until you're reading 
out

the fourth packet that is corrupted before flushing it?  In the current
scenario, you read out the amount of data as specified by the fourth 
packet

and see that the CRC doesn't check out.  Upon reading the next packet, the
length is found to be invalid and the RXFIFO is flushed.

Putting in an explicit check for RXFIFO overflow may be more desirable, 
but
the question is, when is the best time to flush the RXFIFO?  Right when 
the

error occurs? Or after you get any remaining valid packets out?

-David



-Original Message-
From: Liusand [mailto:[EMAIL PROTECTED]
Sent: Friday, March 14, 2008 10:33 PM
To: David Moss; tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] TXFIFO underflow not taken care of in TinyOS
2.0.2?

Thanks, David.

I have some questions concerning RXFIFO overflow. In CC2420ReceiveP.nc,
RXFIFO is flushed only when the length byte is invalid. So where is RXFIFO
overflow taken care of? Can reading bytes from RXFIFO automatically clear
the overflow status?

Also, in CC2420TransmitP, RXFIFO overflow status is not checked before
issuing the STXONCCA or STXON strobe. So if RXFIFO has already overflowed,
there will be no more space for ack frame. TinyOS 1.1.15 does do this 
check

before sending and flush RXFIFO accordingly even though I'm not sure if it
is for this purpose.

Thanks,

-Sha


--
From: "David Moss" <[EMAIL PROTECTED]>
Sent: Friday, March 14, 2008 5:26 PM
To: "'Liusand'" <[EMAIL PROTECTED]>; 


Subject: RE: [Tinyos-help] TXFIFO underflow not taken care of in TinyOS
2.0.2?


The TX FIFO is preloaded with data.  The data is not being transmitted to
the CC2420 as the transmission is taking place, unlike other chips.
Because
of the preload, it is impossible for the CC2420 to produce a TXFIFO
UNDERFLOW. All the data to send is available on the chip when transmit
occurs.

Due to the rules of the CSMA and Transmit modules, a new packet cannot be
uploaded to the TX FIFO until the previous packet in the TX FIFO was
transmitted.  This should guarantee that the TX FIFO be empty when the
next
transmit occurs.  If a cancel occurs, a quick SFLUSHTX empties the
contents
of the TX FIFO.

-David



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Liusand
Sent: Friday, March 14, 2008 12:45 PM
To: tinyos-help@millennium.berkeley.edu
Subject: [Tinyos-help] TXFIFO underflow not taken care of in TinyOS 
2.0.2?


Hi,

When I was studying CC2420TransmitP.nc, I noticed that TXFIFO is never
flushed and underflow status is never checked. In CC2420RadioM.nc from
TinyOS 1.1.15, TXFIFO is flushed in startSend() every time before it is
written data to.

It might be too conservative in TinyOS 1.1.15, but why overflow is never
taken care of in TinyOS 2.0.2?

Another related question is, in which situations TXFIFO underflow may
happen?

Thanks,

Sha

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help








___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Can anyone help me clarify the MicaZ (CC2420) radiostack?

[Ruoshui Liu]

Thanks very much for David's advice.  I am installing modified version 
of CountDual application on one mote as the transmitter, and the 
modified version of TOSBase on another as the receiver. I found the 
CountDual application is using the *GenericComm* component, is that 
different from the CC2420 radio stack? Do I need to replace it with 
CC2420RadioC if I want to use the CC2420 radio stack?


The TOSBase application is using the RadioCRCPacket component for the 
radio stack, do I need to change to CC2420RadioC in order to use the 
CC2420 radio stack? Since simply replacing the "STXONCCA" with "STXON" 
won't take any effect if I didn't use the CC2420 radio stack. Is my 
guess right?


Thank you very much!
Ruoshui


David Moss wrote:


The CC1000 and CC2420 radios are completely different, with no 
relation to each other.


 

Disabling CCA is easy to do in TinyOS 2.x: you just capture 
requestCca() event in the RadioBackoff interface, provided by 
CC2420CsmaC, and call back within that event to setCca(FALSE).


 

TinyOS 1.x is no longer supported; however, you will be able to 
disable the CCA backoffs by searching and replacing any instance of 
"STXONCCA" with "STXON" in any CC2420 source code.


 


-David

 

 

 

 




*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of 
*Ruoshui Liu

*Sent:* Sunday, March 16, 2008 4:56 PM
*To:* tinyos-help@millennium.berkeley.edu
*Subject:* [Tinyos-help] Can anyone help me clarify the MicaZ (CC2420) 
radiostack?


 


Dear all,

Currently I am working on the MicaZ using CC2420 radio stack, and I am 
trying to completely disable the CCA function implemented by CC2420 
radio stack. However, I did not find the right function to do so. 
Therefore, I went through the *Mica High Speed Radio Stack *and the 
*Mica2 (CC1000) Radio Stack* stated on the web: 
http://www.tinyos.net/tinyos-1.x/doc/.


The question is what is the difference between the *Mica2 (CC1000) 
Radio Stack *and the *Mica High Speed Radio Stack*. Is the Mica2 
(CC1000) Radio Stack totally different deign from the Mica High Speed 
Radio Stack, or interleaved design with it? They really confuse me!


The other question is that where I can find the detail of *MicaZ 
(CC2420) Radio Stack *implemented with TinyOS 1.1.15. I know there is 
an article describing the *MicaZ (CC2420) Radio Stack*, but all the 
functions stated in that are implemented in TinyOS 2.0 which is not my 
case.


I really need to find the right function to disable the CCA in CC2420 
regardless whether the channel is busy or not by using TinyOS 1.1.15.


Many thanks!

Ruoshui



___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] tinyos-2.X packet size

[Markus de Brün]

> i now that in tinyos1, the paket size is limited to 29 bytes.
That's the default payload length.
This value is specified by TOSH_DATA_LENGTH and can be reset, for
instance, in your makefile using:
CFLAGS +=-DTOSH_DATA_LENGTH=value

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] [help] wiring CC2420Config, CC2420Packet, CC2420PacketBody etc to my codes

[Ittipong Khemapech]

Forget this one.

CC2420PacketC provides CC2420PacketBody interface.

Ittipong

On 17/03/2008, Ittipong Khemapech <[EMAIL PROTECTED]> wrote:
>
> Not sure whether you've already figured it out.
>
> CC2420Config is provided by CC2420Control component.
>
> Ittipong
>
> On 11/03/2008, Baozhi Chen <[EMAIL PROTECTED]> wrote:
> >
> > Thank you a lot. How about CC2420Config?
> >
> > Philip
> >
> > On Tue, Mar 11, 2008 at 10:20 AM, Ittipong Khemapech <
> > [EMAIL PROTECTED]> wrote:
> >
> > > Hi,
> > >
> > > Actually, the CC2420Packet is interface provided by
> > > CC2420ActiveMessageC component.
> > >
> > > Assume that you rename your own component as App, just do this...
> > >
> > > App.CC2420Packet -> CC2420ActiveMessageC;
> > >
> > > Ittipong
> > >
> > > On 11/03/2008, Baozhi Chen <[EMAIL PROTECTED]> wrote:
> > >
> > > > Hi,
> > > >
> > > > I want to wire components like CC2420Config, CC2420Packet,
> > > > CC2420PacketBody, CC2420ControlC in my code.
> > > > For example, in my configuration, I do the following
> > > >
> > > > configuration ABC{
> > > > }implementation{
> > > >   components CC2420ControlC;
> > > >
> > > > 
> > > > }
> > > >
> > > >
> > > > However, the compiler always reports not find them. How do I
> > > > configure the options so that they can be found?
> > > >
> > > > Thanks.
> > > >
> > > > Philip
> > > >
> > > >
> > > > ___
> > > > Tinyos-help mailing list
> > > > Tinyos-help@millennium.berkeley.edu
> > > >
> > > > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> > > >
> > >
> > >
> >
>
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] TXFIFO underflow not taken care of in TinyOS 2.0.2?

[David Moss]

The ACK delay was increased from ~128 (or lower) from earlier versions of
the CC2420 to 256 simply to handle these types of cases.  Functional tests
show this delay works well for 'normal' networks of multiple nodes and
unaltered CSMA backoffs; however, modifying the CSMA behavior may
necessitate changes to the ACK delay.  The ACK delay, like many parameters
in the stack, was chosen based on the results of functional testing (with no
SPI0 DMA).

I'm not sure off the top of my head what the SPI throughput is, but it can
also vary based on DMA settings.  Adding SPI0 DMA support greatly increases
the throughput.

-David



 -Original Message-
From: Liusand [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 17, 2008 8:08 AM
To: David Moss; tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] TXFIFO underflow not taken care of in TinyOS
2.0.2?

Hi David,

Thanks for the explanation.

The treatment of packets already in the RXFIFO queue is definitely 
reasonable to the receiver. But if we use SACK to issue acknowledgements 
like in CC2420ReceiveP.nc, the 3rd packet may wait quite some time before 
the ack for it is sent, and hence the deadline at sender side may have been 
missed. The delay before ack timer fires is CC2420_ACK_WAIT_DELAY = 256, so 
does it take the delay in reading RXFIFO into consideration? What is the SPI

speed in TelosB or TmoteSky?

Thanks,

Sha


--
From: "David Moss" <[EMAIL PROTECTED]>
Sent: Monday, March 17, 2008 10:21 AM
To: "'Liusand'" <[EMAIL PROTECTED]>; 
Subject: RE: [Tinyos-help] TXFIFO underflow not taken care of in TinyOS 
2.0.2?

> Hi Sha -
>
> You're right, we are missing a check for RXFIFO overflow.  Right now the
> maximum default CC2420 packet size in TinyOS is 41 bytes (including CRC).
> The RXFIFO is 128 bytes, which means you'd be able to fit 3 full packets 
> in
> the RXFIFO before an overflow occurs.  Although I think it may be unlikely
> that you'd spontaneously receive 3+ full packets in the RXFIFO due to CSMA
> backoffs and transmit delays, it can still happen.
>
> But imagine this scenario: you receive 3 maxed-out packets that are valid,
> and get a fourth packet that causes an RXFIFO overflow, and is therefore
> corrupted.  Do you flush the RXFIFO at that point and lose the 3 valid
> packets that are already in there?  Or do you wait until you're reading 
> out
> the fourth packet that is corrupted before flushing it?  In the current
> scenario, you read out the amount of data as specified by the fourth 
> packet
> and see that the CRC doesn't check out.  Upon reading the next packet, the
> length is found to be invalid and the RXFIFO is flushed.
>
> Putting in an explicit check for RXFIFO overflow may be more desirable, 
> but
> the question is, when is the best time to flush the RXFIFO?  Right when 
> the
> error occurs? Or after you get any remaining valid packets out?
>
> -David
>
>
>
> -Original Message-
> From: Liusand [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 14, 2008 10:33 PM
> To: David Moss; tinyos-help@millennium.berkeley.edu
> Subject: Re: [Tinyos-help] TXFIFO underflow not taken care of in TinyOS
> 2.0.2?
>
> Thanks, David.
>
> I have some questions concerning RXFIFO overflow. In CC2420ReceiveP.nc,
> RXFIFO is flushed only when the length byte is invalid. So where is RXFIFO
> overflow taken care of? Can reading bytes from RXFIFO automatically clear
> the overflow status?
>
> Also, in CC2420TransmitP, RXFIFO overflow status is not checked before
> issuing the STXONCCA or STXON strobe. So if RXFIFO has already overflowed,
> there will be no more space for ack frame. TinyOS 1.1.15 does do this 
> check
> before sending and flush RXFIFO accordingly even though I'm not sure if it
> is for this purpose.
>
> Thanks,
>
> -Sha
>
>
> --
> From: "David Moss" <[EMAIL PROTECTED]>
> Sent: Friday, March 14, 2008 5:26 PM
> To: "'Liusand'" <[EMAIL PROTECTED]>; 
> 
> Subject: RE: [Tinyos-help] TXFIFO underflow not taken care of in TinyOS
> 2.0.2?
>
>> The TX FIFO is preloaded with data.  The data is not being transmitted to
>> the CC2420 as the transmission is taking place, unlike other chips.
>> Because
>> of the preload, it is impossible for the CC2420 to produce a TXFIFO
>> UNDERFLOW. All the data to send is available on the chip when transmit
>> occurs.
>>
>> Due to the rules of the CSMA and Transmit modules, a new packet cannot be
>> uploaded to the TX FIFO until the previous packet in the TX FIFO was
>> transmitted.  This should guarantee that the TX FIFO be empty when the
>> next
>> transmit occurs.  If a cancel occurs, a quick SFLUSHTX empties the
>> contents
>> of the TX FIFO.
>>
>> -David
>>
>>
>>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Liusand
>> Sent: Friday, March 14, 2008 12:45 PM
>> To: tinyos-help@millennium.berkeley.edu
>> Subject: [Tinyos-help] TXFIFO underflow not taken 

[Tinyos-help] writing problem with micaz

[ilpadrino corleone]

Hello,
I have installed the crossbow software (cygwin, moteconfig, moteview, ...) on 
windows xp. When I try to install MyApp (tutorials/lesson1) into the mote I 
will get it compiled but it won't upload. 

make micaz install mib520,com3
{}
uisp -dprog=mib520 -dserial=com3 --wr_fuse_h=0xd9 -dpart=ATmega128 
--wr_fuse_e=ff --erase --upload if=build/micaz/main.srec.out

and after that line cygwin will stay silent. I also tried to program it with 
MoteConfig without any results.

I have micaz motes, with a mib520 board and msp400. 

If anyone could give me a hint of what's going on I'd be grateful.

Thanks in advance,

David 


_
MSN Video. 
http://video.msn.com/?mkt=es-es___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Size of message_t

[Eli Gotesman]

Hi All,

I wrote the following program:
one sensor sends data (an array of integers) and another sensor that
receives

I wrote the following header file that defines the structure of the message:


#ifndef RSSISAMPLESC_H
#define RSSISAMPLESC_H

#define SAMPLES_NUM 1002
#define MESSAGE_LEN 100

enum
{
  AM_RssiSamplesC = 6
};

typedef nx_struct RssiSamplesMsg
{
  nx_uint8_t moteid;
  nx_int8_t samples_packet[MESSAGE_LEN];
} RssiSamplesMsg;

#endif


My Problem is with the value of MESSAGE_LEN

If MESSAGE_LEN is equal to 100 then the sender sends the messages but the
reciever doesn't recieve anything ( the recieve event doesn't oocur)
If MESSAGE_LEN is equal to 25 then every thing works fine.

I guess this is got something with the size of message_t...
My question is: what is the maximum size of a message that I can send, and
how I can change this size?

Thanks,
Eli
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] tinyos-2.X packet size

[Michael Schippling]

The packet payload size can be changed in T1 by changing
TOSH_DATA_LENGTH at compile time. I suspect there is a
similar define (and further suspect that "they" changed
the name just to keep "us" on our toes). Search this list
for references to those names to find a multitude of advice.

MS

Boushra MAALA wrote:

hi,
i now that in tinyos1, the paket size is limited to 29 bytes.
is this the same thing in tinyos2.
Boushra



Looking for last minute shopping deals? Find them fast with Yahoo! 
Search. 
 






___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] USART1 at IRIS mote under TinyOS-2.x

[Janos Sallai]

Miles,

>The sensor board MTS420 use the UART1 of mica bus, therefore it isn't
possible to switch to UART0 of mica bus. >At tinyOS 1.x it works with
UART1 well.
OK, then you must use USART1.

>?I'm not sure what you mean with
>"USART1 is used by the radio (in SPI mode)"
>I thought the communication between atm1281 and rf230 happen about
SPI-bus. 
Yes, you're right. The radio is on the SPI bus. It's the flash that's on
the USART1 (in SPI mode). If you don't use the flash though, the GPS
driver should work fine. Make sure that after calling Uart1Init.init()
you set the baud rate to 9600bps by writing the ubrr1 register to 47.
This value will be different if you operate the mote at a clock speed
other than the default 7.3MHz (see table 22-1 in the datasheet).

>Use the IRIS mote the USART1 interface for SPI? 
>I ask because the atm1281 have a seperate SPI port, therefore I thought
it should exist any restrictions for >using UART1 and SPI from the
hardware layer.
The radio is on the separate SPI, but the USARTs can be used in SPI mode
as well.

>Exists any possibility in tinyos 2.x to use SerialActiveMessage
(UART0), USART1 (raw data) and SPI for radio >together?
Yes. There may be some issues though if you want to use the flash, too.

>Or, where can I find more information about communication by UART1 in
SPI mode?
It's explained in the ATMega 1281 datasheet. (
http://atmel.com/dyn/resources/prod_documents/doc2549.pdf )

Janos

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] MultihopOscilloscope application with Snooping ???

[Mahesh Satharla]

Hi Everyone,

I setup a network of 4 motes( including basestation) running with
'MultihopOscilloscope' application from TinyOS 2.x.

// MultihopOscilloscope is a simple data-collection demo. It periodically
samples the default sensor and broadcasts a message every few readings //

I want to implement Snooping in this application, because neighboring nodes
needs to snoop
information transmitted to the base station.

According to my understanding, inorder to implement snooping I should use
AMSnoopingReceiveC/AMSnoopingC component instead of AMReceiveC and I need to
disable to address decoding in makefile by
CFLAGS += -DCC2420_NO_ADDRESS_RECOGNITION

When I see this code in MultihopOscilloscope application
// Overhearing other traffic in the network.
  //
  event message_t*
  Snoop.receive(message_t* msg, void* payload, uint8_t len) {
oscilloscope_t *omsg = payload;
///

Is this code mean the "Snooping" already implemented in this application.??
If so, I didnt find any wiring to AMSnooperC component in configuration
file.

I guess Snoop.receive is called by the nodes which are forwarding messages
to base station.

Will it create any problems if I use AMSnooperC component for 'Receive'
interface.?


Thanks in Advance,
Mahesh Satharla.
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Utilizing a command from another module,

[Mark Tsang]

I was wondering how I would go about calling a command from another module
to utilize in my own module.  For instance, I want to use the command
"txBytes" in NoCRCPacket in my own program MyApp.  What do I have to add in
my program to do so.  I've read in other threads that I need to wire
NoCRCPacket to UART and I have done so, but I'm still receiving the
following error message during compilation:  NOTE:  I'm calling txBytes in
my Timer.fired command below in the module

 

In component `NoCRCPacket':

/opt/MoteWorks/tos/platform/micaz/NoCRCPacket.nc: In function `receiveTask':

/opt/MoteWorks/tos/platform/micaz/NoCRCPacket.nc:306: Receive.receive not
connected

 

 

The error message isn't pointing to my program, instead the platform file.
What am I doing wrong.  Thanks in advance!

 

configuration MyApp {

  provides {

command result_t txBytes(uint8_t *bytes, uint8_t numBytes);

  }

}

implementation {

  components Main, MyAppM, TimerC, LedsC, NoCRCPacket as NoPacket, UART;

  

  Main.StdControl -> TimerC.StdControl;

  Main.StdControl -> MyAppM.StdControl;

  Main.StdControl -> NoPacket.Control;

  

  MyAppM.Timer -> TimerC.Timer[unique("Timer")];

  MyAppM.Leds -> LedsC.Leds;

  

  txBytes = NoPacket.txBytes;

  

  NoPacket.ByteControl -> UART;

  NoPacket.ByteComm -> UART;

 

}

 

module MyAppM {

  provides {

interface StdControl;



  }

  uses {

interface Timer;

interface Leds;

interface StdControl as PhotoControl;

interface SendUART;



command result_t txBytes(uint8_t *bytes, uint8_t numBytes);

  }

}

implementation {

 

  /**

   * Toggle the red LED in response to the Timer.fired event.  

   * Start the Light sensor control and sample the data

   *

   * @return Always returns SUCCESS

   **/

  event result_t Timer.fired()

  {

call Leds.redToggle();

// send message to UART (serial) port

if (call txBytes((uint8_t *)0x41,(uint8_t *)0x01) !=
SUCCESS)

  sending_packet = FALSE;

  

return SUCCESS;

  }

 

  command result_t StdControl.init() {

call Leds.init(); 

}

 

  command result_t StdControl.start() {

// Start a repeating timer that fires every 1000ms

return call Timer.start(TIMER_REPEAT, 1000);

  }

 

  /**

   * Halt execution of the application.

   * This just disables the clock component.

   * 

   * @return Always returns SUCCESS

   **/

  command result_t StdControl.stop() {

return call Timer.stop();

  }

 

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] writing problem with micaz

[Giri Baleri]

Few things to check/try:
- Make sure the programming port on MIB520 is in fact COM3 (lower of the 2 COM 
ports)
- Make sure that the Mote is seated firmly into the 51-pin connector of the 
MIB520
- Make sure that no other application is using COM3.
- Try "make micaz install mib520,/dev/ttyS2" or "make micaz install 
mib510,/dev/ttyS2" instead.
 
Good luck,
Giri
 



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ilpadrino 
corleone
Sent: Monday, March 17, 2008 10:05 AM
To: tinyos-help@millennium.berkeley.edu
Subject: [Tinyos-help] writing problem with micaz


Hello,
I have installed the crossbow software (cygwin, moteconfig, moteview, ...) on 
windows xp. When I try to install MyApp (tutorials/lesson1) into the mote I 
will get it compiled but it won't upload. 

make micaz install mib520,com3
{}
uisp -dprog=mib520 -dserial=com3 --wr_fuse_h=0xd9 -dpart=ATmega128 
--wr_fuse_e=ff --erase --upload if=build/micaz/main.srec.out

and after that line cygwin will stay silent. I also tried to program it with 
MoteConfig without any results.

I have micaz motes, with a mib520 board and msp400. 

If anyone could give me a hint of what's going on I'd be grateful.

Thanks in advance,

David 





Todo ruedas: información práctica y todo el glamour del mundo del motor. MSN 
Estilo y Tendencias   
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Re: corrupted data from serial port

[Afonso Ribas]

Hey,

I am facing a similar problem. I am using micaz and some packets received
from serial are corrupted.
In my payload I have the NODEID, a seq. n° and others things like sensor
readings. Sometimes in my java app, I have some messages where NodeID, seq.
number, and the readings are ZERO.
I either don't know what is the problem.




> Date: Fri, 14 Mar 2008 16:55:45 +0200
> From: "Kaan Tuna" <[EMAIL PROTECTED]>
> Subject: [Tinyos-help] corrupted data from serial port
> To: tinyos-help@millennium.berkeley.edu
> Message-ID:
> <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
> When using Tinyos 2.0.2, my root node connected to PC sends sometimes
> corrupt packets through serial port, starting with BE or FE, instead of
> the (7E7E) formation.
> Has anyone encountered a problem like this before ?
> Any idea or help would be granted.
>
> Kaan
> -- next part --
> An HTML attachment was scrubbed...
> URL:
> https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20080314/e8d61de9/attachment.htm
>
>
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] writing problem with micaz

[ilpadrino corleone]

I checked all of the above without result. 
- The port is com3 because it is the lower of both.
- the mote is firmly into the connector because its attached to it with two 
screws. 
- no other application was using the port since I rebooted the machine and this 
was the first thing I did.
- even compiling for mib510 or changing the port for /dev/ttyS2 does not make a 
difference.

I
know for a fact the the mote works, since it was provided to me with an
application that sended all the data from its sensors to MoteView. 

Thank you anyway Giri.

Subject: RE: [Tinyos-help] writing problem with micaz
Date: Mon, 17 Mar 2008 12:58:17 -0700
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: tinyos-help@millennium.berkeley.edu










Few things to check/try:
- Make sure the programming port on MIB520 is in fact COM3 (lower 
of the 2 COM ports)
- Make sure that the Mote is seated firmly into the 51-pin 
connector of the MIB520
- Make sure that no other application is using 
COM3.
- Try "make micaz install mib520,/dev/ttyS2" or "make micaz 
install mib510,/dev/ttyS2" instead.
 
Good luck,
Giri
 



From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of 
ilpadrino corleone
Sent: Monday, March 17, 2008 10:05 
AM
To: tinyos-help@millennium.berkeley.edu
Subject: 
[Tinyos-help] writing problem with micaz


Hello,
I have installed the crossbow software (cygwin, moteconfig, 
moteview, ...) on windows xp. When I try to install MyApp (tutorials/lesson1) 
into the mote I will get it compiled but it won't upload. 

make micaz 
install mib520,com3
{}
uisp -dprog=mib520 -dserial=com3 
--wr_fuse_h=0xd9 -dpart=ATmega128 --wr_fuse_e=ff --erase --upload 
if=build/micaz/main.srec.out

and after that line cygwin will stay silent. 
I also tried to program it with MoteConfig without any results.

I have 
micaz motes, with a mib520 board and msp400. 

If anyone could give me a 
hint of what's going on I'd be grateful.

Thanks in advance,

David 





Todo ruedas: información práctica y todo el glamour del mundo del motor. MSN 
Estilo y Tendencias 


_
MSN Noticias
http://noticias.msn.es/comunidad.aspx___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] tinyos2 i2c example on telosb

[Nilesh Mishra]

Please search the archives and you might find more relevant details. For
telosb in tinyos-1.x you can have a look at the two files available at
\opt\tinyos-1.x\tos\platform\telosb called I2CPacketC.nc  I2CPacketM.nc .
For tinyos-2.x please look at files inside  \opt\tinyos-
2.x\tos\chips\msp430\usart

Hope it gives you some pointers.
Thanks,
Nilesh

On Thu, Mar 13, 2008 at 4:04 AM, Carloalberto Torghele <
[EMAIL PROTECTED]> wrote:

> 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 any
> suggestion.
>
> thanks,
> Carloalberto Torghele
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>



-- 
Regards
Nilesh

Nilesh Mishra
Embedded Networks Laboratory
University of Southern California,
3710 S. McClintock Avenue, Ronald Tutor Hall (RTH) 418
Los Angeles, CA 90089
mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
ph: (213) 821-5627 (lab)
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] writing problem with micaz

[ilpadrino corleone]

Hello Eric,

I can see a switch in the mote which is off, but I think there is no switch in 
the mib520.

Thanks,

David


> Date: Mon, 17 Mar 2008 16:27:07 -0400
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: [Tinyos-help] writing problem with micaz
> 
> David,
> Are both of the switches off on the MIB?
> 
> I have had the same thing happen to me, cygwin would lock.  I used a
> different command line and
> it worked.  I'm not using micaz regularly, so I don't remember what
> the successful command line was.
> 
> Eric
> 
> 
> 
> On Mon, Mar 17, 2008 at 1:04 PM, ilpadrino corleone
> <[EMAIL PROTECTED]> wrote:
> >
> >  Hello,
> > I have installed the crossbow software (cygwin, moteconfig, moteview, ...)
> > on windows xp. When I try to install MyApp (tutorials/lesson1) into the mote
> > I will get it compiled but it won't upload.
> >
> > make micaz install mib520,com3
> > {}
> > uisp -dprog=mib520 -dserial=com3 --wr_fuse_h=0xd9 -dpart=ATmega128
> > --wr_fuse_e=ff --erase --upload if=build/micaz/main.srec.out
> >
> > and after that line cygwin will stay silent. I also tried to program it with
> > MoteConfig without any results.
> >
> > I have micaz motes, with a mib520 board and msp400.
> >
> > If anyone could give me a hint of what's going on I'd be grateful.
> >
> > Thanks in advance,
> >
> > David
> >
> >
> > 
> > Todo ruedas: información práctica y todo el glamour del mundo del motor. MSN
> > Estilo y Tendencias
> > ___
> >  Tinyos-help mailing list
> >  Tinyos-help@millennium.berkeley.edu
> >  https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> >

_
Tecnología, moda, motor, viajes,…suscríbete a nuestros boletines para estar 
siempre a la última
http://newsletters.msn.com/hm/maintenanceeses.asp?L=ES&C=ES&P=WCMaintenance&Brand=WL&RU=http%3a%2f%2fmail.live.com___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Reset Button

[Ittipong Khemapech]

Hi,

Any way that I can restart a mote by coding instead of pressing reset
button? I've search mailing list and found that ResetC.nc may be useful.
Unfortunately, I can't find the file.

I'm using:

Tmote Sky and Invent
TinyOS 2.x
Windows XP & cygwin

Many thanks in advance.

Ittipong
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Utilizing a command from another module,

[Michael Schippling]

look for documentation on NESC. Basically anything in the interface
for a module can be "call"ed from another module.
MS

Mark Tsang wrote:
I was wondering how I would go about calling a command from another 
module to utilize in my own module.  For instance, I want to use the 
command “txBytes” in NoCRCPacket in my own program MyApp.  What do I 
have to add in my program to do so.  I’ve read in other threads that I 
need to wire NoCRCPacket to UART and I have done so, but I’m still 
receiving the following error message during compilation:  NOTE:  I’m 
calling txBytes in my Timer.fired command below in the module


 


In component `NoCRCPacket':

/opt/MoteWorks/tos/platform/micaz/NoCRCPacket.nc: In function `receiveTask':

/opt/MoteWorks/tos/platform/micaz/NoCRCPacket.nc:306: Receive.receive 
not connected


 

 

The error message isn’t pointing to my program, instead the platform 
file.  What am I doing wrong.  Thanks in advance!


 


configuration MyApp {

  provides {

command result_t txBytes(uint8_t *bytes, uint8_t numBytes);

  }

}

implementation {

  components Main, MyAppM, TimerC, LedsC, NoCRCPacket as NoPacket, UART;

 


  Main.StdControl -> TimerC.StdControl;

  Main.StdControl -> MyAppM.StdControl;

  Main.StdControl -> NoPacket.Control;

 


  MyAppM.Timer -> TimerC.Timer[unique("Timer")];

  MyAppM.Leds -> LedsC.Leds;

 


  txBytes = NoPacket.txBytes;

 


  NoPacket.ByteControl -> UART;

  NoPacket.ByteComm -> UART;

 


}

 


module MyAppM {

  provides {

interface StdControl;

   


  }

  uses {

interface Timer;

interface Leds;

interface StdControl as PhotoControl;

interface SendUART;

   


command result_t txBytes(uint8_t *bytes, uint8_t numBytes);

  }

}

implementation {

 


  /**

   * Toggle the red LED in response to the Timer.fired event. 


   * Start the Light sensor control and sample the data

   *

   * @return Always returns SUCCESS

   **/

  event result_t Timer.fired()

  {

call Leds.redToggle();   


// send message to UART (serial) port

if (call txBytes((uint8_t *)0x41,(uint8_t *)0x01) != 
SUCCESS)


  sending_packet = FALSE;

 


return SUCCESS;

  }

 


  command result_t StdControl.init() {

call Leds.init();

}

 


  command result_t StdControl.start() {

// Start a repeating timer that fires every 1000ms

return call Timer.start(TIMER_REPEAT, 1000);

  }

 


  /**

   * Halt execution of the application.

   * This just disables the clock component.

   *

   * @return Always returns SUCCESS

   **/

  command result_t StdControl.stop() {

return call Timer.stop();

  }

 





___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] Utilizing a command from another module,

[Mark Tsang]

But NoCRCPacket doesn't have an interface.  It looks to be a standalone
module.  Or am I missing something?

-Original Message-
From: Michael Schippling [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 17, 2008 5:43 PM
To: Mark Tsang
Cc: tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] Utilizing a command from another module,

look for documentation on NESC. Basically anything in the interface
for a module can be "call"ed from another module.
MS

Mark Tsang wrote:
> I was wondering how I would go about calling a command from another 
> module to utilize in my own module.  For instance, I want to use the 
> command "txBytes" in NoCRCPacket in my own program MyApp.  What do I 
> have to add in my program to do so.  I've read in other threads that I 
> need to wire NoCRCPacket to UART and I have done so, but I'm still 
> receiving the following error message during compilation:  NOTE:  I'm 
> calling txBytes in my Timer.fired command below in the module
> 
>  
> 
> In component `NoCRCPacket':
> 
> /opt/MoteWorks/tos/platform/micaz/NoCRCPacket.nc: In function
`receiveTask':
> 
> /opt/MoteWorks/tos/platform/micaz/NoCRCPacket.nc:306: Receive.receive 
> not connected
> 
>  
> 
>  
> 
> The error message isn't pointing to my program, instead the platform 
> file.  What am I doing wrong.  Thanks in advance!
> 
>  
> 
> configuration MyApp {
> 
>   provides {
> 
> command result_t txBytes(uint8_t *bytes, uint8_t
numBytes);
> 
>   }
> 
> }
> 
> implementation {
> 
>   components Main, MyAppM, TimerC, LedsC, NoCRCPacket as NoPacket, UART;
> 
>  
> 
>   Main.StdControl -> TimerC.StdControl;
> 
>   Main.StdControl -> MyAppM.StdControl;
> 
>   Main.StdControl -> NoPacket.Control;
> 
>  
> 
>   MyAppM.Timer -> TimerC.Timer[unique("Timer")];
> 
>   MyAppM.Leds -> LedsC.Leds;
> 
>  
> 
>   txBytes = NoPacket.txBytes;
> 
>  
> 
>   NoPacket.ByteControl -> UART;
> 
>   NoPacket.ByteComm -> UART;
> 
>  
> 
> }
> 
>  
> 
> module MyAppM {
> 
>   provides {
> 
> interface StdControl;
> 
>
> 
>   }
> 
>   uses {
> 
> interface Timer;
> 
> interface Leds;
> 
> interface StdControl as PhotoControl;
> 
> interface SendUART;
> 
>
> 
> command result_t txBytes(uint8_t *bytes, uint8_t
numBytes);
> 
>   }
> 
> }
> 
> implementation {
> 
>  
> 
>   /**
> 
>* Toggle the red LED in response to the Timer.fired event.

> 
>* Start the Light sensor control and sample the data
> 
>*
> 
>* @return Always returns SUCCESS
> 
>**/
> 
>   event result_t Timer.fired()
> 
>   {
> 
> call Leds.redToggle();   
> 
> // send message to UART (serial) port
> 
> if (call txBytes((uint8_t *)0x41,(uint8_t *)0x01) != 
> SUCCESS)
> 
>   sending_packet = FALSE;
> 
>  
> 
> return SUCCESS;
> 
>   }
> 
>  
> 
>   command result_t StdControl.init() {
> 
> call Leds.init();
> 
> }
> 
>  
> 
>   command result_t StdControl.start() {
> 
> // Start a repeating timer that fires every 1000ms
> 
> return call Timer.start(TIMER_REPEAT, 1000);
> 
>   }
> 
>  
> 
>   /**
> 
>* Halt execution of the application.
> 
>* This just disables the clock component.
> 
>*
> 
>* @return Always returns SUCCESS
> 
>**/
> 
>   command result_t StdControl.stop() {
> 
> return call Timer.stop();
> 
>   }
> 
>  
> 
> 
> 
> 
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Question about "Direct Parallel Access not defined"

[Ying Shang]

I am using MoteView and MoteWorks from Crossbow.
   
  I try to install Blink application to my sensor mote. I tried to use  "make 
mica2 reinstall mib520,com4", it has the following error: Who can help me with 
this issue?
   
  ==
  bash: [: /home/Ying: binary operator expected
ide.pl Ver:$Id: ide.pl,v 1.1.2.1 2006/05/29 07:22:52 lwei Exp $
Executing: /opt/MoteWorks/apps/general/Blink/ bash -c "make mica2 reinstall
mib520,com4"
cp build/mica2/main.srec build/mica2/main.srec.out
installing mica2 binary using mib520
uisp -dprog=mib520 -dserial=com4 --wr_fuse_h=0xd9 -dpart=ATmega128 --
wr_fuse_e=ff  --erase --upload if=build/mica2/main.srec.out
make: *** [program] Error 2
Direct Parallel Access not defined.
  ==

   
-
Never miss a thing.   Make Yahoo your homepage.___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Utilizing a command from another module,

[Michael Schippling]

I may have spoken out of turn but the 'provides' block in the T1 file is:


module NoCRCPacket {
  provides {
interface StdControl as Control;
interface BareSendMsg as Send;
interface ReceiveMsg as Receive;
interface SendVarLenPacket;

command result_t txBytes(uint8_t *bytes, uint8_t numBytes);
/* Effects: start sending 'numBytes' bytes from 'bytes'
*/
  }
  uses {
interface ByteComm;
interface StdControl as ByteControl;
interface Leds;
  }
}


Which seems to indicate that you could "call txBytes(...)" from your code,
but I'm resistant to becoming familiar with that special syntax.
If that doesn't work, then close study of the nesc doc is indicated.

MS


Mark Tsang wrote:

But NoCRCPacket doesn't have an interface.  It looks to be a standalone
module.  Or am I missing something?

-Original Message-
From: Michael Schippling [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 17, 2008 5:43 PM

To: Mark Tsang
Cc: tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] Utilizing a command from another module,

look for documentation on NESC. Basically anything in the interface
for a module can be "call"ed from another module.
MS

Mark Tsang wrote:
I was wondering how I would go about calling a command from another 
module to utilize in my own module.  For instance, I want to use the 
command "txBytes" in NoCRCPacket in my own program MyApp.  What do I 
have to add in my program to do so.  I've read in other threads that I 
need to wire NoCRCPacket to UART and I have done so, but I'm still 
receiving the following error message during compilation:  NOTE:  I'm 
calling txBytes in my Timer.fired command below in the module


 


In component `NoCRCPacket':

/opt/MoteWorks/tos/platform/micaz/NoCRCPacket.nc: In function

`receiveTask':
/opt/MoteWorks/tos/platform/micaz/NoCRCPacket.nc:306: Receive.receive 
not connected


 

 

The error message isn't pointing to my program, instead the platform 
file.  What am I doing wrong.  Thanks in advance!


 


configuration MyApp {

  provides {

command result_t txBytes(uint8_t *bytes, uint8_t

numBytes);

  }

}

implementation {

  components Main, MyAppM, TimerC, LedsC, NoCRCPacket as NoPacket, UART;

 


  Main.StdControl -> TimerC.StdControl;

  Main.StdControl -> MyAppM.StdControl;

  Main.StdControl -> NoPacket.Control;

 


  MyAppM.Timer -> TimerC.Timer[unique("Timer")];

  MyAppM.Leds -> LedsC.Leds;

 


  txBytes = NoPacket.txBytes;

 


  NoPacket.ByteControl -> UART;

  NoPacket.ByteComm -> UART;

 


}

 


module MyAppM {

  provides {

interface StdControl;

   


  }

  uses {

interface Timer;

interface Leds;

interface StdControl as PhotoControl;

interface SendUART;

   


command result_t txBytes(uint8_t *bytes, uint8_t

numBytes);

  }

}

implementation {

 


  /**

   * Toggle the red LED in response to the Timer.fired event.



   * Start the Light sensor control and sample the data

   *

   * @return Always returns SUCCESS

   **/

  event result_t Timer.fired()

  {

call Leds.redToggle();   


// send message to UART (serial) port

if (call txBytes((uint8_t *)0x41,(uint8_t *)0x01) != 
SUCCESS)


  sending_packet = FALSE;

 


return SUCCESS;

  }

 


  command result_t StdControl.init() {

call Leds.init();

}

 


  command result_t StdControl.start() {

// Start a repeating timer that fires every 1000ms

return call Timer.start(TIMER_REPEAT, 1000);

  }

 


  /**

   * Halt execution of the application.

   * This just disables the clock component.

   *

   * @return Always returns SUCCESS

   **/

  command result_t StdControl.stop() {

return call Timer.stop();

  }

 





___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] initialBackoff and congestionBackoff

[renjie huang]

Hi

What is the relationship between initialBackoff and congestionBackoff in
CC2420? In TinyOS-1.x, initialBackoff is smaller than congestionBackoff, but
in T2,  initialBackoff is larger value. I searched mailing list and some one
mentioned that usually initialBackoff is bigger than congestionBackoff.
Could anyone tell me what is the reason for that ? Thanks

-- 

  Renjie
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] initialBackoff and congestionBackoff

[Yiannis Yiakoumis]

renjie huang wrote:

Hi
 
What is the relationship between initialBackoff and congestionBackoff in 
CC2420? In TinyOS-1.x, initialBackoff is smaller than congestionBackoff, 
but in T2,  initialBackoff is larger value. I searched mailing list and 
some one mentioned that usually initialBackoff is bigger than 
congestionBackoff. Could anyone tell me what is the reason for that ? Thanks


--

  Renjie




InitialBackoff defines the window a packet uses when enters CSMA. After this period 
expires, and in case that the channel is occupied, CongestionBackoff defines the new 
window, which is smaller in order to give priority to congested packets rather than new 
ones. CSMA protocols use a binary exponential backoff to catch up with high contention, 
but TinyOS sets the exponent base to 1, thus keeping congestion window static.


Yiannis





___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] initialBackoff and congestionBackoff

[renjie huang]

Thanks Yiannis

On 3/17/08, Yiannis Yiakoumis <[EMAIL PROTECTED]> wrote:
>
>
>
> renjie huang wrote:
> > Hi
> >
> > What is the relationship between initialBackoff and congestionBackoff in
> > CC2420? In TinyOS-1.x, initialBackoff is smaller than congestionBackoff,
> > but in T2,  initialBackoff is larger value. I searched mailing list and
> > some one mentioned that usually initialBackoff is bigger than
> > congestionBackoff. Could anyone tell me what is the reason for that ?
> Thanks
> >
> > --
> >
> >   Renjie
> >
>
> InitialBackoff defines the window a packet uses when enters CSMA. After
> this period
> expires, and in case that the channel is occupied, CongestionBackoff
> defines the new
> window, which is smaller in order to give priority to congested packets
> rather than new
> ones. CSMA protocols use a binary exponential backoff to catch up with
> high contention,
> but TinyOS sets the exponent base to 1, thus keeping congestion window
> static.
>
> Yiannis
>
> >
> > 
> >
> > ___
> > Tinyos-help mailing list
> > Tinyos-help@millennium.berkeley.edu
> > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>



-- 

  Renjie
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] Utilizing a command from another module,

[Mark Tsang]

Exactly, I know that I'm able to call txBytes from my own code but I can't
seem to get it to work because of the error about a connection from within
NoCRCPacket explained below:  I've searched the documents for areas
regarding "calling a command from another module" but no luck.  Aside from
this being my 14th hour working on this project, could you please at least
direct me to the proper documentation that would explicitly explain the
syntax to make this command call.  Thanks!  I'm starting to run out of
ideas.

 In component `NoCRCPacket':

 /opt/MoteWorks/tos/platform/micaz/NoCRCPacket.nc: In function
 `receiveTask':
 /opt/MoteWorks/tos/platform/micaz/NoCRCPacket.nc:306: Receive.receive 
 not connected

-Original Message-
From: Michael Schippling [mailto:[EMAIL PROTECTED] 
Sent: Monday, March 17, 2008 9:27 PM
To: Mark Tsang
Cc: tinyos-help@millennium.berkeley.edu
Subject: Re: [Tinyos-help] Utilizing a command from another module,

I may have spoken out of turn but the 'provides' block in the T1 file is:

> module NoCRCPacket {
>   provides {
> interface StdControl as Control;
> interface BareSendMsg as Send;
> interface ReceiveMsg as Receive;
> interface SendVarLenPacket;
> 
> command result_t txBytes(uint8_t *bytes, uint8_t numBytes);
> /* Effects: start sending 'numBytes' bytes from 'bytes'
> */
>   }
>   uses {
> interface ByteComm;
> interface StdControl as ByteControl;
> interface Leds;
>   }
> }

Which seems to indicate that you could "call txBytes(...)" from your code,
but I'm resistant to becoming familiar with that special syntax.
If that doesn't work, then close study of the nesc doc is indicated.

MS


Mark Tsang wrote:
> But NoCRCPacket doesn't have an interface.  It looks to be a standalone
> module.  Or am I missing something?
> 
> -Original Message-
> From: Michael Schippling [mailto:[EMAIL PROTECTED] 
> Sent: Monday, March 17, 2008 5:43 PM
> To: Mark Tsang
> Cc: tinyos-help@millennium.berkeley.edu
> Subject: Re: [Tinyos-help] Utilizing a command from another module,
> 
> look for documentation on NESC. Basically anything in the interface
> for a module can be "call"ed from another module.
> MS
> 
> Mark Tsang wrote:
>> I was wondering how I would go about calling a command from another 
>> module to utilize in my own module.  For instance, I want to use the 
>> command "txBytes" in NoCRCPacket in my own program MyApp.  What do I 
>> have to add in my program to do so.  I've read in other threads that I 
>> need to wire NoCRCPacket to UART and I have done so, but I'm still 
>> receiving the following error message during compilation:  NOTE:  I'm 
>> calling txBytes in my Timer.fired command below in the module
>>
>>  
>>
>> In component `NoCRCPacket':
>>
>> /opt/MoteWorks/tos/platform/micaz/NoCRCPacket.nc: In function
> `receiveTask':
>> /opt/MoteWorks/tos/platform/micaz/NoCRCPacket.nc:306: Receive.receive 
>> not connected
>>
>>  
>>
>>  
>>
>> The error message isn't pointing to my program, instead the platform 
>> file.  What am I doing wrong.  Thanks in advance!
>>
>>  
>>
>> configuration MyApp {
>>
>>   provides {
>>
>> command result_t txBytes(uint8_t *bytes, uint8_t
> numBytes);
>>   }
>>
>> }
>>
>> implementation {
>>
>>   components Main, MyAppM, TimerC, LedsC, NoCRCPacket as NoPacket, UART;
>>
>>  
>>
>>   Main.StdControl -> TimerC.StdControl;
>>
>>   Main.StdControl -> MyAppM.StdControl;
>>
>>   Main.StdControl -> NoPacket.Control;
>>
>>  
>>
>>   MyAppM.Timer -> TimerC.Timer[unique("Timer")];
>>
>>   MyAppM.Leds -> LedsC.Leds;
>>
>>  
>>
>>   txBytes = NoPacket.txBytes;
>>
>>  
>>
>>   NoPacket.ByteControl -> UART;
>>
>>   NoPacket.ByteComm -> UART;
>>
>>  
>>
>> }
>>
>>  
>>
>> module MyAppM {
>>
>>   provides {
>>
>> interface StdControl;
>>
>>
>>
>>   }
>>
>>   uses {
>>
>> interface Timer;
>>
>> interface Leds;
>>
>> interface StdControl as PhotoControl;
>>
>> interface SendUART;
>>
>>
>>
>> command result_t txBytes(uint8_t *bytes, uint8_t
> numBytes);
>>   }
>>
>> }
>>
>> implementation {
>>
>>  
>>
>>   /**
>>
>>* Toggle the red LED in response to the Timer.fired
event.
> 
>>* Start the Light sensor control and sample the data
>>
>>*
>>
>>* @return Always returns SUCCESS
>>
>>**/
>>
>>   event result_t Timer.fired()
>>
>>   {
>>
>> call Leds.redToggle();   
>>
>> // send message to UART (serial) port
>>
>> if (call txBytes((uint8_t *)0x41,(uint8_t *)0x01) != 
>> SUCCESS)
>>
>>   sending_packet = FALSE;
>>
>>  
>>
>> return SUCCESS;
>>
>>   }
>>
>>  
>>
>>   command result_t StdControl.init() {
>>
>> call Leds.init();
>>
>> }
>>
>>  
>>
>>   command result_t StdControl.start() {
>>
>> // Start a repeating timer that fires every 1000ms
>>
>> return call Timer.start(TIMER_REPEAT, 1000);
>>
>>   }
>>
>>  
>

Re: [Tinyos-help] Reset Button

[Bastien Mainaud]

Hi

tinyos-2.x/tos/lib/TOSBoot/msp430/HardwareC.nc must be useful for the 
reset function.


Bastien

Ittipong Khemapech wrote:

Hi,

Any way that I can restart a mote by coding instead of pressing reset 
button? I've search mailing list and found that ResetC.nc may be useful. 
Unfortunately, I can't find the file.


I'm using:

Tmote Sky and Invent
TinyOS 2.x
Windows XP & cygwin

Many thanks in advance.

Ittipong




___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help