Can't get the code editor to connect to my Thumby

Started by Perodis, April 03, 2026, 09:02:49 PM

Previous topic - Next topic

Perodis

*
Newbie
Posts: 1
Logged
Just received my Thumby today and am trying to get the code editor connected so I can get games downloaded and it isn't connecting. On my device manager it shows as 'Unknown USB Device (Device Descriptor Request Failed)'.

The steps I've tried to fix this are the fixes in the FAQ (Reloading the firmware and installing Zadig and installing a USB Serial (CDC) driver). Neither have worked. When I did the reloading the firmware, my computer did detect it as RPI-RP2, which then I placed the firmware into the device, so it is connecting to my computer. But as soon as the firmware loaded, it went back to 'Unknown USB Device (Device Descriptor Request Failed)' in Zadig and my device manager.

I'm at a bit of a loss, so if anyone could help me, I would really appreciate it. I'm on Windows 10.

Gunnarjace20!

***
Full Member
Posts: 13
  1. Skype don’t exist
Location: Not telling
Logged
I'm sorry but windows 10 ain't supported anymore. Try seeing if you can update your PC or laptop. 💻

harrydaily

*
Newbie
Posts: 1
  1. harrydaily
Logged
The steps I've tried to fix this are the fixes in the FAQ (Reloading the firmware and installing Zadig and installing a USB Serial (CDC) driver).

fixobo

*
Newbie
Posts: 1
Logged
Quote from: Perodis on April 03, 2026, 09:02:49 PMJust received my Thumby today and am trying to get the code editor connected so I can get games downloaded and it isn't connecting. On my device manager it shows as 'Unknown USB Device (Device Descriptor Request Failed)'.

The steps I've tried to fix this are the fixes in the FAQ (Reloading the firmware and installing Zadig and installing a USB Serial (CDC) driver). Neither have worked. When I did the reloading the firmware, my computer did detect it as RPI-RP2, which then I placed the firmware into the device, so it is connecting to my computer. But as soon as the firmware loaded, it went back to 'Unknown USB Device (Device Descriptor Request Failed)' in Zadig and my device manager.

I'm at a bit of a loss, so if anyone could help me, I would really appreciate it. I'm on Windows 10.
I had a similar issue with a USB device not being recognized properly on Windows. Since the Thumby shows up as **RPI-RP2** when you enter bootloader mode, that suggests the USB connection and board are at least working at that stage.

I'd try a few basic things first:

* Use a different USB cable, making sure it's a data cable rather than charge-only.
* Try another USB port, preferably a direct port on the PC rather than a hub.
* After flashing the firmware, unplug the Thumby completely and reconnect it.
* Check Device Manager for any leftover driver entries and remove the failed device before reconnecting.
* If possible, test it on another Windows computer to determine whether it's a PC/driver issue or something with the Thumby itself.

If it consistently works only in **RPI-RP2** mode but immediately becomes an unknown USB device after the firmware boots, I'd suspect either a driver/USB enumeration issue or potentially a hardware problem. Testing with another computer would probably be the quickest way to narrow that down.

webglgames

*
Newbie
Posts: 1
  1. webglgames
Location: USA
Logged
Since the Thumby is detected correctly as RPI-RP2 in bootloader mode, the USB connection itself seems to be working at least at that stage.
I would try a different known-good data cable and another USB port first, preferably directly on the PC instead of through a hub. It may also help to remove the failed USB device entry from Device Manager, reboot, and reconnect the Thumby after flashing the firmware.
If it works in RPI-RP2 mode but immediately becomes an unknown USB device after the firmware starts, that points more toward a driver or USB enumeration issue than a completely dead device.
For a quick gaming break while troubleshooting hardware, I sometimes use BunaGames for browser games that do not require any installation.
Testing the Thumby on a second computer would probably be the fastest way to confirm whether the issue is with Windows/drivers or the device itself.

SMF spam blocked by CleanTalk