Mysterious
Posts: 13
Joined: Fri Feb 22, 2013 11:34 am

Re: USB FIQ testing....

Sat Jul 06, 2013 8:17 pm

Hi,

I want to code a little workaround for my soundcard's driver (which i mentioned before). Unfortunately I am not so into USB. Thus I would like you to tell me if the workaround I am considering is possible...

Workaround idea:
Due to "esoteric" many endpoints I thought of ignoring all unneeded endpoints (in scheduling) and keep talking to one pcm 44.1khz output endpoint.

Might not work:
- because there is a fixed scheduling on the soundcard's side that expects communication with all endpoints. (for example synchronizing the endpoints although no audio data is send or somewhat)
- the soundcard needs at least some endpoints for control tasks (possibly like usage of volume control) => (would it sound better if only the control endpoint and output endpoint were used)

Thank you very much in advance

P.S.: Sigh.... that all these people need to get personal...

aaddame
Posts: 3
Joined: Sat Jul 13, 2013 3:00 pm

Re: USB FIQ testing....

Sun Jul 14, 2013 8:29 am

gsh wrote:
GrayShade wrote:Hello,

PS: How do I get a specific version with rpi-update? I tried overwriting the files from /boot with the ones in /boot.bak, but I got an older version than my previous one.
I assume you're using BRANCH=next already? We've integrated the new fiq_split fixes into the next branch (3.9) which may be causing the problem... try fiq_split_enable=0 on the command line if you're using that...

Also dmesg | grep fiq

Would be useful output

Gordon
After switching to the NEXT branch, kernel modules are missing. See my post "missing modules" on this

gsh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1465
Joined: Sat Sep 10, 2011 11:43 am

Re: USB FIQ testing....

Sun Jul 14, 2013 8:42 am

Actually the fixes are on the head branch as well...

Gordon
--
Gordon Hollingworth PhD
Raspberry Pi - Director of Software Engineering

aaddame
Posts: 3
Joined: Sat Jul 13, 2013 3:00 pm

Re: USB FIQ testing....

Mon Jul 15, 2013 9:27 am

Right, I reverted to the main branch and added "dwc_otg.microframe_schedule=1 dwc_otg.speed=1 dwc_otg.fiq_fix_enable=1" to cmdline.txt.
Seems my USB issues are gone now.
Is there a description somewhere about the meaning of these parameters???

kalehrl
Posts: 350
Joined: Tue Jul 24, 2012 10:49 am

Re: USB FIQ testing....

Mon Jul 15, 2013 12:56 pm

dwc_otg.speed=1
forces USB ports to be 1.0 - pretty slow compared to 2.0.
I'm not sure about the rest.

gsh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1465
Joined: Sat Sep 10, 2011 11:43 am

Re: USB FIQ testing....

Mon Jul 15, 2013 1:20 pm

Yes,

microframe schedule and fiq split are enabled by default so you can get rid of those. The selection of USB 1 will fix the problem since the issue is specific about the way USB 2 and 1 speeds are dealt with, but as said, will slow down everything!

If you get rid of those three it should still work correctly with the head branch

Gordon
--
Gordon Hollingworth PhD
Raspberry Pi - Director of Software Engineering

User avatar
jackokring
Posts: 816
Joined: Tue Jul 31, 2012 8:27 am
Location: London, UK
Contact: ICQ

Re: USB FIQ testing....

Mon Jul 15, 2013 1:26 pm

After power cycling the hub, and hence the dongle of da WiFi, I no longer get errors. I assume the errors are due to not having a full device reinitialize on reboot. No errors today, slightly faster, boot and ssh response with -X.

FIQing excellent work! :D
Pi[NFA]=B256R0USB CL4SD8GB Raspbian Stock.
Pi[Work]=A+256 CL4SD8GB Raspbian Stock.
My favourite constant 1.65056745028

gsh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1465
Joined: Sat Sep 10, 2011 11:43 am

Re: USB FIQ testing....

Wed Jul 17, 2013 12:20 pm

Just to note to those interested, there have been a number of fixes to the FIQ code recently which are currently in the latest rpi-update version.

Also I've fixed the function tracing with FIQ enabled and checked it into github (it is not yet reflected in rpi-update)

