Sep 26, 2007 #1 B bharat_in Member level 4 Joined Oct 5, 2006 Messages 78 Helped 9 Reputation 18 Reaction score 7 Trophy points 1,288 Activity points 1,716 Just a concern about output signal generation from FSM... Can we use current_state and next_state signals for particular output signal generation? // cosider below FSM is based on one-hot encoding :| e.g. fsm_out = ( !cur_state[7] && next_state[7]); Is it bad coding style? If Yes, then why?
Just a concern about output signal generation from FSM... Can we use current_state and next_state signals for particular output signal generation? // cosider below FSM is based on one-hot encoding :| e.g. fsm_out = ( !cur_state[7] && next_state[7]); Is it bad coding style? If Yes, then why?
Sep 27, 2007 #2 T Thinkie Full Member level 3 Joined May 26, 2005 Messages 177 Helped 18 Reputation 36 Reaction score 4 Trophy points 1,298 Activity points 2,242 FSM outputs This sort of makes a "mealy" kind of state machine. It is not necessary bad, but you should be aware that this signal is generated asynchronously and directly depends on inputs (if next state depends on inputs)
FSM outputs This sort of makes a "mealy" kind of state machine. It is not necessary bad, but you should be aware that this signal is generated asynchronously and directly depends on inputs (if next state depends on inputs)