[Tinyos-host-mote-wg] Re: [Tinyos-2.0wg] Power Management

[Joe Polastre]

The microcontroller can't know which pins to change; only the device
drivers know (ie, the radio knows that it should revert its pins to
minimize power consumption when the radio is off).  As each component
turns off, they should be responsible for setting their pins in the
correct orientations.

The only way a port pin would change on every interrupt is if the
software chose to do so (there are rare exceptions to this, such as
the supply voltage supervisor on the msp430, but those pins do not
affect power consumption).

When did you run into this questions and why?  I couldn't find any
reference to it in the notes.

If you can work out how to start and stop components, the pin
management follows automatically (and this policy of turning your pins
off when you're done actually DOES work in TinyOS 1.x!)

-Joe

On 9/30/05, Philip Levis <pal at cs.stanford.edu> wrote:
>
> On Sep 30, 2005, at 5:54 PM, mturon at xbow.com wrote:
>
> >
> > Also, there is an interesting paragraph in the data sheet that
> > makes me think we should revisit the pin management discussion:
> >
> >
> >
> > Port Pins (pg. 45)
> >
> >
> >
> > When entering a sleep mode, all port pins should be configured to
> > use minimum power.  The most important thing is then to ensure that
> > no pins drive resistive loads….
> >
> >
> Can you give an example of a pin whose state you would want to change
> on every interrupt? I think this was the question we ran into.
>
> Phil
> _______________________________________________
> Tinyos-2.0wg mailing list
> Tinyos-2.0wg at Mail.Millennium.Berkeley.EDU
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg
>

_______________________________________________
Tinyos-2.0wg mailing list
Tinyos-2.0wg at Mail.Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg