It is micaz mote.

I have dug further. It seems that whenever I run PortE6.makeOutput()
(in order to make the E4 pin an output pin), the radio gets stuck
(i.e., the radio communication stops). I can use, without problem,
Ports E4 (INT0), E5 (INT1), E7 (INT3). It is the INT2 that is causing
problem.

BTW, where did you find that the radio interrupts are on INT0 and
INT1? I tried to search this kind of information, but other than the
Xbow user manual at
http://www.xbow.com/Support/Support_pdf_files/MPR-MIB_Series_Users_Manual.pdf
(which show GPIO pins to be usable), I found nothing.

On Thu, Dec 4, 2008 at 7:07 PM, Varun Jain <[EMAIL PROTECTED]> wrote:
> Hi Saikat,
> Can you give more info about your environment?? Which motes, radio,
> etc??
>
> I am using Micaz, so it might be possible that it interferes with the
> Radio. Because the Radio Interrupt (FIFO and FIFOP for CC2420) is
> defined on INT0 and INT1. I would recommend that you use other ports for
> GPIO purpose. I have used other GPIO pins and it does not interfere with
> the radio operation.
>
> Cheers,
> Varun
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Saikat
> Ray
> Sent: Friday, December 05, 2008 1:52 AM
> To: [email protected]
> Subject: [Tinyos-help] GPIO and radio
>
> HI,
>
> Do the GPIO pins (INT0-INT3) somehow interfere with the radio? I am
> creating a square wave from each of the pins (by using, say,
> PortE4.set() and PortE4.clr() alternately in a timer.fired()
> function). However if the square wave is on, then the radio does not
> seem to receive packets. Any input is appreciated.
>
> Thanks in advance.
> _______________________________________________
> Tinyos-help mailing list
> [email protected]
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>



-- 
Saikat Ray
Web: http://raysaikat.googlepages.com
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to