[Solved] Gamebuino not detected

[ziirish]

Hi,

I received my Gamebuino last week as a gift. It's a nice little piece of hardware.

Unfortunately, I could't manage to get it detected by my computer when plugging it either in Linux or in Windows.

Also, the rx/tx leds aren't lighting while connected to my computer. They are just "flashing" briefly when I plug the Gamebuino.

I tried several wires and several computers.

Here is a dmesg output in case of:

Code: Select all

Dec 14 19:19:51 cobalt kernel: [47331.403488] usb 3-4: new full-speed USB device number 3 using xhci_hcd
Dec 14 19:19:51 cobalt kernel: [47331.515671] usb 3-4: device descriptor read/64, error -71
Dec 14 19:19:51 cobalt kernel: [47331.619670] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 20.
Dec 14 19:19:51 cobalt kernel: [47331.619675] usb 3-4: hub failed to enable device, error -22
Dec 14 19:19:51 cobalt kernel: [47331.731818] usb 3-4: new full-speed USB device number 4 using xhci_hcd
Dec 14 19:19:51 cobalt kernel: [47331.844010] usb 3-4: device descriptor read/64, error -71
Dec 14 19:19:51 cobalt kernel: [47331.948042] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 21.
Dec 14 19:19:51 cobalt kernel: [47331.948047] usb 3-4: hub failed to enable device, error -22
Dec 14 19:19:51 cobalt kernel: [47332.060197] usb 3-4: new full-speed USB device number 5 using xhci_hcd
Dec 14 19:19:51 cobalt kernel: [47332.060429] usb 3-4: Device not responding to setup address.
Dec 14 19:19:52 cobalt kernel: [47332.264662] usb 3-4: Device not responding to setup address.
Dec 14 19:19:52 cobalt kernel: [47332.468640] usb 3-4: device not accepting address 5, error -71
Dec 14 19:19:52 cobalt kernel: [47332.580777] usb 3-4: new full-speed USB device number 6 using xhci_hcd
Dec 14 19:19:52 cobalt kernel: [47332.580999] usb 3-4: Device not responding to setup address.
Dec 14 19:19:52 cobalt kernel: [47332.785039] usb 3-4: Device not responding to setup address.
Dec 14 19:19:52 cobalt kernel: [47332.989198] usb 3-4: device not accepting address 6, error -71
Dec 14 19:19:52 cobalt kernel: [47332.989251] usb usb3-port4: unable to enumerate USB device
Dec 14 19:19:54 cobalt kernel: [47334.206604] usb 3-4: new full-speed USB device number 7 using xhci_hcd
Dec 14 19:19:54 cobalt kernel: [47334.318768] usb 3-4: device descriptor read/64, error -71
Dec 14 19:19:54 cobalt kernel: [47334.422829] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 24.
Dec 14 19:19:54 cobalt kernel: [47334.422835] usb 3-4: hub failed to enable device, error -22
Dec 14 19:19:54 cobalt kernel: [47334.535032] usb 3-4: new full-speed USB device number 8 using xhci_hcd
Dec 14 19:19:54 cobalt kernel: [47334.647118] usb 3-4: device descriptor read/64, error -71
Dec 14 19:19:54 cobalt kernel: [47334.751229] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 25.
Dec 14 19:19:54 cobalt kernel: [47334.751233] usb 3-4: hub failed to enable device, error -22
Dec 14 19:19:54 cobalt kernel: [47334.863347] usb 3-4: new full-speed USB device number 9 using xhci_hcd
Dec 14 19:19:54 cobalt kernel: [47334.863570] usb 3-4: Device not responding to setup address.
Dec 14 19:19:54 cobalt kernel: [47335.067744] usb 3-4: Device not responding to setup address.
Dec 14 19:19:55 cobalt kernel: [47335.271787] usb 3-4: device not accepting address 9, error -71
Dec 14 19:19:55 cobalt kernel: [47335.383929] usb 3-4: new full-speed USB device number 10 using xhci_hcd
Dec 14 19:19:55 cobalt kernel: [47335.384148] usb 3-4: Device not responding to setup address.
Dec 14 19:19:55 cobalt kernel: [47335.588403] usb 3-4: Device not responding to setup address.
Dec 14 19:19:55 cobalt kernel: [47335.792374] usb 3-4: device not accepting address 10, error -71
Dec 14 19:19:55 cobalt kernel: [47335.792441] usb usb3-port4: unable to enumerate USB device
Dec 14 19:19:56 cobalt kernel: [47337.125896] usb 3-4: new full-speed USB device number 11 using xhci_hcd
Dec 14 19:19:57 cobalt kernel: [47337.238087] usb 3-4: device descriptor read/64, error -71
Dec 14 19:19:57 cobalt kernel: [47337.342125] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 28.
Dec 14 19:19:57 cobalt kernel: [47337.342130] usb 3-4: hub failed to enable device, error -22
Dec 14 19:19:57 cobalt kernel: [47337.454285] usb 3-4: new full-speed USB device number 12 using xhci_hcd
Dec 14 19:19:57 cobalt kernel: [47337.566500] usb 3-4: device descriptor read/64, error -71
Dec 14 19:19:57 cobalt kernel: [47337.670486] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 29.
Dec 14 19:19:57 cobalt kernel: [47337.670492] usb 3-4: hub failed to enable device, error -22
Dec 14 19:19:57 cobalt kernel: [47337.782653] usb 3-4: new full-speed USB device number 13 using xhci_hcd
Dec 14 19:19:57 cobalt kernel: [47337.782882] usb 3-4: Device not responding to setup address.
Dec 14 19:19:57 cobalt kernel: [47337.987029] usb 3-4: Device not responding to setup address.
Dec 14 19:19:58 cobalt kernel: [47338.191050] usb 3-4: device not accepting address 13, error -71
Dec 14 19:19:58 cobalt kernel: [47338.303268] usb 3-4: new full-speed USB device number 14 using xhci_hcd
Dec 14 19:19:58 cobalt kernel: [47338.303488] usb 3-4: Device not responding to setup address.
Dec 14 19:19:58 cobalt kernel: [47338.507620] usb 3-4: Device not responding to setup address.
Dec 14 19:19:58 cobalt kernel: [47338.711636] usb 3-4: device not accepting address 14, error -71
Dec 14 19:19:58 cobalt kernel: [47338.711691] usb usb3-port4: unable to enumerate USB device
Dec 14 19:19:59 cobalt kernel: [47339.957094] usb 3-4: new full-speed USB device number 15 using xhci_hcd
Dec 14 19:19:59 cobalt kernel: [47340.069268] usb 3-4: device descriptor read/64, error -71
Dec 14 19:20:00 cobalt kernel: [47340.173303] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 32.
Dec 14 19:20:00 cobalt kernel: [47340.173308] usb 3-4: hub failed to enable device, error -22
Dec 14 19:20:00 cobalt kernel: [47340.285448] usb 3-4: new full-speed USB device number 16 using xhci_hcd
Dec 14 19:20:00 cobalt kernel: [47340.397584] usb 3-4: device descriptor read/64, error -71
Dec 14 19:20:00 cobalt kernel: [47340.501697] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
Dec 14 19:20:00 cobalt kernel: [47340.501701] usb 3-4: hub failed to enable device, error -22
Dec 14 19:20:00 cobalt kernel: [47340.613868] usb 3-4: new full-speed USB device number 17 using xhci_hcd
Dec 14 19:20:00 cobalt kernel: [47340.614100] usb 3-4: Device not responding to setup address.
Dec 14 19:20:00 cobalt kernel: [47340.818241] usb 3-4: Device not responding to setup address.
Dec 14 19:20:00 cobalt kernel: [47341.022250] usb 3-4: device not accepting address 17, error -71
Dec 14 19:20:00 cobalt kernel: [47341.134405] usb 3-4: new full-speed USB device number 18 using xhci_hcd
Dec 14 19:20:00 cobalt kernel: [47341.134626] usb 3-4: Device not responding to setup address.
Dec 14 19:20:01 cobalt kernel: [47341.338847] usb 3-4: Device not responding to setup address.
Dec 14 19:20:01 cobalt kernel: [47341.542868] usb 3-4: device not accepting address 18, error -71
Dec 14 19:20:01 cobalt kernel: [47341.542952] usb usb3-port4: unable to enumerate USB device
Dec 14 19:20:02 cobalt kernel: [47342.876407] usb 3-4: new full-speed USB device number 19 using xhci_hcd
Dec 14 19:20:02 cobalt kernel: [47342.988508] usb 3-4: device descriptor read/64, error -71
Dec 14 19:20:02 cobalt kernel: [47343.092630] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
Dec 14 19:20:02 cobalt kernel: [47343.092634] usb 3-4: hub failed to enable device, error -22
Dec 14 19:20:03 cobalt kernel: [47343.204733] usb 3-4: new full-speed USB device number 20 using xhci_hcd


