AVR-Chat

At 11:50 PM 4/9/05 -0500, Chuck Hackett wrote:
> > From: Larry Barello [mailto:yahoo@barello.net]
> >
> > ....
> > Most (but not all) of my current projects use a foreground loop with Finite
> > State Machine (FSM) tasks and a high speed timer interrupt that increments
> > counters or runs additional FSM that need precise periodic execution (e.g.
> > motor or sensor control/input tasks, filtering, etc)  That structure is
> > pretty simple and works well for just about everything. ....
>
>On larger systems in a previous life I wrote a FSM "compiler" that consumed a
>description of a state machine and produced a set of tables and source code
>which was compiled into a communications application.  Support libraries
>included debugging/trace tools that allowed symbolic debugging of a FSM.  Has
>anyone done something like this for embedded C?


I know of a couple of commercial products

         BetterState from Wind River
         VisualState from IAR

Neither are cheap and both are dongled (Flexlm).  Both generate ANSI C. I 
use BetterState myself.  Both use UML statecharts as there source (and 
provide graphical editors).  I prefer BetterStates generation which allows 
in lines condition tests over VisualStates which insists everything be 
converted to an event first.

Robert

" 'Freedom' has no meaning of itself.  There are always restrictions,   be 
they legal, genetic, or physical.  If you don't believe me, try to chew a 
radio signal. "  -- Kelvin Throop, III
http://www.aeolusdevelopment.com/