[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [avr-libc-dev] Calls to eeprom_write_block on CAN64 increase sleepcu
|
From: |
Weddington, Eric |
|
Subject: |
RE: [avr-libc-dev] Calls to eeprom_write_block on CAN64 increase sleepcurrent? |
|
Date: |
Thu, 14 May 2009 14:40:55 -0600 |
> -----Original Message-----
> From: Bob Paddock [mailto:address@hidden
> Sent: Thursday, May 14, 2009 2:36 PM
> To: Weddington, Eric
> Cc: address@hidden
> Subject: Re: [avr-libc-dev] Calls to eeprom_write_block on
> CAN64 increase sleepcurrent?
>
> > So you're saying that the current goes up to 1.1 mA and
> *stays there*, even when the eeprom write is finished?
>
> I found that the problem was, that I was putting the part to sleep
> *before* the EEPROM write finished, then
> the current does stay at 1.1 mA. Addeding eeprom_busy_wait() after
> the block write fixed the problem.
>
> I'm guessing the internal EEPROM oscillator misses the command to go
> to sleep while it is busy.
You're probably right.
Glad you found a solution. :-)