Xiao not programming

Products & Technology XIAO
#15

Hi Baozhu

Thanks for the response.

I tried on my laptop and it uploaded first time. I know the Seeeduino used a USB-C connector but is USB 3 only? The failing machine has USB 2 only so this could be a reason.

Having said that, the device is visible on USB 2, configured as a serial device, is visible to the Windows eg COM5, and the Arduino IDE - Board Info reports back correctly (see below) - using the same MS driver on an Intel (Gigabyte) motherboard exactly as per the laptop yet it can’t upload.

BN: Seeeduino XIAO
VID: 2886
PID: 802F
SN: 9511AD735053574C342E3120FF042711

I can get around this by uploading from the laptop but I’m still curious to understand what the incompatibility is.

Also, the original machine (which is an Intel i7) takes ages and appears to do a significant amount more work to compile than the laptop which is just an i3 and compiles in seconds. The debug logs show the extra work clearly - .txt file of the successful log is 20k vs 193k for the failing machine? I will try re-installing the IDE to clean it up and see if that helps.

Thanks

#16

Hey there Whatnot. I had problems myself and there is something that happens when Arduino tries to flash that can make the flash fail. One thing that helped me was removing “ghost” com ports and devices. If you go into device manager in windows and select view and tick hidden devices and go through the list and right click the grey devices and remove, it may help.

#17

I am facing the same problem. XIAO is truly a groundbreaking products given its size vs cost. However, the bootloader issues are making me doubt its reliability in the field. For me as well, the programming is a 50-50 chance thing. Sometimes it works, sometimes it doesnt !

Do you know if its possible to replace the current bootloader with a more stable one? Like the one used in Arduino (optiboot) or something?

#18

Hi sghice,
Yep, I tried that but it has no effect. When the IDE gets to upload it shows the following:

Sketch uses 40644 bytes (15%) of program storage space. Maximum is 262144 bytes.
    Forcing reset using 1200bps open/close on port COM3
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    PORTS {COM3, } / {COM3, } => {}
    Uploading using selected port: COM3
    C:\Users\...\AppData\Local\Arduino15\packages\Seeeduino\tools\bossac\1.7.0-arduino3/bossac.exe -i -d --port=COM3 -U true -i -e -w -v C:\Users\...\AppData\Local\Temp\arduino_build_443199/DFPlayer_Test.ino.bin -R

Followed by a long delay and then it fails. I can upload the same code with the same versions of the IDE and libraries on the same version of Windows 10 on my laptop. It uses the same version/date MS driver and works reliably. So the only difference left is that the USB port different hardware. Whether that’s a V2 vs V3 difference or just that Intel ICH10 USB hardware on my desktop is too old I don’t know. Once the code is uploaded, I can re-attach the XIAO to the desktop and the Serial Monitor works perfectly so the Serial via USB is working.
It appears, on my laptop, to mount the XIAO as a USB drive and copy the code that way so it must be a peculiarity of that approach. All the real USB drives I have work fine on both machines.

#19

i face the same problem. It works on my laptop but not on my desktop. It gets stuck in the exact same point as yours. I tried to tinker around it and now my XIAO is bricked :frowning: . its no longer detected by any computer., it doesnt goto bootloader mode, it doesnt reset with the jumper method, only a green led glows… nothing else happens…its bricked :frowning:

Anyone has any experience reviving a dead xiao?

#20

i was able to unbrick mine…using raspberry pi

#21

I ran in to the same problem, and to me it appears to be baud rate related. I can program at 9600 baud over and over again, but the symptom occurs repeatedly when I try to program the XIAO at a higher baud rate. This occurred on 2 different modules. Now I will try increasing speed slowly instead of jumping immediately to 115200 baud and see how fast I can reliably program the XIAO with my setup.

#22

I ran in to the same problem
-baud rate is 9600
-default drivers from Microsoft in Windows10
-uninstalled all ghost COM ports
-USB Intel ICH9
-Arduino: 1.8.13 (Windows Store 1.8.42.0) (Windows 10), Board: “Seeeduino XIAO, Arduino, Off”
BN: Seeeduino XIAO VID: 2886 PID: 802F SN: 461E97315053574C342E3120FF0C021B

image
image872×1196 58.4 KB

:confused:

#23

I see a lot of similar serial ports on your computer that might interfere with downloading. @MichaelZP

#24

on another computer this Seeeduino XIAO is programmable :confused:

#25

I have two Raspberrypi’s that are 3B and tried this from this page: How to unbrick a dead xiao using raspberry pi [ GUIDE ][openocd]
and it didn’t work. When the first one didn’t work, thought it might be dead, so I tried it with a known good one…now I have two bricks. Wondering it the openocd software changed from when did it and broke it?

#26

Hi @tannenba

Please try the above method as mentioned in a previous post

#27

I actually did and was able to bring one of them back. I still have a dead one. I think it is really dead.

#28

@tannenba Oh. Maybe you could try one last method for the dead XIAO you have, which is to enter the bootloader mode or to reset it.

Best Regards,
Lakshantha

#29

Tried that, no go it’s dead. Thanks for the suggestion.

1 Like
#30

Just got one of the Seeeduino developemnet boards and it has pogo connectors for the 4 pins on the bottom. Works great with the ST-Link.

2 Likes
#31

Got the same problem, after few days flashing without bigger problems, now is freezed,
Blue and greeb led constant on, amber quick flash 3 times, try to reset it or reloaded number of times.
Still unable to upload any sketch even empty. there is comunication with it, you can check board info, serial etc. but no chance to upload any data.

#32

After numbers of try got it working, with double tap reset, then change com port in arduino and reload sketch

1 Like
#33

You are likely using Windows

If you are having any of these issues

**Uploads forever then fails *
**Upload bar disappears **
*Won’t compile even though there are no errors
*XIAO does not receive reset signal

*If you have a program that has ran in the past but when you try to upload it now your Seeeduino acts like it dont want to accept that shit and the ide shoots out a weird ass compiling/upload message that you cant understand

*other COM issues

PLEASE TRY THIS PROCEDURE

1. Go to Arduino IDE app settings and this can be done by right clicking the arduino app in start menu or whatever directory it is located on your computer.

2.There will be 3 options, you will use all of them.1 Terminate, 2 Repair, then 3 Reset; none of these will delete your precious data .

3. Restart your computer and then bring the Arduino IDE up if you don’t get the common message that your libraries have been updated select manage libraries through the tools tab (this will update your list of libraries automatically) don’t expect it to pop up right away, just be patient (you don’t really have to do much after this) soon you will see a sluggish loading bar at the bottom of you library manager that will fill to 100%. After that process is finished, you should restart the IDE and try to compile and upload your program assuming you are on the correct COM and you have already did the prerequisites for Seeeduino XIAO setup.

Your program should upload successfully, you are welcome !

#34

I am having more or less the same problem @Seeed. May be a fix of the firmware or so is in order… They brick very easy now…