AR# 3092: Foundation F1.3 State Editor: when selecting HOLD for Unsatisfied Conditions, selection not kept.
AR# 3092
Foundation F1.3 State Editor: when selecting HOLD for Unsatisfied Conditions, selection not kept.
説明
Keywords: state editor, fsm, undefined, hold
Urgency: Standard
General Description: In F1.3 State Editor, using VHDL encoding, when user edits Unsatisfied Conditions to be handled as a HOLD: (RClick w/in State Machine window -> Properties -> Defaults -> Unsatisfied Conditions), the HOLD selection appears to be accepted. But if the user goes back into the same window after applying HOLD to the state machine, the selection has changed to Don't Care. In F1.3 State Editor-VHDL encoding, when user edits Unsatisfied Conditions to be handled as a HOLD (RClick w/in State Machine window -> Properties -> Defaults -> Unsatisfied Conditions), the HOLD selection appears to be accepted. But if user goes back into same window after applying to state machine, the selection has changed to Don't Care.
ソリューション
In VHDL, the two choices, HOLD and Don't Care, have the same functionality. The HOLD choice, if fully implemented, would add a line to each 'case' choice: case State_machine is when S1 => if i=1 then State_machine <= S2; else State_machine <= S1; --This line is due to HOLD
when S2 => ...
The line introduced by HOLD is redundant. Without it, the same action is implied. F1.3 writes the VHDL code the same, regardless of the two choices.