fix Delay3PatchFSM: init issue (JIRA ESSURF-24) #1089
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixing init bug of the delay3PatchFSM
Description
I added an additional step named CHECK_CNT_S. IT handles the logic previously located in the IDLE_S state. Then, the IDLE_S has been changed to wait for a load command. The FSM goes to CHECK_CNT_S after loading where the logic check if the CNTINVALUE has to be inc/dec. Finally, if the FSM has reached the expect value, it goes back to IDLE_S and wait for a new LOAD_S.
Details
Side effect: no new value can be load until busy signal goes back to low.
JIRA
ESSURF-24