- Micro:bits can be used with either Scratch or MakeCode
- MakeCode tends to be easier to get up and running, since it will use WebUSB and works across Windows, Macs and Chromebooks equally
- Micro:bits on Scratch requires Scratch Link to run in the background, to pair Scratch with the Micro:bit over Bluetooth.
- Scratch Link tends to be temperamental on Macs and does not exist for Chromebooks at all
- CoderDojo/Code Club's documented projects live at https://projects.raspberrypi.org/en/pathways/microbit-intro
- Additional retro arcade games can be found at https://arcade.makecode.com
Tip
When updating multiple microbits (either firmware or Scratch) @conallob would save time by:
- Downloading the relevant hex files and be ready to go
- Use the same CLI copy command to copy the hex file over
- Attach a micro:bit
- Copy the hex file over
- Disconnect micro:bit and attach the next micro:bit.
- Download firmware,
being careful to get firmware for the correct board version. (Firmware to Board mismatches
will result in the
529Boot Error) - Boot into Micro:bit bootloader, by holding down reset button (non LED grid side) before plugging in USB cable
- Copy the
.hexfile onto theMAINTAINENCEdrive - Wait for the yellow LED beside the reset button to stay solid
- Disconnect and reconnect USB cable
- Download Scratch Micro:bit
.hexfrom https://scratch.mit.edu/microbit & unzip - Boot the Micro:bit into Normal mode (appears as
NO NAMEdevice) - Copy
.hexfile into Micro:bit toNO NAMEdrive (NB: Make sure you are not in bootloader, you will confuse yourself) - Wait for the yellow LED beside the reset button to stay solid
- Reboot Micro:bit
- Confirm 5 letters are scrolling across the LED grid. This means it is ready to pair in Scratch
- Pair with Scratch