Carlos Pereira Atencio
Carlos Pereira Atencio
I don't know sorry, maybe that is just the make program build info. Based on the output though, sounds like you are building with gcc arm v5: ``` -- Found...
This a great feature, thanks MakeCode team! I tried it today in makecode.microbit.org/beta but it shows the "Oops, gif encoder could not load. Please try again." error: 
This experiment doesn't seem to be present in the share screen in MakeCode 2022.
Doesn't look like the `--erase chip` flag is being applied, but something different is happening because in this case it takes a few more senconds to throw the error: ```...
As expected, `pyocd cmd` has the same results: ``` $ pyocd cmd --verbose 0001346:INFO:board:Target type is nrf52833 0001372:INFO:dap:DP IDR = 0x2ba01477 (v1 rev2) 0001418:INFO:ap:AHB-AP#0 IDR = 0x24770011 (AHB-AP var1 rev2)...
Okay, so i can confirm that `pyocd erase --chip` doesn't work but `pyocd erase --mass` does work 🎉 Is "chip erase" the same a sector erase, but going through all...
If the nRF52 chip erase goes via the flash algos, then it looks like it's using the same ERASEALL command as the mass erase: - Flash Algo chip erase: https://github.com/pyocd/FlashAlgo/blob/ea94915222bc0fadba9c556a424a3663d3a010fa/source/nordic/FlashPrg.c#L150...
The micro:bit V2 nRF52 flash is not locked from factory, or at least not on purpose. Would DAPLink MSD flashing work if it's locked? We had an issue with a...
> 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...