Gordon
--
Gordon Hollingworth PhD
Raspberry Pi - Director of Software Engineering

MattF
Posts: 55
Joined: Tue Feb 12, 2013 10:01 am

Re: USB FIQ testing....

Wed Jul 17, 2013 1:07 pm

Hi Gordon,

I'm having to maintain a local tree for aufs support.

Are all the fixes commited to https://github.com/raspberrypi/linux/commits/rpi-3.10.y ?

Thanks,

Matt

gsh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1465
Joined: Sat Sep 10, 2011 11:43 am

Re: USB FIQ testing....

Wed Jul 17, 2013 1:14 pm

The ftrace fix is currently only pushed to rpi-3.6.y. But otherwise the USB fixes are pushed to all branches

Gordon
--
Gordon Hollingworth PhD
Raspberry Pi - Director of Software Engineering

sbp
Posts: 128
Joined: Wed Sep 26, 2012 7:54 pm

Re: USB FIQ testing....

Wed Jul 17, 2013 6:27 pm

Hi gsh.
Thank you for the work on the USB problems. Just a quick question.

I noticed that you now has pushed the newest fix into the 3.9.y, I'm currently fetching it via git, but it is very slow, it is much faster getting the 3.9.y version through the wget command, but I don't know it that will be the latest version.
Cold you inform me if there is a delay between a change in the github and the one that we get using wget github.com/raspberry/Linux/archive/rip-3.9.y.tar.gz?
piCorePlayer webpage: https://sites.google.com/site/picoreplayer/home

gsh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1465
Joined: Sat Sep 10, 2011 11:43 am

Re: USB FIQ testing....

Wed Jul 17, 2013 8:06 pm

I was under the impression I had checked the fix into 3.6.y but anyway, you can do:

git clone http://github.com/raspberrypi/linux.git --branch=rpi-3.6.y --depth=1

This will limit it to only check out that branch and it won't check out the complete history

Gordon
--
Gordon Hollingworth PhD
Raspberry Pi - Director of Software Engineering

jdb
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2213
Joined: Thu Jul 11, 2013 2:37 pm

Re: USB FIQ testing....

Thu Jul 18, 2013 10:31 pm

To anyone using USB audio DACs:

The current FIQ implementation will make USB audio sound cards/DACs play very choppy/distorted/static sound if all of the following conditions are met:

- You have a hub with a single Transaction Translator (cheap chip inside)
- You plug another full speed/low speed device into the same hub that your USB sound card is plugged into.
- The other full/low speed devices have periodic endpoints (pretty much all mice/keyboards, other USB sound cards, etc)

You can check if your hub is a "bad" one by doing e.g.

Code: Select all

lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 012: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub
Bus 001 Device 015: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like Sound Device
Bus 001 Device 016: ID 05dc:a761 Lexar Media, Inc.
Bus 001 Device 014: ID 045e:0768 Microsoft Corp. Sidewinder X4
Then looking at the Device 012 line (my external hub) - the device ID is 1a40:0201

Code: Select all

sudo lsusb -v -d 1a40:0201 | grep bInterfaceProtocol
      bInterfaceProtocol      1 Single TT
      bInterfaceProtocol      2 TT per port
"Good" hubs will have both lines. "Bad" hubs will have only Single TT mode.

One of the issues I'm looking at whether it will be possible to cater for single-TT hubs in the driver, to at least get a "better" state of affairs.

USB sound cards that use Asynchronous Isochronous endpoints (that employ a feedback mechanism for rate adaptive behaviour) will probably also be adversely affected - these are typically the more expensive devices. The two issues are somewhat related.

If you have a USB audio device that does not work, or breaks if you plug in another device please post the full output of sudo lsusb -v and dmesg.
Rockets are loud.
https://astro-pi.org

GrayShade
Posts: 39
Joined: Fri Jul 05, 2013 6:13 am

Re: USB FIQ testing....

Fri Jul 19, 2013 4:48 am

I only have the DAC and it seems it doesn't have asynchronous endpoints for playback:

dmesg output: http://pastebin.com/jVaZVNEd
lsusb output: http://pastebin.com/UsKWaZJF

