Steven Bos

For those interested and mentioned in #1212, another non-command line workaround is to drag-and-drop the user.hex or user.bin onto the microbit drive, which will also remove the SD. > >...

Command line workaround (needed only once): 1) pyocd erase --mass --t nrf52833 2) flash like normal, eg. pyocd flash Any idea why a mass erase is needed and a chip...

It look like new MicrobitV2's are programmed with APPROTECTSTATUS register enabled, meaning that an ERASEALL command is needed to overwrite this protection according to https://infocenter.nordicsemi.com/pdf/nwp_027.pdf. This is different from new...

See OP, if I drag and drop my .bin file to the MSD of a new micro:bit V2 the flash is programmed and pyocd flash command line then works with...

Thanks for the quick response. And spot on. When I upload the Out of Box hex, the issue returns and I cannot flash it without doing pyocd erase --mass first

Interesting, it fails to flash my .bin after I flashed it with a hex from the online editor as well.

Yes, I can flash different bin files with PyOCD consecutively, but only after it is unlocked with a pyocd erase --mass when it was programmed with a hex before

I don't know if this is relevant, but I cannot "pyocd flash microbit_program.hex" resulting in this error:  With the first five lines of the hex (downloaded from https://python.microbit.org and...

Ah ok, so unrelated to this issue.

Inspired by Issue #1215 , I am starting to doubt if APPROTECTSTATUS register is enabled. If I try  I get the same result with both the .hex and my...