OK, I understand this might be a stretch! I have a RP2350B computer which was working perfectly, but has suddenly stopped! I built it from a Silicon Chip kit, and it hasn't ever missed a beat - until yesterday. I've been using Tera term and a USB cable to power it, and transfer information. Yesterday, when I plugged it in, and chose the USB serial option, it would not show the >. Ive tried following the information in the original Silicon Chip article - setting the the DVDD pot to 6K; setting switches to 'disable'; pressing the boot switch and uploading the 'çlear flash' UF2 file. Then Ive reset the DVDD pot to 18K etc. But all to no avail. However, if I press the 'reset' button on the rear, I do get some strange  'hieroglyphics' appear on the screen. On close inspection, I can't see any 'mechanical' issues - solder pads etc, and both red and green LEDs are on. If anyone has any suggestions on what to try or where to monitor - anything, really, Id be very grateful! As I said, it was working *exactly* as anticipated before plugging it in yesterday..... Suggestions? Many thanks to everyone!

I think a few of us have experienced something similar in the past. Mine wouldn't work in any USB port. I fiddled with deleting the USB ports and letting them re-establish themselves. Don't remember if that was the actual cure because I did lots of things but it eventually started working.

G'day Mikeinnc,
The mention of hieroglyphics makes me wonder if the baud rate in Tera-Term has become incorrectly set. I would check this first.

Setup -> Serial Port -> 115200 8 n 1

What version of Windows are you running, has it done an update.

So can you confirm:
The RP2350 does show up as a drive and you can download the clear flash uf2
The drive reappears and you can download the PicoMiteHDMIUSB firmware
is the heartbeat LED flashing?
You can connect to the PicoMite in Tera-Term but not communicate.

Regards, Lyle.
Edited 2026-10-28 19:26 by mozzie

On my (WeAct) RP2350B-Boards the "clear flash uf2" never worked, but the "Pico Universal Flash Nuke" always did.

https://github.com/Gadgetoid/pico-universal-flash-nuke

Latest Release:
https://github.com/Gadgetoid/pico-universal-flash-nuke/releases/tag/v1.1.0

  mozzie said  

G'day Mikeinnc,
The mention of hieroglyphics makes me wonder if the baud rate in Tera-Term has become incorrectly set. I would check this first.

Setup -> Serial Port -> 115200 8 n 1

What version of Windows are you running, has it done an update.

So can you confirm:
The RP2350 does show up as a drive and you can download the clear flash uf2
The drive reappears and you can download the PicoMiteHDMIUSB firmware
is the heartbeat LED flashing?
You can connect to the PicoMite in Tera-Term but not communicate.

Regards, Lyle.

Lyle, you are a champion! I'm using WIN11 and setting up the TeraTerm port did the trick! Certainly, the other issues you mentioned all appeared to be OK - except I don't appear to see a flashing LED? There is a green and a red one- they are both on. I must admit I did wonder if it was a speed issue, but the documentation says that anything other than 1200 b/s works. It clearly doesn't! But, yes - all is good now. Thank you again!

And I must say a big thank you to all of the other very helpful replies. Its so good to know that I'm not alone out there!

Mike

G'day Mike,
First of all, welcome to the forum. I hope you'll find (as I have) the breadth of knowledge here and willingness to help is second to none.

Been tripped up by this numerous times in the past. It should be printed in big bold type in the article somewhere and also above my monitor  

For future reference:
If using a NON-USB firmware variant (IE: plugging direct into the Micro-USB on the PICO / board) the baud rate is ignored except for possibly 1200bps
If using a USB firmware variant then the console is via a serial link (CH340 etc) and the baud rate needs to be set, normally 115200

This has also been slightly confused now we have the HDMIBTH variant that is USB but not named as such.

Also if you plug the Pico in to a different USB port it can be assigned a new COM port with the wrong settings.

Regards, Lyle.