XIMEA USB2.0 camera not recognised on TUSB4041 USB2.0 hub

Hi

We have designed a custom TX2 carrier board which features a Texas Instruments TUSB4041 hub to split one upstream USB2.0 port into four downstream.

When Ubuntu loads, it identifies the TUSB4041 USB2.0 hub as a TUSB8041 USB3.0 hub (per the datasheets both devices have the same VID:PID of 0451:8142)

Various USB2.0 devices (mass storage devices) are identified succesfully and visible using lsusb, but our XIMEA USB2.0 camera is not visible when connected directly to the downstream ports. Strangely, if the camera is connected via another external standalone hub it appears.

With the camera attached directly, dmesg shows the following error messages:

[ 56.580451] usb 1-1.2: new high-speed USB device number 3 using xhci-tegra
[ 56.660688] usb 1-1.2: device descriptor read/64, error -71
[ 56.840673] usb 1-1.2: device descriptor read/64, error -71
[ 57.020450] usb 1-1.2: new high-speed USB device number 4 using xhci-tegra
[ 57.100680] usb 1-1.2: device descriptor read/64, error -71
[ 57.280681] usb 1-1.2: device descriptor read/64, error -71
[ 57.460471] usb 1-1.2: new high-speed USB device number 5 using xhci-tegra
[ 57.467882] usb 1-1.2: Device not responding to setup address.
[ 57.676887] usb 1-1.2: Device not responding to setup address.
[ 57.884463] usb 1-1.2: device not accepting address 5, error -71
[ 57.960471] usb 1-1.2: new high-speed USB device number 6 using xhci-tegra
[ 57.967894] usb 1-1.2: Device not responding to setup address.
[ 57.995575] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work mailbox command 5
[ 58.002612] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work ignore firmware MBOX_CMD_DEC_SSPI_CLOCK request
[ 58.176885] usb 1-1.2: Device not responding to setup address.
[ 58.384464] usb 1-1.2: device not accepting address 6, error -71
[ 58.390734] usb 1-1-port2: unable to enumerate USB device

So the questions are:

  1. Is the TUSB4041 compatible with the TUSB8041, even though the former doesn’t support Super speed?
  2. Are the dmesg error messages being caused by the camera, or the hub?

Thanks and regards

Bob Stiles

What you are describing might be a signal quality issue (the addition of a HUB tends to suggest this), but it is hard to say since I do not know what the various error codes are. I’ve seen cases where a lack of firmware has caused something similar, or some unsupported power feature got in the way (and a HUB might support a feature the camera does not), but far more often it was just signal quality.

Someone else may know the specific error code meaning.

Hi,
Please check if compliance test with the hub is passed.
http://developer.nvidia.com/embedded/dlc/tx2-series-interface-tuning-compliance-testing-guide

Thanks for the responses. We don’t have the schedule or the resources to run the acceptance test at this point, unfortunately. Although this might become a necessity! :-)

It’s interesting that the XIMEA camera is recognised when we attach it to our carrier board via a second unpowered hub. This leads us to believe that it’s more likely to be a configuration issue than a speed or termination problem. But we’re open to suggestions! Could it be power related?
Thanks
Bob

Signal quality is a result of the entire chain of source/line/sink, so adding a HUB can improve signal quality just by being very slightly different than the actual end device. If there is a power issue, then adding a powered HUB would resolve the issue…but you said you added an unpowered HUB and it resolved. Thus it seems to be more likely a signal quality issue.