At 16:30 +1200 4/1/03, Bernard Mentink wrote:
You might also want to look at NESOS, it is a state-machine OS which
works really well on the MSP430. All process comms is done with
packets that re-use RAM so you need very little ram to run with. It
also only takes 4K of flash for the OS.
See : http://home.eunet.no/~jen/nenesos.html
Yes, I've seen that before, and NESOS will certainly appeal to a
certain class of users.
While I have not implemented anything with NESOS, your numbers above
and my quick perusal of the source code lead me to believe that
Salvo's RAM and ROM footprints will be considerably smaller, and thus
more suitable to MSP430's, especially the smaller ones.
A typical ROM (Flash) footprint with a Salvo -t library (all
features, including priority-based multitasking, delays, events and
timeouts) will be on the order of 1.5-2 K.
A typical RAM footprint will be 10 bytes of RAM per task, 4 bytes of
RAM per event, and a few (8-10?) bytes of globals. Stack usage is no
different from conventional "main-loop" applications, i.e. there is
not a per-task stack requirement.
Regards,
--
______________________________________
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