jdb
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2213
Joined: Thu Jul 11, 2013 2:37 pm

Re: USB FIQ testing....

Fri Jul 19, 2013 9:04 am

GrayShade wrote:I only have the DAC and it seems it doesn't have asynchronous endpoints for playback:

dmesg output: http://pastebin.com/jVaZVNEd
lsusb output: http://pastebin.com/UsKWaZJF
What audio format are you playing? Sample rate/bitrate? I mean the source audio, not what you set ALSA to.
Rockets are loud.
https://astro-pi.org

GrayShade
Posts: 39
Joined: Fri Jul 05, 2013 6:13 am

Re: USB FIQ testing....

Fri Jul 19, 2013 9:08 am

SND_PCM_FORMAT_S16_LE at 44.1 KHz. I described my problem in a post on the previous page; basically I'm getting choppy sound when there's a lot of data coming from the network. fiq_split_enable=0 fixes it.

And I won't even start on SD card corruption issues and network not working sometimes :).

gsh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 1465
Joined: Sat Sep 10, 2011 11:43 am

Re: USB FIQ testing....

Fri Jul 19, 2013 9:58 am

@GrayShade

Have you updated to the latest kernel with rpi-update?

Check SDCard corruption again... We've fixed a bug in the driver in the last week, I'd be interested in whether you still get SDCard corruption now?

Thanks

Gordon
--
Gordon Hollingworth PhD
Raspberry Pi - Director of Software Engineering

GrayShade
Posts: 39
Joined: Fri Jul 05, 2013 6:13 am

Re: USB FIQ testing....

Fri Jul 19, 2013 10:07 am

@gsh

I've seen the commit from July 11, but if i recall correctly the last time it happened to me was on Friday.

Right now I'm using the next branch because it seems to help somewhat with another weird issue I had with ALSA.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5397
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: USB FIQ testing....

Fri Jul 19, 2013 10:30 am

GrayShade wrote:@gsh

I've seen the commit from July 11, but if i recall correctly the last time it happened to me was on Friday.

Right now I'm using the next branch because it seems to help somewhat with another weird issue I had with ALSA.
Latest "next" branch has sdcard fix in too.

richtoy
Posts: 14
Joined: Tue Jun 05, 2012 8:35 pm

Re: USB FIQ testing....

Fri Jul 19, 2013 6:22 pm

First off, great work on the usb driver, for me it is generally very stable but a few questions: -

I have a hama 7 port hub

lsusb gives this

Code: Select all

[email protected] ~ $ lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. 
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 005: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
Bus 001 Device 006: ID 1997:1221  
Bus 001 Device 007: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
which I think means that there are 2 4 port hubs daisy chained together

however, interrogating one of the hubs gives no indication of there being a Transaction Translator

Code: Select all

[email protected] ~ $ sudo lsusb -v -d 05e3:0608 | grep bInterfaceProtocol
      bInterfaceProtocol      0 Full speed (or root) hub
      bInterfaceProtocol      0 Full speed (or root) hub
what does this mean?
greping for TT gives this

Code: Select all

sudo lsusb -v -d 05e3:0608 | grep TT
  bDeviceProtocol         1 Single TT
    TT think time 32 FS bits
  bDeviceProtocol         1 Single TT
    TT think time 32 FS bits
and this is the full output

Code: Select all

[email protected] ~ $ sudo lsusb -v -d 05e3:0608

Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         1 Single TT
  bMaxPacketSize0        64
  idVendor           0x05e3 Genesys Logic, Inc.
  idProduct          0x0608 USB-2.0 4-Port HUB
  bcdDevice           77.64
  iManufacturer           0 
  iProduct                1 USB2.0 Hub
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval              12
Hub Descriptor:
  bLength               9
  bDescriptorType      41
  nNbrPorts             4
  wHubCharacteristic 0x00e0
    Ganged power switching
    Ganged overcurrent protection
    TT think time 32 FS bits
    Port indicators
  bPwrOn2PwrGood       50 * 2 milli seconds
  bHubContrCurrent    100 milli Ampere
  DeviceRemovable    0x00
  PortPwrCtrlMask    0xff
 Hub Port Status:
   Port 1: 0000.0503 highspeed power enable connect
   Port 2: 0000.0303 lowspeed power enable connect
   Port 3: 0000.0100 power
   Port 4: 0000.0503 highspeed power enable connect
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         0 Full speed (or root) hub
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered

