micro:bit FW update sequence (Browser Version)
Issue #146
resolved
This might not be an issue, but since I never encountered it, I am documenting it:
- Plugged in a micro:bit with old FW.
-
Selected USB port and got the FW mismatch message:
-
Selecting YES brings up:
-
Clicking OK brings up CHROME application window in Win Explorer !!! And there is no MICROBIT there.
Not only that, the explorer window is a FILE SAVE dialog ! - One is at a dead-end at this point.
Comments (2)
-
repo owner
-
repo owner
- changed status to resolved
Hopefully the new wording will make things clear.
- Log in to comment
Sorry that the wording is confusing. We’ve tweaked the wording in 0.6.9 to try to make it more clear.
Although surprising, this sequence is correct. MicroBlocks needs to write the firmware .hex file onto the MICROBIT virtual USB drive. However, the only way to save a file from the browser version of MicroBlocks is through the Chrome file save dialog. That’s a browser security feature, to make sure the user agrees to save the file.
Assuming that your micro:bit appears as a virtual disk drive, you should select that drive as the destination, then click the “save” button in the Chrome file dialog. However, it sometimes takes some time for the virtual MICROBIT drive when plugging in the micro:bit. If you don’t see that drive, you can close the file dialog, wait for Windows to find the drive, then try again using the “update firmware” menu command.