XIAO looses its Ports

[msfujino]

Creator,
Your post will not appear on the pages below.
https://forum.seeedstudio.com/
However, if you use the search function to search for “xiao port”, you will find two posts.
https://forum.seeedstudio.com/search?q=xiao%20port

Did I brick my Xiao

Something very odd happened that I can’t make sense of. Existing project, a device that reports how far I walk on an outing. It is a Arduino Uno, serial GPS to Uno uart & LCD display. I’m using the Arduino IDE. The hardware is a 3" x 3" x 2" cube that I want to make smaller. End goal is running on a Seeeduino Xiao, same serial GPS & a small Oled display. I stripped out the LCD code & brought the remainder up on the Xiao watching the GPS distance data on the IDE serial monitor, all good. Next…

2 bricked XIAOs

Something very odd happened that I can’t make sense of resulting in 2 bricked XIAOs. Converting an existing project from Uno to Xiao. I modified an ESP32 IIC HelTec OLED library to properly exist with the Arduino IDE and compile for Xiao with the old project code. It compiled & uploaded OK but just after a good upload the Com port disappeared and would not return (per Win10 Device Manager & Arduino IDE). Had a spare Xiao so I connected that one & the Com port re-appeared. As a test I loaded …

Managing memory boundaries seems to be the programmer’s responsibility. The link below is an example of a sketch that will definitely make a brick.

Two "bricked" Xiaos [how to fix and how'd it happen]?

So to start I have two Xiaos that won’t go into bootloader no matter how much I try to short the pads. I know how to do it normally because I’m constantly needing to trigger the bootloader. Neither one will work even plugged into a battery pack, so it’s not just a PC thing. What do I do? How do I get them so they can work again? Also they both died after running the same sketch. I was just playing around with sounds on a piezo speaker. Can anyone spot anything in the code that would cause the…