If you're micro:bit appears to have developed a fault, this article works through some potential problems and the steps to try to bring the device back to life.
Test on USB
Plug the micro:bit into your computer with a USB lead capable of transferring power and data* - it should appear as a MICROBIT drive and the yellow system LED on the back should light up.
On computers running Windows, MICROBIT appears as a drive under Devices and drives.
On a Mac it appears as a new drive under Devices.
If the yellow LED does not light up, it is likely that either your USB lead has developed a fault, or even your computer might have powered down the USB port (this can happen if you short-out your micro:bit when running from USB and plugging in electronic components). Some Mac's when they power down their USB port require a restart for the USB port to recover. In this case:
|Try another Lead*||Try another USB port on your computer||Try restarting your computer|
* Some USB leads are 'power only' leads (especially some really cheap leads, and some designed to charge mobile phones). Try to find a known working USB lead that has been used to transfer data - such as a lead for a smartphone or a digital camera, and try again. Also, try your micro:bit in a different computer, just in case your computer has powered down its USB ports for some reason.
Some older computers can take a few seconds for the MICROBIT drive to register when you first plug the micro:bit into a new USB port, so wait for about 20 seconds to see if it appears in your file manager. If it does not appear, then press the reset button on the back briefly, and wait another 20 seconds.
MBED Driver (Windows)
If you have upgraded from a previous version of windows to WIndows 10 or already have the MBED driver installed, Windows may not detect the micro:bit. In this case, you will need to remove the old driver to allow Windows to automatically install it.
If you see the yellow system LED lit but no MICROBIT drive after the tests above, it is possible your micro:bit has developed a fault. You should contact the supplier that you purchased your micro:bit from and ask them about their returns process.
However, if you now get a MICROBIT drive on your computer, test it with our little smiley test program by flashing the .hex file to your MICROBIT drive. Wait for the yellow LED on the back to stop flashing, and then you should get a smiley face on your micro:bit.
If you find your compass or accelerometer isn’t working in the way you expect it to, it may be a result of recent software updated to support the micro:bit motion sensor revision. Modifications have been made to the underlying software that supports the compass and accelerometer, so you may need to update your hex file.
If you're still having compass troubles, check out our tips for calibration.
If you have been using your micro:bit with Bluetooth and flashing programs over the Bluetooth from your phone or tablet, there is a small chance that you might have interrupted the code transfer process while this was happening. Follow the steps above then try the Bluetooth pairing process again (note that re-flashing a micro:bit over USB will make it forget it's Bluetooth pairing).
Bluetooth pairing mode will not work if the micro:bit has previously been flashed with a MicroPython hex file. In this case, reinstate Bluetooth by flashing a MakeCode program
If you were accidentally holding the reset button at the back at the time you copied the program onto the micro:bit this would have put the micro:bit into maintenance mode (a new MAINTENANCE drive would appear in your file manager). Also if you had pressed this button while powering it up (even after you loaded the .hex file), the micro:bit would go into this special maintenance mode and would not accept user code.
If this is the case, power down the micro:bit and reconnect the power, being sure not to press the reset button at the back as you are doing this, and the MICROBIT drive should re-appear.
If you are still experiencing issues, please try upgrading the firmware