S110 hardware\software error - (Device descriptor request failed) - General Help and Assistance on using CHDK stable releases - CHDK Forum

S110 hardware\software error - (Device descriptor request failed)

  • 14 Replies
  • 11338 Views
Advertisements
Hi,
recently I purchased a new Canon s110 after the older one (few months old) was sent to repairing.
Today after 2 weeks of use, with CHDK i found the new camera in the same condition as the one before it.

When I connect it to the PC (windows 8.1) I get a pop-up that says:
"USB DEVICE NOT RECOGNIZED - the last usb device you connected to this computer malfunctioned..."


and in the device manager:
Unknown USB device (Device Descriptor Request Failed)


As I mentioned already, both cameras ended in the same condition, both after being used only with CHDK and chdkptp protocol. Both were good taken care of, and didn't suffer from any kind of abuse, bump or anything similar.

Please let me know if you have any kind of suspect for the cause to this malfunction.
The warranty did take care of the first one buy I can't afford continuing with this ritual.

Thanks,
Nadav
« Last Edit: 09 / May / 2014, 14:51:38 by nadavofi »

*

Offline srsa_4c

  • ******
  • 4451
Re: S110 hardware\software error - (Device descriptor request failed)
« Reply #1 on: 09 / May / 2014, 16:03:04 »
Have you tried connecting the camera to a different PC? Either with or without libusb?

*

Offline reyalp

  • ******
  • 14128
Re: S110 hardware\software error - (Device descriptor request failed)
« Reply #2 on: 10 / May / 2014, 00:07:36 »
Have you tried connecting the camera to a different PC? Either with or without libusb?
I definitely second this. Preferably with a PC that doesn't have any libusb stuff on it, or a linux system.

If you haven't already, also try without CHDK loaded.
Don't forget what the H stands for.

Re: S110 hardware\software error - (Device descriptor request failed)
« Reply #3 on: 10 / May / 2014, 01:38:33 »
Quote
  Have you tried connecting the camera to a different PC? Either with or without libusb?I definitely second this. Preferably with a PC that doesn't have any libusb stuff on it, or a linux system.If you haven't already, also try without CHDK loaded.

Well I did try all of those. Including different types of USB ports.
Tryed removing rhe CHDK card
And tryed connecting to a linux computer (Odroid)

All of them gave the same error message regarding the "descriptor" issue.

Re: S110 hardware\software error - (Device descriptor request failed)
« Reply #4 on: 10 / May / 2014, 07:23:27 »
Connected it to the Linux operated ODROID computer

USING USB 3.0

Code: [Select]
[   65.367363] usb 5-1: new full-speed USB device number 2 using exynos-xhci
[   65.367551] usb 5-1: Device not responding to set address.
[   65.572431] usb 5-1: Device not responding to set address.
[   65.777359] usb 5-1: device not accepting address 2, error -71
[   65.887343] usb 5-1: new full-speed USB device number 3 using exynos-xhci
[   65.887553] usb 5-1: Device not responding to set address.
[   66.092481] usb 5-1: Device not responding to set address.
[   66.297332] usb 5-1: device not accepting address 3, error -71
[   66.407327] usb 5-1: new full-speed USB device number 4 using exynos-xhci
[   66.407505] usb 5-1: Device not responding to set address.
[   66.612425] usb 5-1: Device not responding to set address.
[   66.817346] usb 5-1: device not accepting address 4, error -71
[   66.927317] usb 5-1: new full-speed USB device number 5 using exynos-xhci
[   66.927501] usb 5-1: Device not responding to set address.
[   67.132524] usb 5-1: Device not responding to set address.
[   67.337307] usb 5-1: device not accepting address 5, error -71
[   67.341768] hub 5-0:1.0: unable to enumerate USB device on port 1

USING USB 2.0

Code: [Select]
[  106.822623] usb 1-3.2: new full-speed USB device number 4 using s5p-ehci
[  106.907603] usb 1-3.2: device descriptor read/64, error -32
[  107.097635] usb 1-3.2: device descriptor read/64, error -32
[  107.287627] usb 1-3.2: new full-speed USB device number 5 using s5p-ehci
[  107.372617] usb 1-3.2: device descriptor read/64, error -32
[  107.562637] usb 1-3.2: device descriptor read/64, error -32
[  107.752656] usb 1-3.2: new full-speed USB device number 6 using s5p-ehci
[  108.162336] usb 1-3.2: device not accepting address 6, error -32
[  108.237579] usb 1-3.2: new full-speed USB device number 7 using s5p-ehci
[  108.647276] usb 1-3.2: device not accepting address 7, error -32
[  108.651952] hub 1-3:1.0: unable to enumerate USB device on port 2

