This Knowledge Base article is specifically for people who write content for the micro:bit. Please also see our general user information about the micro:bit motion sensor change.
We’d like to start by saying thanks for your support of the micro:bit - without people writing amazing resources and showing the world creative ways to use technology, micro:bit wouldn’t be nearly as exciting for people all around the world to use.
It’s important that we have an easy way to update you about any future hardware or important software revisions, so please sign up to our Device and DAL mailing list. This list will be used to give notifications about hardware revisions, or key software changes as early as possible: though we don’t anticipate anything soon, it is clear from this revision that such a list is useful.
As described on the main knowledge base article about the micro:bit motion sensor revision, your existing hex files will need to be updated before they work on the revised micro:bit. After they have been updated they will work on all versions of the device.
Hex files can be updated by loading them (for example, using drag and drop) in an editor and then downloading a new .hex. We will publish further advice about the editor changes once they are complete.
Both the MakeCode editor at makecode.microbit.org and MicroPython editor at python.microbit.org will be updated before the release of the device. We are also working with Nicholas Tollervey and the Mu Developers to ensure that the v1.0 of the Mu editor will also contain support for the revised micro:bit. For other editors, please contact the editor authors to enquire about their timeline for support of the revised micro:bit.