Workaround for waiting for all bootloader writes to be finished #1045
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
… before returning and resetting GAP8.
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.
This fixes the issue bitcraze/crazyflie-lib-python#330 where the library/CF would reset the GAP8 before all the bootloader writes had been handled in the GAP8 (since this is asynchronous). This was especially problematic when the last part of the binary crossed a page boundary which triggers an erase (erases takes extra time).
In this workaround we're requesting the MD5 checksum of what we've written after the last write has been sent. This is to make sure that all write packages has been processed (they are processed in order in the GAP8), when we get the result we know that the writes have taken place. But we do not care about the results of the checksum.