Because I was happy with Seeed’s products in the past I recently bought a Seeed XIAO RP2350 and a Seeed Expansion Board Base.
In the “Getting Started with Seeed Studio XIAO RP2350” there is this text of October 2024:
MicroPython Firmware Issue
As of November 10, 2024, the stable MicroPython firmware version 1.24.0 available for download at MicroPython.org for RPI_PICO2 is currently incompatible with certain devices due to variations in the flash chip.
The Seeed Team is actively working to resolve this issue in collaboration with the official MicroPython maintainers. In the meantime, you can use a preview version of the MicroPython firmware as a temporary solution: RP2350 MicroPython Firmware Preview
Now we are at the end of the first week of May and nothing has changed regarding the message of November 10, 2024!
I have the feeling that Seeed product XIAO RP2350 is treated like an orphant.
Something you left forgotten in a corner, so to speak.
The past years I bought and experimented a lot of different microcontrollers (see my Github repos).
With this XiAO RP2350 I encounter a lot of problems.
To start with and referencing Seeed’s message of November 10, 2024, above,
until now nothing has been published that the problems mentioned were handled.
So, I am still stuck with this old version of Micropython 1.24.0 that lacks various modules, like sdcard. There is also the problem of main.py not starting automatically at power-on or reset.
Question: what are Seeed’s intentions to get this product working?
Hi there,
So I see this assertion and LOL, the MCU is only matured since release, OCT 24’ so along with Seeed several vendors noted issue’s and have varying levels of support. It’s in the Wiki even , So maybe go read up a TAD and you can read between the lines, ALL other vendors HAVE reported issues, just so happens the FLASH issue hampers the implementation of the MicroPython. It’s a RPI problem not Seeed’s if you have experimented then you will see that.
" Luke Wren, one of the engineers working on RP2350 has stated that the supplier responsible for the pad circuitry has provided a faulty design. “We didn’t modify the pad, we asked the vendor to modify their own pad. There was one particular structure on the RP2040 FT pad that limited its tolerance, but on inspection the modified layout we got back was a completely different circuit.” [8] "
Give it time and they WILL figure it out, with so many New Products, all the AI and IOT. We are lucky they even include that boat anchor of a chip (imo) in the Xiao Line up. 
Patients 
, if they say they will… then it will be
HTH
GL 
PJ 
AFAIK, there is a LOT that go’s on behind the scenes, even ADAfruit and DF robo are dealing with the same issue’s with there offerings 
@PJ_Glasso Thank you for your rapid and very informational reply. I wish all enigineers working on it good luck with mastering the problems together with the supplier(s)! In the mean time I’ll read again the Wiki. I wish you a nice weekend!
Afterburner:
What I didn’t write in my initial text, however this fact is - I guess - known with Seeed’s engineers.
Many times when, from within Thonny, I saved the file main.py or another file to the XIAO RP2350, the transfer broke off. After a next reboot the XIAO RP2350 appeared to do nothing, did not have a COM port or came up in DFU/Download mode. My solution was then: in the first place try to flash the same micropython .uf2 (v1.24.0-preview.201 for the RPI_PICO2) that worked or first flash the flash_nuke.uf2 followed by micropython and then download my files into the XIAO RP2350.
1 Like