Carlos Pereira Atencio

Hi @gerargz, > In v0252, there is an issue where the applications don't start after flashing (power cycle is needed) but no error is reported. How did you trace this?...

Just tried this in a brand new Windows VM and it did show the micro:bit name directly on first connect:  So you are onto something there.

Okay, so even more weirdly, right after my previous message I closed Chrome and reopen it, and the second time it showed me the LPC1768 name:  Oddly, this is...

Could not replicate anymore in a new Windows VM. To be fair, even if it was still a problem, I'm not sure DAPLink could do much about it if it's...

Link to the hex file: https://www.segger.com/downloads/jlink#BBC_microbit The j-link hex file does work with DAPLink 0234 bootloader, but not with the newer 0243. One simple difference in this hex file is...

The bin file worked, but I tried this a while ago and I don't remember which tool or flags I used. It's quite possible I used the hex2bin tool from...

I haven't tested it with the latest DAPLink bootloader, but as far as I am aware the problem hasn't been solved, just a workaround found (to convert the original J-Link...

With 0241 the serial driver gets automatically installed in Windows 8/10, so there is no need to use the .exe installer. It's possible older versions of Windows (like Win7) still...

We have this micro:bit support article with instructions on how to uninstall it: https://support.microbit.org/en/support/solutions/articles/19000089574-beta-testing-mbed-driver-doesn-t-work-with-windows

The access denied error is often caused by having another MakeCode or Python editor window or tab in the background that is already WebUSB connected (MakeCode can connect automatically, so...