Any hint?

Thanks

[Myndale]

Sounds like you might be a victim of FTDI-gate. To cut a long story short there was an apparent issue in manufacturing in which counterfeit USB-to-Serial chips were installed in Gamebuinos and FTDI (the company that makes the genuine chip) updated their drivers to deliberately brick all the counterfeits by setting the hardware VID to 0000. Here's the original thread that led to the discovery that Gamebuino was affected:

viewtopic.php?f=7&t=1373

Fortunately it's reversible, if you read through the thread you'll see there's an installation that allows 0000 hardware VIDs to work under Windows and another that restores the chip to its original state. Your first step should be to open the Gamebuino device in Device Manager and check the hardware settings, if the VID is 0000 then you'll know what the problem is. If not, post back here again and we'll go from there.

[ziirish]

Hi,

Thanks for the quick answer.
I'll give it a try, but on the windows box I tried, I couldn't see anything related to arduino/gamebuino in the device manager.

Also, I actually use Linux 99.999999% of the time. I personally don't have any windows system, I borrowed a colleague computer for my testings.
I didn't search deeply yet about the FTDI issue, but the "reset VDI to 0000 issue" seems to only affect windows. Do you know if there are any cases reported with Linux too?
Because I first tried my gamebuino on my Linux box and I've never been able to get it detected by the Arduino IDE.

