I have two cristals, 1.8432 MHz external clock an 32kHz on TOSC. When i go into "SLEEP_MODE_EXT_STANDBY" current falls to about 0,50 mA and 0,48 mA is consumed by clock.
My question is - how to turn off clock during sleep and is it possible to start clock from atmega64 ?
My question is - how to turn off clock during sleep and is it possible to start clock from atmega64 ?
michalnow wrote:Did you read the chapter on sleep and specifically the table showing you the various sleep modes available. The more intense form of sleeping involve stopping more and more of the clocks but (generally) they are more difficult to wake up as there are fewer reactivation interrupts.My question is - how to turn off clock during sleep and is it possible to start clock from atmega64 ?
I did. This clock is controlled with its enable pin. I need some possibility to put it to logical 0 to turn it off, and back to 1 to turn it on. Problem is - program will stop if i turn off clock before sleep, and will not continue before it comes back (As far as I know !).
Maybe whatever signal wakes up the AVR can also set the XTAL enable high...it could be wired or'd so that then the AVR can force it to stay high, even if the signal goes away.
you didn't mention exactly what wakes things up. If it is timer2 & the 32K xtal, this might help
It is not possible to change clock source on a mega64.
You could switch off the external clock when you first go to sleep.
But you can never wake up !!!
Surely it is easier to use the internal 2MHz RC.
It can sleep and wake up.
It will give you "good enough" accuracy for UART comms and most peripherals.
Obviously Timers will not be as accurate as with a crystal.
Your 32kHz TOSC can give you accurate RTC functionality. You can even use the TOSC to calibrate the 2MHz RC.
Modern MCUs can switch clock source at run time e.g. from RC to crystal
The mega64 (and traditional Mega AVRs) can only select clock source by fuses.
David.
The mega64 (and traditional Mega AVRs) can only select clock source by fuses.
I'd speculate from the OP that the purpose of this snipe hunt is to minimize power consumption, and thus the clock contortions.
IME/IMO, if this is a primary concern, then use an AVR model with better characteristics. Indeed you can haul gravel with a pickup truck, but you will never do a good job of it.
Choosing a more modern AVR8 model, even if not a late generation that can change cl0ock sources, will draw less power in all modes. In addition, the wake-on-pin-change allows a common wakeup trigger to be used, and the AVR draws next to nothing in powerdown sleep.
program will stop if i turn off clock before sleep
As far as turning the osc off, you can use an RC to delay the turning off by a few ms...that's 1/2 of the issue.
I have two cristals, 1.8432 MHz external clock an 32kHz on TOSC. When i go into "SLEEP_MODE_EXT_STANDBY" current falls to about 0,50 mA and 0,48 mA is consumed by clock
Is that .5ma/.48ma or is it 50ma/48ma? Big difference
If the first, then its operating correctly. .5ma, or 500microamps is nothing.
50ma on the other hand is too high for sleep mode.
My question is - how to turn off clock during sleep and is it possible to start clock from atmega64 ?
You are using an external oscillator with an enable pin. Why? And why would you want the AVR to turn off its clock?
As others have been guessing it looks like you want to operate on the 32khz crystal while in sleep and hen kick it into high gear when awake. There are numerous threads on how fast a clock should be used for maximum battery life etc.
Before this thread turns into a long winding road of frustration can you explain your thinking on this dual crystal/oscillator setup?
JIm
