[Tinyos-devel] more bugging about current consumption on Mica Z in tinyos-2.x

[Philip Levis]

On Aug 1, 2007, at 3:00 AM, Murray, Ben wrote:

> Current spikes:
> sounds feasible as I'd have thought the Mcu would have to partially  
> wake,
> check the taskloop and then go back to sleep? I seem to recall reading
> somewhere that McuSleep.sleep() only puts the Mcu into a sleep mode  
> for a
> short while (something like tens of ms?) I'll try grab a scope at  
> some point
> to see if it's these spikes causing at least some of the current  
> rise I'm
> witnessing.
>
> As an aside - is there a way I can control how long the MCU sleeps for
> having received the McuSleep commad?

It'll sleep until an interrupt. So you can schedule an interrupt to  
occur...

<snip>

> I've also just installed the newer tos 2.0.2 (and the new tools  
> rpm) - same
> results as before.
>
> also... I'm not entirely certain what the other clock source options
> actually do yet from within wr_fuse_l ...could that be my problem?  
> x?4 means
> internal oscillator I believe. I'll post the make output below:

I'll take a look today. My best guess is that there's a floating pin  
or two?

Phil