Steve wrote:
The tasker code in examples, is function but very basic. Oleg's SOS is rather more functional, but doesn't really address the needs of an MSP430 user - it does nothing about power management. I spent some idle moments today trying to formulate what an MSP430 kernel should really be like. It certainly needs to sit in a lower state as much as possible. That means it needs to be very event oriented. The manner in which it sleeps when there are no active events also needs to be controllable, to maintain appropriate response times. I'm wondering how well automatic control over going into LPM0 or LPM3 would work. It could be adapted according to the delay until the next timed event, but it couldn't take account of external interrupts. Has anyone else been thinking along these lines?
FYI, because the Salvo RTOS is purely event-driven, it handles all of the LPM issues innately -- you just enter whichever LPM you want from within OSIdlingHook(), and you forcibly disable LPM on exit from the associated ISRs ... once the scheduler is done with the event, the application will find itself back in OSIdlingHook(), and LPM will be invoked.
In the Latest News page on our website there's a PDF of our TI 2003 MSP430 ATC conference presentation, and it has code examples of LPM stuff.
-- ______________________________________ Andrew E. Kalman, Ph.D. Salvo(TM), The RTOS that runs in tiny places(TM) Pumpkin, Inc. 750 Naples Street San Francisco, CA 94112 tel: (415) 584-6360 fax: (415) 585-7948 web: http://www.pumpkininc.com email: a...@pumpkininc.com
