A “.hex” file is the only file type that a micro:bit will read. Whether you are downloading your .hex file directly from an online language like MakeCode, or you are downloading a custom .hex file (like the BitFirmware.hex required for bluetooth connection) from our website, confirming that the .hex file is correctly downloading onto your micro:bit is important.
Note: While micro:bit may appear in your File Explorer (Windows/Chromebooks) or on your Desktop (Mac) as a drive, micro:bits do not behave like drives. When a .hex file is “copied” onto the micro:bit, that file will begin to automatically run as a program. The .hex file will not show up in the micro:bit as it would in a drive.
- Does your micro:bit show up as a drive in your file explorer (Windows/Chromebook) or on your desktop (Mac)? If not, then you will want to see our article titled, “Why is my micro:bit not showing up on my computer?”
- Do you know where your BitFirmware.hex file is being downloaded to? It is possible that the .hex file is downloading, but it is not going somewhere other than the micro:bit. See the video below for more information.
- When you copy or download the BitFimware.hex file onto the micro:bit, is the yellow light on the back of the micro:bit flashing? If not, your micro:bit firmware may need to be updated. Check out our article titled, “How do I update my micro:bit firmware?”