Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #28747
| From | "A.P.Richelieu" <aprichelieu@gmail.com> |
|---|---|
| Newsgroups | comp.arch.embedded |
| Subject | Re: FSM - Mealy vs. Moore |
| Date | 2019-08-11 08:10 +0200 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <qiobgb$1o9e$1@gioia.aioe.org> (permalink) |
| References | <1b76b8b1-538a-448d-92e9-161827d1427f@googlegroups.com> |
Den 2019-08-11 kl. 00:21, skrev Rick C: > I'm discussing Finite State Machine (FSM) design in logic with some hardware folks and I thought I'd ask what a software community thinks. > > Moore - outputs are only a function of the state. > > Mealy - outputs are a function of both inputs and state. > > So considering this issue, it seems it comes down to as Wikipedia says, "In Mealy machines, input change can cause output change as soon as logic is done" while Moore machines outputs don't change until the clock. > > In software, I was thinking this distinction is meaningless since the clock, for all practical purposes, is equivalent to entering the code for the FSM. In this case one does not need to concern with the issue of an output changing immediately without being clocked... > > But then that really is not the distinction that this classification is intended to address. The distinction is that the outputs of the Moore FSM are only dependent on the state while the Mealy outputs depend on the input as well and so effectively the outputs are part of the state even if the next state does not depend on them. > > I guess it is a bit different in software than hardware because effectively all inputs and outputs are clocked. > > As much as anything, I was thinking out loud here. But feel free to comment. > There is no difference between S/W and H/W. Most hardware today is described with software. When you program in Verilog or VHDL you can implement both Moore and Mealy statemachines. When you program in procedural languages, you can drive a statemachine with a clock tick or in a loop, but you can still change the output by taking an interrupt when an input is toggled. AP
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
FSM - Mealy vs. Moore Rick C <gnuarm.deletethisbit@gmail.com> - 2019-08-10 15:21 -0700
Re: FSM - Mealy vs. Moore Paul Rubin <no.email@nospam.invalid> - 2019-08-10 18:08 -0700
Re: FSM - Mealy vs. Moore Rick C <gnuarm.deletethisbit@gmail.com> - 2019-08-10 19:00 -0700
Re: FSM - Mealy vs. Moore "A.P.Richelieu" <aprichelieu@gmail.com> - 2019-08-11 08:10 +0200
Re: FSM - Mealy vs. Moore Rick C <gnuarm.deletethisbit@gmail.com> - 2019-08-10 23:28 -0700
Re: FSM - Mealy vs. Moore Richard Damon <Richard@Damon-Family.org> - 2019-08-12 08:04 -0400
Re: FSM - Mealy vs. Moore Rick C <gnuarm.deletethisbit@gmail.com> - 2019-08-12 07:05 -0700
Re: FSM - Mealy vs. Moore Richard Damon <Richard@Damon-Family.org> - 2019-08-12 22:19 -0400
Re: FSM - Mealy vs. Moore Rick C <gnuarm.deletethisbit@gmail.com> - 2019-08-12 22:27 -0700
Re: FSM - Mealy vs. Moore Richard Damon <Richard@Damon-Family.org> - 2019-08-14 23:13 -0400
Re: FSM - Mealy vs. Moore Rick C <gnuarm.deletethisbit@gmail.com> - 2019-08-14 21:05 -0700
Re: FSM - Mealy vs. Moore Richard Damon <Richard@Damon-Family.org> - 2019-08-16 21:22 -0400
Re: FSM - Mealy vs. Moore Rick C <gnuarm.deletethisbit@gmail.com> - 2019-08-16 20:15 -0700
Re: FSM - Mealy vs. Moore Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2019-08-12 10:12 -0400
csiph-web