Bus 001 Device 007: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         1 Single TT
  bMaxPacketSize0        64
  idVendor           0x05e3 Genesys Logic, Inc.
  idProduct          0x0608 USB-2.0 4-Port HUB
  bcdDevice           77.64
  iManufacturer           0 
  iProduct                1 USB2.0 Hub
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval              12
Hub Descriptor:
  bLength               9
  bDescriptorType      41
  nNbrPorts             4
  wHubCharacteristic 0x00e0
    Ganged power switching
    Ganged overcurrent protection
    TT think time 32 FS bits
    Port indicators
  bPwrOn2PwrGood       50 * 2 milli seconds
  bHubContrCurrent    100 milli Ampere
  DeviceRemovable    0x00
  PortPwrCtrlMask    0xff
 Hub Port Status:
   Port 1: 0000.0103 power enable connect
   Port 2: 0000.0100 power
   Port 3: 0000.0100 power
   Port 4: 0000.0100 power
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         0 Full speed (or root) hub
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered
I have never seen anything like this level of detail in a spec sheet for a hub, do you have a list of the "best" hubs?

jdb
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2213
Joined: Thu Jul 11, 2013 2:37 pm

Re: USB FIQ testing....

Fri Jul 19, 2013 7:47 pm

Oh - oops

Yes, for single TT hubs they will only have one interface and so will omit the interface descriptor(s). bDeviceProtocol is the field to use. For comparison:

Code: Select all

sudo lsusb -v -d 1a40:0101 | grep bDeviceProtocol
  bDeviceProtocol         1 Single TT
  bDeviceProtocol         0 Full speed (or root) hub

Code: Select all

sudo lsusb -v -d 1a40:0201  | grep bDeviceProtocol
  bDeviceProtocol         2 TT per port
  bDeviceProtocol         0 Full speed (or root) hub
Two hubs from the same manufacturer, one with multiple TT, the other with single TT.
Rockets are loud.
https://astro-pi.org

User avatar
jbeale
Posts: 3578
Joined: Tue Nov 22, 2011 11:51 pm
Contact: Website

Re: USB FIQ testing....

Fri Jul 19, 2013 10:04 pm

richtoy wrote:I have never seen anything like this level of detail in a spec sheet for a hub, do you have a list of the "best" hubs?
Here is an example of a 7-port hub that actually specifies it has multiple TTs. At $30 it is certainly not the cheapest available, but maybe you get what you pay for. http://www.amazon.com/gp/product/B004Y3 ... UTF8&psc=1

richtoy
Posts: 14
Joined: Tue Jun 05, 2012 8:35 pm

Re: USB FIQ testing....

Sat Jul 20, 2013 11:44 am

jbeale wrote:
richtoy wrote:I have never seen anything like this level of detail in a spec sheet for a hub, do you have a list of the "best" hubs?
Here is an example of a 7-port hub that actually specifies it has multiple TTs. At $30 it is certainly not the cheapest available, but maybe you get what you pay for. http://www.amazon.com/gp/product/B004Y3 ... UTF8&psc=1
Unfortunately I don't find this one or the 4 port offering from amazon available with either EU or UK power supply :(

Does anyone know of any others that are Multi TT but don't advertise the fact?

jdb
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2213
Joined: Thu Jul 11, 2013 2:37 pm

Re: USB FIQ testing....

Sat Jul 20, 2013 9:18 pm

I've identified two root causes of issues relating to USB audio DACs - one that was always there (caused by high interrupt loading), the other that was brought to the fore by the way the split-transaction allocation now works with the FIQ.

These aren't going to be quick or simple fixes.

For mitigation in the meantime, perhaps try running without fiq_split_enable - set dwc_otg.fiq_split_enable=0 in cmdline.txt.
Rockets are loud.
https://astro-pi.org

j.deBree
Posts: 1
Joined: Sun Jul 28, 2013 5:39 pm

Re: USB FIQ testing....

