Makecode website "Download" fails

micro:bit
1

Just got a new micro:bit – first time user.

# DAPLink Firmware - see https://daplink.io
Build ID: v0257-gc782a5ba (gcc)
Unique ID: 990636020005282060de3498268d7eba000000006e052820
HIC ID: 6e052820
Auto Reset: 1
Automation allowed: 0
Overflow detection: 0
Incompatible image detection: 1
Page erasing: 0
Daplink Mode: Interface
Interface Version: 0257
Bootloader Version: 0257
Git SHA: c782a5ba907377658bc28aa8d132a0fa44543687
Local Mods: 0
USB Interfaces: MSD, CDC, HID, WebUSB
Bootloader CRC: 0x725bea7d
Interface CRC: 0xe561f1de
Remount count: 0
URL: https://microbit.org/device/?id=9906&v=0257

Google Chrome 145.0.7632.159 (Official Build) (64-bit) – this seems way higher than the v61+ cited in the troubleshooting page.

“Pair” – the popup window shows the device. But “connect” says “failed to connect.”

I also tried unmounting MICROBIT from the file browser and repeating the steps. Same behavior.

Copying a .hex file to the MICROBIT folder seems to work, though it failed a few times for reasons I couldn’t figure out. Perhaps that’ll be OK, but I’m curious why the advertised method didn’t work at all.

hjh

1 Like
2

honestly that “failed to connect” error is just Chrome being annoying.

the main problem is probably your firmware—0257 is super old. if you update that, the pairing usually stops tripping out. also, make sure you don’t have the microbit folder open in your files while you try to connect, because that can block the browser from grabbing it.

the .hex drag-and-drop is a decent backup, but it’s a hassle compared to the direct connect.

if that doesn’t work then just ask @richard he could probably help

1 Like
3

Thanks, good tip.

I go to https://microbit.org/get-started/user-guide/firmware/ and find https://tech.microbit.org/docs/software/assets/DAPLink-factory-release/0257_nrf52820_microbit_if_crc_c782a5ba90_gcc.hex – which looks like 257 is the latest official firmware for a micro:bit v2.21?

I tried again in the browser, this time making sure that no OS file browsers were open – still got the same “failed to connect” error.

hjh