The BBC micro:bit is a pocket-sized computer that introduces you to how software and hardware work together. Code.org's Creating Apps for Devices (micro:bit) curriculum is compatible with the micro:bit, but requires specific Firmata firmware to install onto the micro:bit.
Table of Contents
- Recommended Installation
- Alternative Installation
- Starting a Project with micro:bit
- Troubleshooting / FAQ
Recommended Installation via the Maker Setup page
These steps are designed for Google Chrome and Microsoft Edge web browsers released in March 2021 or later (version 90 or higher). If you are using a Chromebook, you will need to be on V90 or above.
- Plug in your micro:bit device.
- Visit https://studio.code.org/maker/setup.
- Click the Connect to Board button.
A window will pop up - something similar to a micro:bit device will appear in this window such as ‘BBC micro:bit CMSIS-DAP’ or ‘mbed Serial Port’. Select it, then press the Connect button
If this window doesn't pop up or if the screen is blank: See our Connecting the Circuit Playground or micro:bit to Your Browser: A Step-by-Step Guide. - This process will fail on the Board Connectable step if the device does not have the required Firmata firmware installed (this is expected!) - press the Update micro:bit button.
If you continue to see a red X after pressing this button: Skip to the alternative installation method in this support article - A second window will pop-up, listing a micro:bit device (the name may be different from the first window. Select the micro:bit device, then click Connect
If this window doesn't pop up or is blank: Skip to the Alternative Installation method in this support article - The step will update to show it is installing the micro:bit Firmata firmware. You will see the progress update automatically.
When it's finished, press the re-detect button at the top of the steps
When the page reloads, click "Connect to Board" again, and re-select the micro:bit device from the pop-up window
The board should connect. You can tell because the website will update, and the micro:bit itself will show a checkmark animation before disappearing.
Alternative Installation via Drag-and-Drop
This option is for computers that cannot complete the method described above, including devices with WebSerial or WebUSB disabled and browsers other than Google Chrome or Microsoft Edge. This method involves downloading the micro:bit Firmata firmware, then dragging and dropping the .hex file into the micro:bit virtual USB drive. This process is similar to the one used by Microsoft Makecode.
- Download this file onto a computer: https://downloads.code.org/maker/microbit-firmata-universal-ver1.2.hex.
- Plug in your micro:bit.
- Open both your downloads folder and the micro:bit drive, then drag-and-drop the .hex file from your computer to the micro:bit.
- The micro:bit window on your computer will close and the micro:bit device will restart.
- Visit https://studio.code.org/maker/setup and press the "Connect To Board" button
- A window will pop up - something similar to a micro:bit device will appear in this window. Select it, then press the Connect button
If this window doesn't pop up or if the screen is blank: See our Connecting the Circuit Playground or micro:bit to Your Browser: A Step-by-Step Guide. - The board should connect. You can tell because the website will update, and the micro:bit itself will show a checkmark animation before disappearing.
Still Having Trouble? Email support@code.org so we can help troubleshoot!
Starting a Project with micro:bit
Micro:bit works with our Creating Apps with Devices unit, as well as within standalone App Lab projects. Here's how to create a project in App Lab that uses the micro:bit
- In the header across the top of the screen, on the right side, click the Create --> App Lab button
- In the toolbox, click the gear icon to the right of the text "Toolbox". In the menu that appears, select "Enable Maker Toolkit"
- In the window that appears, select "Use micro:bit" from the button on the bottom
- The page will reload. When it does, you will see the micro:bit option in the toolbox
Troubleshooting / FAQ
1. What if I accidentally disconnect my micro:bit during the installation process?
Reconnect your micro:bit, then restart the steps from the beginning - your device should be able to reconnect.
2. What if no window appears asking for my micro:bit?
You may need to enable WebSerial and WebUSB.
To enable WebSerial: Follow the troubleshooting steps in our support article.
To enable WebUSB:
- Go into your browser settings
- Click "Privacy and Security"
- Click "Site Settings"
- Click "Additional Permissions"
- Click "Usb Devices"
- Make sure "Sites can ask to connect to USB devices" is selected
3. Does the micro:bit have to stay tethered to the computer?
Yes - unlike Microsoft MakeCode, the micro:bit needs to stay tethered to the computer the whole time. This is what allows it to engage with the App Lab coding environment and have it interact with apps.
4. Does the JavaScript code get transferred and execute on the micro:bit?
No - the javascript code stays on the computer. Only the initial setup code from code.org/maker/setup is installed on the microbit, which interprets the javascript from App Lab.
5. Can the App Lab interface be sent to my phone and then used with a micro:bit a few feet away via the radio feature?
Unfortunately this functionality doesn't exist in our platform at this time.
6. Do you have examples of projects that students can make with the micro:bit for the final project?
Not yet - currently all of our example projects are with the Circuit Playground, which are still a good model since the type of projects are the same.
7. A list of potential supplies to consider? Servo motors?
The supplies are the same as the existing Creating Apps with Devices course: LEDs and alligator clips. These would need to be purchased separately from the micro:bit device.
Run into a problem not covered here? Email support@code.org!