The orange LED doesn’t turn completely off, as in a blink sketch. It brightens and darkens but it’s not as slow as when entering bootloader mode with the other XIAO I have. Actually it’s much quicker (maybe OSC malfunction?).
When you flash the bootloader with ST-LINK, do you get the following message?
** Programming Started **
** Programming Finished **
** Verify Started **
** Verified OK **
EDIT (since max replies reached):
I tried to “unbrick” the XIAO because none of my machines would recognize it anymore (as in not seen by Device Manager or lsusb).
It’s hard to say what sketch was uploaded before because I’ve been trying to unbrick it for a while now. But I believe that sketch shouldn’t be there anymore since I used command “at91samd chip-erase” a couple of times before (after that the orange LED is off).
Worked like charm!!!
Thank you so much. I recovered a Xiao (stoped working after a few days transmitting LoRaWan to ThethingsNetwork on battery- brown out??). But most of all it was pure joy when I saw the Xiao port again.
I can’t say for sure because our PC environment are different, but it sounds like there is a problem with the USB driver.
I suggest you look into the USB driver “Zadig”.
Hi PANOK,
I think the situation is exactly the same as post #32. It sounds like there is a problem with the USB driver. I suggest you look into the USB driver “Zadig”.
I ended up soldering the cables directly to the pads and using a multimeter I ensured there is connection between the ST-link V2 and the microcontroller. I also swapped SWDIO with SWCLK just in case I got it wrong the first time around but still no luck.
I’m 100% sure the wiring is correct, I checked it a bunch of times and also rewired it from scratch a few times.
I was looking around and found this article (Programming RP2040 with ST-LINK - Electrical Engineering Stack Exchange) that explains how the ST-LINK V2 can’t connect to the Seeed XIAO RP2040. Someone said to do the update however I have no idea what that guide is talking about. I updated it to the latest version (V2.J37.S7) using the “STM32 ST-link” software.
Did you have to do some weird update or did it just work?
Am I missing something?
Any Idea on how I can fix it?
Hi Andrea_Nizzola,
I have made a RescueTool for ST-Link.
Unzip the file to a suitabule location and rewrite xxxxxxxx to yours in two places in “flash.bat”.
Double-click “flash.bat” to write the bootloader. XIAO_BootloaderRescueTool_STLink.zip (10.5 KB)
Greetings, if you are still monitoring this feed, would you be so kind as to explain the following? You write
Download the bootloader file bootloader-XIAO_m0-v3.7.0-33-g90ff611-dirty.bin to C:/XIAO_bootloader.
But where do I find the file I am to download? You told me where to place it but I cannot find it. Would you please tell me what the source is? I am certain the information is in your article but it is rather lengthy and I am somewhat dyslexic.
I’ve used this guide a couple of times, and provided that the MCU isn’t damaged, it works just the way you’d expect. (Sometimes it takes more than one try.)
Here’s a small improvement. At least in current versions of OpenOCD, the at91samdXX.cfg file allows you to override CPUTAPID directly from your config file. So, instead of modifying the at91samdXX.cfg file and changing XIAO_openocd.cfg to load the modified file, you can insert a line just before, like so:
...
set CPUTAPID 0x0bc11477
source [find target/at91samdXX.cfg]
...
This change allows you to use a stock OpenOCD package, regardless of how you’ve installed it.
