Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
There's no reason I can think of why you need to know if it's Mealy or Moore. In all my years of working with state machines, I have never, ever, given a thought to that.
Look up the definition; one of them has the output a function of both present state and inputs; the other has the output depend only on the present state.
@barry There's no reason I can think of why you need to know if it's Mealy or Moore. In all my years of working with state machines, I have never, ever, given a thought to that.
+1
Neither do I, but in the university there are such exercises given to the students I guess.
The style of VHDL presented by the OP is also antiquated (clk'event and clk='1', encodings for curr_state and next_state, etc.). I has used such a SM VHDL coding style last back in 2008/2009, and it was most probably due to some limitations of the Simulation or Synthesis tool (cannot remember correctly).
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
