Fix unsigned fw update #11604
Merged
Fix unsigned fw update #11604
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
|
@remibettan , @SamerKhshiboun FYI |
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.
We changed the behavior and do not wait for HWM response when we don't need it (previous PR) .
Unsigned FW update process loop and send HWM byte by byte for writing the new image.
Looks like he cannot handle the write speed and the previous action bought it some time. (or it is really expecting the
getcommand)The process does not end without it..
I restored the old behavior on that case and it fixed the issue.
LibCI test? I think it's needed for regression.
Next PR.
Tracked on [LRS-745]