Change "done" mechanism to be tolerant to Single Event Upsets. #17
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.
This changes how the
true_done
flag is calculated:true_done
might never be set and as such the FSM can stall the accelerator. At the same timetrue_done
can not just bedone
from the input since that might be set on reset.To solve this, make
true_done
assert on the rising edge ofdone
input.(A fault-tolerant accelerator should continuously asserts
done
and then has the guarantee that this will eventually be forwarded).true_done
output itself might also experience a single event upset in just the cycle where it is asserted and thus done signal is destroyed. To mitigate this extend the above mechanism to assert the output for two cycles at minimum.This does not add any protection in the other direction e.g. an SEU causing an abort when the accelerator is in fact doing fine.