i love the clip! … extra words to trick the man… bla bla… what da?
Hi there,
So , And for those JLink Jockey’s out there. Just connect under reset at speed = 1000 or less I used at 500hz on a very stubborn one I was I2S messing with in the Round Display and did not want to halt or erase… after a low speed strafing run it cracked it open like an egg. Able erase , write(loadfile) AOK. (keep the leads REAL short)
connect
device type
SWD
Speed- 1000k (defualts to 4000k) if it works but won’t verify, drop it to 500K and " Roberto’ is your Uncle"
Halt
Erase
Loadfile c:\Your\good\stuff.hex
(optional)…
Regs (cpu registers print out)
Go (after a halt, sanity check it’s alive and working)
EXIT … Your work is done here, Enjoy the Restored Xiao 
HTH
GL 
PJ 
Looks like this,
Hi! Thanks for posting this solution.
I had a custom board with built-in cmsis debugger and it turns out that, every chip out of the factory is enabled with access port protection and requires j-link to flash. I was able to erase the chip and flash it with the cmsis.
I was very close to buying the J-link / DK 
2 Likes
Mass erase support in OpenOCD has already been added in the latest SDK. It now checks the lock status and automatically unlocks the device before flashing.
4 Likes
Would you mind linking the source repo, instructions, and version number that was updated? Just want to make sure as of 2/2026 I don’t have to hunt down the latest between Nordic and Seeed.
I would be ever so grateful 
I somehow bricked one and I can’t even get it to show up as a usb device anymore. 
I was just messing around with making a usb gamepad over ble and it just stopped randomly after testing my controls were working. I can see the device still runs for a little bit then crashes (red led turns off)
Hello guys, I just had the same problem and searched around how to revive my bricked hardware (happened twice already today), it’s also a SeeedStudio nRF54L15. Could’t get the latest SDK working with Chocolatey and stuff… I just updated a github repo, so you can use it too, it reads out the specific hardware ID so it should just erase the whole memory and make it usable again without a lock, no guarantee for other device, worked with nrf54. Use a .venv for this operation and let me know if this helped you:
You can search the GitHub Repo, just clone into: MikeProStudio/nRF-Unlocker