Lpc2000

> 3.  If app can afford 4096+ clk dly post interrupt, enter Power 
Down in RTOS 
> idle loop.  Wakeup condition via external interrupt.  Be sure to 
read the 
> Wakeup Timer section in UM_LPC21XX_LPC22XX_2.pdf

I don't think I can use power down mode, because I need to wake up 
upon new character arrive at the UARTs. Here's my reasoning, please 
correct me if I'm wrong: I think the UARTs are off on power down 
mode, so even if I externally cheat an interrupt at the character's 
start bit, the UART wouldn't wake up fast enough to receive the 
character (at 57600 bauds). It would take at least ~410 µS to wake up 
with a 10 MHz xtal. One bit at 57600 is ~17µS.

Guille

--- In lpc2000@yahoogroups.com, "Joel Winarske" <joelw@i...> wrote:
> > Thanks. Looks mostly like what I need. I'd like to make the OS to
> > enter a slower tick rate when there's no more processing to do, 
but
> > this change looks trivial if all other issues are taken care of.
> 
> Some more ideas for software power savings:
> 1.  Power off each peripheral not in use.  Control on the fly.
> 
> 2.  Enter idle mode in your RTOS idle loop.  Idle mode stops the 
processor 
> clock, but peripherals stay up.  This is a similar to power 
consumption of a 
> DC light controlled via PWM.
> 
> 3.  If app can afford 4096+ clk dly post interrupt, enter Power 
Down in RTOS 
> idle loop.  Wakeup condition via external interrupt.  Be sure to 
read the 
> Wakeup Timer section in UM_LPC21XX_LPC22XX_2.pdf