[Tinyos-devel] tmote P3.6 / P3.7 direction

[David Moss]

To be implemented properly, the library implements this needs to catch and
handle the interrupt that signals the mote has been connected or
disconnected from USB power.

 

-David

 

 

  _____  

From: Geoffrey Werner-Allen [mailto:geoffrey.werner.allen at gmail.com] 
Sent: Wednesday, July 02, 2008 3:28 PM
To: Philip Levis
Cc: David Moss; tinyos-devel at millennium.berkeley.edu
Subject: Re: [Tinyos-devel] tmote P3.6 / P3.7 direction

 

Good point; that's correct.

-gwa-

geoffrey werner-allen :: 617.694.7261 :: www.eecs.harvard.edu/~werner 

On Wed, Jul 2, 2008 at 6:25 PM, Philip Levis <pal at cs.stanford.edu> wrote:


On Jul 2, 2008, at 3:22 PM, Geoffrey Werner-Allen wrote:

Phil:

IIRC on the TMote one of the USB power lines controls whether or not the
serial input buffer is active.  If it's active it's driving the line feeding
into Port 3.7 and if the port isn't configured to catch it, then you have
the port conflict causing unnecessary power consumption and possible lockup.
Currently the serial stack sets up 3.7, so if its not included and the mote
is plugged in to USB, you have the problem.  I don't think the ordering of
reprogramming/plugging in matters, just the inclusion of the serial stack in
the running binary and whether or not the mote is plugged in to USB.  Does
that make sense?

 

It does; I was commenting on David's solution, which proposed sensing
whether a mote was plugged in or not. So if a mote started not plugged in,
but then was plugged in (with no serial stack), then it would leak current,
right?

Phil

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-devel/attachments/20080702/f5e43530/attachment.htm