On Mon, May 18, 2009 at 07:34:57AM -0400, Bruno L. Albrecht wrote:
> why don't you try some state machines?

A RTOS is supposed to make guarantees on the latency of processing a task
or an event.

The biggest problem with SW and all his question is that he never gives
sufficient background as to what he's doing to give the question meaningful
context.

There are CS and Engineering people here on the list that have decades of
experience and education that SW could leverage if he'd start asking the
right questions. Design isn't about tools and toys. It's about understand
what you need to get done, and how to leverage the available tools to do
it.

So whether it's a RTOS, or a state machine, or an event loop doesn't really
matter. Tell us what you are trying to accomplish and then the available
tools start to make more sense.

BAJ

> 
> On Mon, May 18, 2009 at 6:32 AM, Tamas Rudnai <tamas.rudnai@gmail.com>wrote:
> 
> > On Mon, May 18, 2009 at 9:05 AM, Jan-Erik Soderholm <
> > jan-erik.soderholm@telia.com> wrote:
> >
> > > Besides, even an RTOS can't do more than one thing "at once"...
> > >
> >
> > Of course, you have one core anyway. But it could help you to think as
> > threads were running parallel. It is just a different abstraction to
> > interrupts or polling methods on a non rtos system.
> >
> > Like an event driven rtos 'thinks' that a change on a pin is an event when
> > a
> > process has to be triggered to run. On a cooperative rtos the thread waits
> > for the pin change and till the thread is suspended. On a preemptive you
> > can
> > poll the pin without suspending the thread (and the entire mcu) -- all of
> > them are doing the same basically with different way of thinking (and of
> > course of different overhead on it). One could help to approach a specific
> > problem better, the other one fits worse/better to many other related
> > functions. But of course there is no rtos that makes you possible to write
> > a
> > firmware that was impossible on the bare silicon.
> >
> > Tamas
> > --
> > http://www.mcuhobby.com
> > --
> > http://www.piclist.com PIC/SX FAQ & list archive
> > View/change your membership options at
> > http://mailman.mit.edu/mailman/listinfo/piclist
> >
> -- 
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist