I was trying to get my USB IR Toy to work today.
Firmware 22 (V222). Tried reflashing it a few times to see if it helps.
I'm seeing a lot of USB issues.
At first, it comes on normal:
[ 4144.077994] usb 2-3: new full-speed USB device number 25 using xhci_hcd
[ 4144.097305] usb 2-3: New USB device found, idVendor=04d8, idProduct=fd08
[ 4144.097315] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4144.097320] usb 2-3: Product: CDC Test
[ 4144.097324] usb 2-3: Manufacturer: Dangerous Prototypes
[ 4144.097328] usb 2-3: SerialNumber: 00000001
[ 4144.098015] cdc_acm 2-3:1.0: This device cannot do calls on its own. It is not a modem.
[ 4144.098046] cdc_acm 2-3:1.0: ttyACM0: USB ACM device
But after playing with it for a while, it quits:
[ 5468.244296] xhci_hcd 0000:00:14.0: Timeout while waiting for stop endpoint command
This is still not fatal. Then:
[ 6121.566972] usb 2-3: reset full-speed USB device number 25 using xhci_hcd
[ 6125.505932] xhci_hcd 0000:00:14.0: Signal while waiting for address device command
[ 6125.706879] xhci_hcd 0000:00:14.0: Signal while waiting for address device command
[ 6125.911078] usb 2-3: device not accepting address 25, error -62
[ 6126.023201] xhci_hcd 0000:00:14.0: Signal while waiting for reset device command
[ 6126.023231] usb 2-3: reset full-speed USB device number 25 using xhci_hcd
[ 6126.023241] xhci_hcd 0000:00:14.0: Signal while waiting for address device command
[ 6126.227368] xhci_hcd 0000:00:14.0: Signal while waiting for address device command
[ 6126.431599] usb 2-3: device not accepting address 25, error -62
[ 6126.543722] xhci_hcd 0000:00:14.0: Signal while waiting for reset device command
[ 6126.543748] usb 2-3: reset full-speed USB device number 25 using xhci_hcd
[ 6126.543757] xhci_hcd 0000:00:14.0: Signal while waiting for address device command
[ 6126.747923] xhci_hcd 0000:00:14.0: Signal while waiting for address device command
[ 6126.952121] usb 2-3: device not accepting address 25, error -62
[ 6127.064239] xhci_hcd 0000:00:14.0: Signal while waiting for reset device command
[ 6127.064263] usb 2-3: reset full-speed USB device number 25 using xhci_hcd
[ 6127.064272] xhci_hcd 0000:00:14.0: Signal while waiting for address device command
[ 6127.268442] xhci_hcd 0000:00:14.0: Signal while waiting for address device command
[ 6127.472641] usb 2-3: device not accepting address 25, error -62
[ 6127.472736] usb 2-3: USB disconnect, device number 25
[ 6127.473204] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88037c98c1c0
[ 6127.473212] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880409e82f80
[ 6127.473216] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880409e82fc0
[ 6127.640821] usb 2-3: new full-speed USB device number 26 using xhci_hcd
[ 6132.645713] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[ 6137.855035] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[ 6138.059241] usb 2-3: device not accepting address 26, error -62
[ 6138.171367] usb 2-3: new full-speed USB device number 27 using xhci_hcd
[ 6143.176367] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[ 6148.385585] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[ 6148.589765] usb 2-3: device not accepting address 27, error -62
[ 6148.701916] usb 2-3: new full-speed USB device number 28 using xhci_hcd
[ 6153.706874] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[ 6158.916090] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[ 6159.120337] usb 2-3: device not accepting address 28, error -62
[ 6164.125350] xhci_hcd 0000:00:14.0: Timeout while waiting for a slot
[ 6164.125366] hub 2-0:1.0: couldn't allocate port 3 usb_device
Now it's gone. And my USB is dead. Reconnecting it:
[ 6164.125350] xhci_hcd 0000:00:14.0: Timeout while waiting for a slot
[ 6164.125366] hub 2-0:1.0: couldn't allocate port 3 usb_device
[ 6234.291599] xhci_hcd 0000:00:14.0: Timeout while waiting for a slot
[ 6234.291614] hub 2-0:1.0: couldn't allocate port 3 usb_device
[ 6253.018359] xhci_hcd 0000:00:14.0: Timeout while waiting for a slot
[ 6253.018375] hub 2-0:1.0: couldn't allocate port 3 usb_device
[ 6310.375771] xhci_hcd 0000:00:14.0: Timeout while waiting for a slot
[ 6310.375777] hub 2-0:1.0: couldn't allocate port 3 usb_device
[ 6320.617515] usb 2-2: USB disconnect, device number 19
And Linux eventually just killed off that hub, with everything on it (also a keyboard dongle):
[ 6325.623068] xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command.
[ 6325.623079] xhci_hcd 0000:00:14.0: Assuming host is dying, halting host.
[ 6325.623128] xhci_hcd 0000:00:14.0: HC died; cleaning up
[ 6325.707447] usb 2-4: USB disconnect, device number 7
[ 6325.951715] usb 2-10: USB disconnect, device number 8
So, is this normal?
Can I do something about it?
Have you tried to use any alternative device on that USB port ?
Have you tried to use USB IR Toy on any other computer arround ?
But after playing with it for a while, it quits:
It could depend on this. What software are you using etc?
[quote author="AnalysIR"]
But after playing with it for a while, it quits:
It could depend on this. What software are you using etc?[/quote]
Software that pokes with /dev/ttyUSB0. Nothing very advanced, was trying to get it to do the basic function of recording and transmitting a signal. Didn't get that far. (I started to write my own, because the original examples are very slow and somewhat buggy.)
[quote author="acosmo"]Have you tried to use any alternative device on that USB port ?
Have you tried to use USB IR Toy on any other computer arround ?[/quote]
Since I use remote keyboards and USB sticks all the time and leave my computers on for weeks, yes, I have used other device on the same USB port.
The only other computer around at that time was a computer I rather not hang in any way, so no.
Should I take your answers as that this isn't normal?
Maybe look at the source for IRtoy.exe and relplicate what is being done there.
Some interacations may be time critical, particularly when sending IR. I found that sending IR was the biggest challenge, so why not try just in receive mode to see can you isolate the problem a bit. Alternatively, just us with a known/working piece of software so you can eliminate the device and the PC.
I haven't played with it on Linux, but on Windows - ensuring the correct driver & firmware is installed helps.
I can't comment on having it plugged in over longer periods as I typically am plugging it in an out all the time for testing and never have it plugged in 24x7.
I'm a bit confused if irtoy.exe and similar tools can cause these issues. Linux is kicking out the USB subsystem because the ir-toy behaves so bad that entire bus goes down. As far as I can see the software side is only trying to use the ir-toy as a serial port.