Changes for open source / custom firmware #217
Merged
Conversation
This file contains hidden or 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
Avoids error that occurs when handling large amount of sensor data. In future, might be interesting to see if we can support faster UART baud rate.
This is so that we can handle multiple line if statements.
If user creates directory called 'data/' where they run their Python script from and places following files in: * firmware.bin * signature.bin * version This custom firmware will then be used instead of bundled firmware.
Bump timer from 8s to 11s, to wait after receiving "Done initialising ports", to avoid geting disconnected message, even though sensor connected to port.
Add information on how to make use of custom firmware.
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.
Based on recent changes to https://github.com/raspberrypi/buildhat in order to allow for anyone to build and sign firmware.
Not sure why linter errors have kicked in here and not on
main/ in previous PRs (since the linter is complaining about issues already present inmain). Will fix in a future PR...