RE: More playing around with RTOS, to task or not to task

DAB — Fri, 01 Jul 2011 22:59:48 GMT

I built many a embedded system without a "standard" operating system. I found that unless you have a large quantity of threads operating in a non determanistic fashion, you can usually get by with a very simple approach using flags and calls. Part of my "roll your own" approach was dictated by the entire lack of available OS when I began building embedded systems.

When OS options became available, we mostly had to deal with the limitations impossed by the OS rather than the benefits provided by the OS. Even for production systems, most commercial OS just did not provide enough value added to make it worth using them, not to mention that most wanted a license fee, or as I called it, an extortion fee.

To work out scheduling issues, I developed a simulation that let me model a system and its OS to assess if it could handle the realtime requirements of a given application. It provided data similar to Rate Monotonic Analysis, but it let you see the more subtle dynamic interactions between multiple processors in either a distributed or parallel environment.

Bottom line, keep it simple.

This does not mean I would dismiss a commercial OS from your project, but for most hobbiest and small projects, they are a lot more overkill than you need.

As long as you stay focussed upon the data flow and processing requirements of each thread, you can build a very complex multitasking system without incurring onerous delays that some standard OS forces on your implementation to keep your application "portable."

Thanks,

DAB