Sun Jul 28, 2013 5:57 pm

I am also having USB problems with a rtl2832 DVB device, Terratec Cinergy T-Stick RC rev.3.
I think it might be related to the rpi because on my linux desktop it works perfectly.
When I try to do a simple channel scan with w_scan it doesn't find anything on the rpi.
There are no errors in dmesg or syslog.
I tried all sort of kernels, including self-compiled, nothing helps. Tried all possible cmdlines.txt options regarding USB, didn't help either.
Tried the stick directly or with two diferent powered usb-hubs, still nothing.
Voltage was 4,65 Volt on the usb port, but don't think that's the problem because of the powered hubs.
Also tried an usb trace, but I don't understand any of the output.
Here's lsusb -v:

Code: Select all

Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         2 TT per port
  bMaxPacketSize0        64
  idVendor           0x0424 Standard Microsystems Corp.
  idProduct          0x9512 
  bcdDevice            2.00
  iManufacturer           0 
  iProduct                0 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           41
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      1 Single TT
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval              12
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       1
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      2 TT per port
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval              12
Hub Descriptor:
  bLength               9
  bDescriptorType      41
  nNbrPorts             3
  wHubCharacteristic 0x000d
    Per-port power switching
    Compound device
    Per-port overcurrent protection
    TT think time 8 FS bits
  bPwrOn2PwrGood       50 * 2 milli seconds
  bHubContrCurrent      1 milli Ampere
  DeviceRemovable    0x02
  PortPwrCtrlMask    0xff
 Hub Port Status:
   Port 1: 0000.0503 highspeed power enable connect
   Port 2: 0000.0303 lowspeed power enable connect
   Port 3: 0000.0503 highspeed power enable connect
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         0 Full speed (or root) hub
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         1 Single TT
  bMaxPacketSize0        64
  idVendor           0x1d6b Linux Foundation
  idProduct          0x0002 2.0 root hub
  bcdDevice            3.09
  iManufacturer           3 Linux 3.9.10+ dwc_otg_hcd
  iProduct                2 DWC OTG Controller
  iSerial                 1 bcm2708_usb
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0004  1x 4 bytes
        bInterval              12
Hub Descriptor:
  bLength               9
  bDescriptorType      41
  nNbrPorts             1
  wHubCharacteristic 0x0008
    Ganged power switching
    Per-port overcurrent protection
    TT think time 8 FS bits
  bPwrOn2PwrGood        1 * 2 milli seconds
  bHubContrCurrent      0 milli Ampere
  DeviceRemovable    0x00
  PortPwrCtrlMask    0xff
 Hub Port Status:
   Port 1: 0000.0503 highspeed power enable connect
Device Status:     0x0003
  Self Powered
  Remote Wakeup Enabled

Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass         0 
  bDeviceProtocol         1 
  bMaxPacketSize0        64
  idVendor           0x0424 Standard Microsystems Corp.
  idProduct          0xec00 
  bcdDevice            2.00
  iManufacturer           0 
  iProduct                0 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0 
      bInterfaceProtocol    255 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval               4
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass         0 
  bDeviceProtocol         1 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered

Bus 001 Device 005: ID 0a81:0101 Chesen Electronics Corp. Keyboard
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x0a81 Chesen Electronics Corp.
  idProduct          0x0101 Keyboard
  bcdDevice            1.10
  iManufacturer           1 CHESEN
  iProduct                2 USB Keyboard
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           59
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      1 Keyboard
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode           33 US
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      65
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode           33 US
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength     102
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
Device Status:     0x0000
  (Bus Powered)

Bus 001 Device 010: ID 0ccd:00d3 TerraTec Electronic GmbH 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0ccd TerraTec Electronic GmbH
  idProduct          0x00d3 
  bcdDevice            1.00
  iManufacturer           1 Realtek
  iProduct                2 RTL2838UHIDIR
  iSerial                 3 00000001
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           34
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          4 USB2.0-Bulk&Iso
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              5 Bulk-In, Interface
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              5 Bulk-In, Interface
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      2
Device Status:     0x0000
  (Bus Powered)
I hope anybody has an idea I could try out.

Return to “Troubleshooting”