[Tinyos-devel] problem with msp430 spi unconfigure.
Vlado Handziski
handzisk at tkn.tu-berlin.de
Mon May 12 17:41:48 PDT 2008
I think that we should return the normal power manager to the USARTs (that
was removed in some of the refactoring) and deal with this there. When there
is no PM, the unconfigure should indeed leave the module in reset to
minimize the consumption, however, I vaguely remember that we checked with a
scope that the difference was almost undetectable.
Vlado
2008/5/9 Eric Decker <cire831 at gmail.com>:
> async command void ResourceConfigure.unconfigure[ uint8_t id ]() {
> call Usart.resetUsart(TRUE);
> call Usart.disableSpi();
> call Usart.resetUsart(FALSE);
> }
>
>
> The above is from tos/chips/msp430/usart/Msp430SpiNoDmaP.nc and I suspect
> other spi modules
> but I haven't looked. I suspect the last call Usart.resetUsart(FALSE) of
> being a problem. It
> will leave the Usart in a running state.
>
> I would think that the Usart should be left reset if it is unconfigured.
>
> eric
>
>
>
> _______________________________________________
> Tinyos-devel mailing list
> Tinyos-devel at millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-devel/attachments/20080513/89028fe7/attachment.htm
More information about the Tinyos-devel
mailing list