Update to latest release firmware (v1.1.1 and v2.1.2). #86
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.
Updates v1 to https://github.com/bbcmicrobit/micropython/releases/tag/v1.1.1 and v2 to https://github.com/microbit-foundation/micropython-microbit-v2/releases/tag/v2.1.2
I'm helping some schools in Australia that are using Mu and need the fix for lancaster-university/codal-microbit-v2#294 to make their robots work.
I'm not entirely sure I've done this correctly. I grabbed the official release binaries and then use the universal hex tool to combine them. As a trial run I did this for the versions that uFlash currently uses, but ended up with a small but unexpected diff. This is the first commit in the PR. The second commit updates to the latest versions.
I couldn't see any issues in my testing, but I'd like to understand the diff. @ntoll @carlosperate hoping you can spot what I've missed. Perhaps this is just due to a later version of the universal hex maker tool and the difference is not important? Thanks!