[Myndale]

Ok, it's unlikely to be the FTDI-gate issue then. The bad driver was indeed Windows-only but it would overwrite the VID stored in the chip's EEPROM which subsequently stopped Gamebuino working in Linux as well. If you saw this problem before trying it in Windows then it's probably something else. Unfortunately I'm a Windows-only guy so I'll have to defer to one of the Linux gurus to help out here. Have you ever installed any other Arduino-type devices in Linux?

[rodot]

When you connect your Gamebuino to your computer, both RX and TX should flash twice quickly. If not, it's often a connectivity problem (bad USB cable, etc..) or a driver issue.

You told us you tried with several cables on several computers, did you install the drivers each time ? Was it on different operating system ? I'm not sure if you have to install drivers with Linux, I mainly use windows.

Sounds like it's an hardware issue, I just want to make sure. If it's the case, we can do replacement. Until then, you can still use the micro SD card to load programs. I'm sorry for the inconvenience.

[ziirish]

Hi,

Yes, I tried many configurations.
A non-exhaustive list here:

• Linux debian jessie 64bit with the stock cable on computer1
• Linux debian jessie 64bit with another cable (the one from my mobile phone which works well for adb and so on) on computer1
• Linux ubuntu 13.04 64bit with stock cable on computer2
• Linux ubuntu 13.04 64bit with my mobile phone cable on computer2
• Linux ubuntu 14.04 32bit with stock cable on computer3
• Linux ubuntu 14.04 32bit with my mobile phone cable on computer3
• Windows 7 64bit with stock cable on computer4
• Windows 7 64bit with my mobile phone cable on computer4

On Linux it looks like the drivers are embedded within the kernel so I just installed the Arduino IDE v1.0.5
On Windows I followed the documentation, installing the Arduino IDE, connecting my gamebuino powered-on and waiting for the windows install driver process to begin, but it never happened. So I looked at the device manager and didn't see any "COM" entry.

When plugged-in the two RX/TX leds are flashing very briefly but only once, not twice.

[jonnection]

I think that is really a hardware issue. The error you are getting means the device is failing USB detection completely. The 1 flash you see is the USB port inquiring for the device. According to the demesg log, it never gets a reply.

Is your Gamebuino working otherwise ? I.e. does the battery get charge and are you able to power on w/o the USB cable ?

[ziirish]

Yes I'm afraid this is a hardware issue too.

Beside the USB/COM issue, the gamebuino is working well, The charging leds are OK. When the gamebuino is fully loaded it switches to the right one. I can play without connecting the USB cable meaning the battery is OK too, and I can load the games present on the SD card.

[rodot]

OK, then please send me a message through the shop's contact form if you want a replacement. I'm sorry for the inconvenience.

[ziirish]

I sent you a message through your shot/contact page but I'm not sure you received it because I received a "Mail delivery failed" notice...

Let me know if I should retry later.