|
||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||
|
|
by Dr. Barry Henderson
Power Management Analysis Immediately after initialization has been finalized we should force the DSP to enter either sleep or deep sleep mode. Sleep mode can be exited by either the occurrence of a peripheral event {generating an interrupt say} or by a timeout event upon which a specific re-enabling sequence of instructions would be executed. The DSP would then transition quickly either to full on {assume PLL pre-programmed, on but disabled}, active, or relaxed mode depending upon how critical the required activity is. After the event has been serviced and all associated processing completed, the DSP would transition back to sleep mode. Deep sleep mode can only be exited by a reset or an RTC event, and would then take several clock cycles to enable and stabilize the PLL from its off state. This mode would only entered when we know that processing events are going to be absent for a prolonged time period.
Each essential operation would then be performed at the slowest feasible clock speed. This would mean trying to run the DSP with the PLL turned off in either the processors relaxed or active modes whenever possible, to maximize power savings. In relaxed and active modes the actual DSP clock speed is a mere fraction of its normal operating frequency {and Power}, i.e. CLKIN/2. Substantial benchmarking and code profiling may well be necessary to ensure that all timing criterion are still met when processing each event.
Conclusion
References Real-Time Processing Using DSPs, FPGAs & uCs Archive Guides and Experts Analog Avenue EDA Tools PLD DSP EDA Embedded Systems Power Test
|
|||||||||||||||||||||||||||||||||||
|
Copyright © 2003 ChipCenter-QuestLink About ChipCenter-Questlink |
||||||||||||||||||||||||||||||||||||