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

[Murray, Ben]

> > With the BOD disabled I get the same results as originally posted  
> > (hundreds
> > of uA at 3.0V, hundreds or tens of uA in the 2.5-2.8V 
> region, <10uA  
> > at about
> > 2.3-2.4V, and hundreds again at 2.1-2.2V) With BOD fully enabled
> > (wr_fuse_l=24) the current stuck at around 8-9mA (note: mA, 
> not uA)  
> > and with
> > it part-enabled (wr_fuse_l=A4) the same pattern as the 
> original was  
> > observed
> > between 2.7-3.0V but at anything less than 2.7V the current jumps  
> > up to the
> > several-mA region.
> >
> 
> I ran tests on some micaZs here and didn't see the same 
> behavior. The  
> current jumped to the mA region at about 2.2V, but before that point  
> was 2-6uA.
> 
> Other folks in core who have micazs are going to test them.
> 
> Phil 
> 

Thanks for trying...I thought it'd just be me!

...but I have no idea why. Dodgy motes aside, are there any other settings
aside from the fuses that might be interfering with mcusleep.sleep? Perhaps
something setting an interrupt that shouldn't be, or something I have failed
to initialise?

Standard T2 install, unmodified makefiles, unmodified .nc files.

can I ask what your default fuse settings are for fuse_h fuse_l and fuse_e?


Ben

*******************************************************************************
Please consider the environment before printing this email.
*******************************************************************************
This email and any files transmitted with it are intended solely for the use of
the individual or entity to whom they are addressed and may not be divulged to
any third party without the express permission of the originator.  Any views
expressed in this message are those of the individual sender, except where the
sender specifically states them to be the views of Thales Research & Technology
(UK) Limited.
*******************************************************************************