I have 2 suspected causes I'd like to share with you:

1. This camera is being set on a Gimbals which moves a lot, while it's connected via USB to the Odroid.
maybe after a while it caused a physical damage to the connection, and made it shorten.

2. I was running chdkptp with -c followed by a 'remoteshoot -cont=6000', then after a while I run a new chdkptp command with -c followed by a 'killscript' command.
Reyalp, you told me it's shouldn't work since only one connection can be established at a time but it did work...

In your opinion, can anyone of this scenarios be the cause of the Descriptor mismatch?



In addition, since we will probably have to buy another camera (the third one), and there is a chance we will not be able to guarantee it won't end the same as the last two, we might be interested in trying another camera.
This camera must be:
Compact (S110 like)
Capture high res pictures (~12MP)
to fully support CHDK
to be able to: shoot continuously, focus manually, have a Manual mode for shutter and aperture preset.
Do you know any camera that will cover all of those requirements?


We are very short in time, so I hope you can help me pass this crisis quickly, thank you very much for your support!

Nadav

*

Offline srsa_4c

  • ******
  • 4451
Re: S110 hardware\software error - (Device descriptor request failed)
« Reply #5 on: 10 / May / 2014, 08:37:03 »
Connected it to the Linux operated ODROID computer
(...)
Thanks for the logs, that's certainly more information than the Windows error messages.
Note that "full speed" USB device is mentioned (<=12Mb/s), your camera is normally a "high speed" (<=480Mb/s) device. I suspect a hw issue, perhaps related to what you are suspecting (USB socket partially disconnected from the PCB).

You can also dump the camera's firmware, but I find it extremely unlikely that it would be damaged (not to mention the damage would have to be equal in the 2 cameras).
To make absolutely sure, dump your next cam's firmware before using CHDK, and if it develops an issue later, another dump could show whether or not it's firmware corrruption related.

Try to fixate the USB plug to the camera when it's on the plane, so there's less chance for vibrations damaging the connector.

This camera must be:
Compact (S110 like)
Capture high res pictures (~12MP)
to fully support CHDK
to be able to: shoot continuously, focus manually, have a Manual mode for shutter and aperture preset.
That's something only the S series offer (S100?).

Questions.
When did you first notice the problem (in either case), was the cam surely working correctly before?
Do you happen to use an AC power supply for the camera?

Re: S110 hardware\software error - (Device descriptor request failed)
« Reply #6 on: 10 / May / 2014, 09:27:56 »
Quote
Questions.
When did you first notice the problem (in either case), was the cam surely working correctly before?

It was working perfectly, but it we did have some photos missing in the end of the flight.
Is it possible that during the flight and the vibrations the connection was lost and renewed so we got, lets say, IMG_1000 & IMG_1002 (missing IMG_1001?) and then the camera continued like nothing has happened?

Quote
Do you happen to use an AC power supply for the camera?
NOP. we're using the originally provided battery.

Nadav.

*

Offline srsa_4c

  • ******
  • 4451
Re: S110 hardware\software error - (Device descriptor request failed)
« Reply #7 on: 10 / May / 2014, 09:39:42 »
It was working perfectly, but it we did have some photos missing in the end of the flight.
Is it possible that during the flight and the vibrations the connection was lost and renewed so we got, lets say, IMG_1000 & IMG_1002 (missing IMG_1001?) and then the camera continued like nothing has happened?
I think so. You don't happen to have the syslogs made during that flight, I suppose? Connection problems would show up there.

Re: S110 hardware\software error - (Device descriptor request failed)
« Reply #8 on: 10 / May / 2014, 09:45:54 »
I probably don't.
What is a syslog? where should it be printed\located?

Re: S110 hardware\software error - (Device descriptor request failed)
« Reply #9 on: 10 / May / 2014, 09:49:29 »
This camera must be:
Compact (S110 like)
Capture high res pictures (~12MP)
to fully support CHDK
to be able to: shoot continuously, focus manually, have a Manual mode for shutter and aperture preset.
That's something only the S series offer (S100?).
If you are willing to live with CHDK providing the manual focus and exposure, and with not having an adjustable aperture, then the little IXUS/ELPH cameras like the IXUS140_ELPH130 might work for you - and for a lot less money.
Ported :   A1200    SD940   G10    Powershot N    G16

 

Related Topics


SimplePortal © 2008-2014, SimplePortal