• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 34 subscribers
  • Views 785 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/TUSB4041I: XIMEA camera not recognised

Bob Stiles
Prodigy 50 points
Part Number: TUSB4041I
Other Parts Discussed in Thread: TUSB8041

Tool/software: Linux

Hi 

We have a TUSB4041 mounted on our Jetson TX2 carrier board to split out the Jetson's USB2.0 upstream port to four USB2.0 downstream. 

The Jetson is running Ubuntu 16.04

Using lsusb -vvv Ubuntu reports:

Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub 

and

SuperSpeed USB Device Capability:                                                                                       

 bLength                10                                                                                             

 bDescriptorType        16                                                                                             

 bDevCapabilityType      3                                                                                             

 bmAttributes         0x00                                                                                             

 wSpeedsSupported   0x000e                                                                                               

   Device can operate at Full Speed (12Mbps)                                                                             

   Device can operate at High Speed (480Mbps)                                                                           

   Device can operate at SuperSpeed (5Gbps)                                                                           

The TUSB4041 is clearly not a Super speed device, however per the datasheet its VID:PID are 0451:8142, which is identical to the VID:PID in the TUSB8041's datasheet.

Is this intentional?  Is the TUSB8041 Super speed driver for Ubuntu untended to be backward compatible with the TUSB4041?

We have tested various devices with the hub.  Mass storage devices successfully connect at USB2.0, however our XIMEA USB2.0 is not recognised at all.

Strangely, if we connect an additional standalone hub to one of the TUSB4041's downstream ports, the camera connects.

Could this be related to Ubuntu loading the 'wrong' driver?

  • 0
    TI__Guru** 104440 points
    TUSB4041 was the USB2 version of TUSB8041 but disabled USB3, maybe VID/PID didn't change.
    does camera connect to downstream of TUSB4041 and didn't work? it's nothing to with driver for hub
  • 0 in reply to Brian Zhou
    Prodigy 50 points

    Brian Zhou said:
    TUSB4041 was the USB2 version of TUSB8041 but disabled USB3, maybe VID/PID didn't change.
    does camera connect to downstream of TUSB4041 and didn't work? it's nothing to with driver for hub

    Thanks for your response. :-)

    Yes it appears that the TUSB4041 is a USB2 version of TUS8041.

    Surprisingly, in the datasheets they have the same default VID:PID in EPROM of 0451:8142.  Isn't this likely to cause problems for the TUSB4041 since it's not a USB3 device?

    Yes, the camera does not connect downstream of  the TUSB4041. But it does if we connect an unpowered hub to downstream of the TUSB4041, then connect the camera to the unpowered hub.

    What is the 'correc't VID:PID for the TUSB4041? In your TUSB4041 eval board it seems to be set to 0451:80FF. 

    In other posts I have seen people asking for the EPROM programming utility, and it seems they can then change the VID and PID to their own company's parameters.  Our TUSB4041 is integrated into an NVIDIA Jetson carrier board running Ubuntu, so programming it via Windows is not an option. Is there a version of this utility for Ubuntu.  If not, is the source code available?

    Thanks and regards

    Bob Stiles

  • 0 in reply to Bob Stiles
    Prodigy 50 points

    HI Brian

    We are still having problems with the VID and PID of the TUSB4041.

    Do you have an uodate for us?

    Thanks

    Bob

  • 0 in reply to Bob Stiles
    TI__Guru** 104440 points
    VID:PID should not be the issue. you said unpowered hub , so it's bus powered or totally no power?
  • 0 in reply to Brian Zhou
    Prodigy 50 points
    The working case is when the camera is connected to the TUSB4041 downstream port through a bus powered hub.
    The non working case is when the camera is connected directly to the TUSB downstream port.

    So is it OK that the TUSB4041 (a USB2 device) is trying to use a USB3 driver?
  • 0 in reply to Bob Stiles
    TI__Guru** 104440 points
    USB3 is disabled in TUSB4041, so it's not going to use USB3 driver, what bus powered hub connected to TUSB4041 downstream, still TUSB4041?
  • 0 in reply to Brian Zhou
    Prodigy 50 points

    Brian Zhou said:
    USB3 is disabled in TUSB4041, so it's not going to use USB3 driver, what bus powered hub connected to TUSB4041 downstream, still TUSB4041?

    Yes - but it _is_ using the USB3 driver because it has the same default VID:PID as the TUSB8041!  Please read my original posting.

    No, the bus powered hub that works is a BELKIN 4-port mobile travel hub featuring a Genesys Logic GS850G

  • 0 in reply to Bob Stiles
    TI__Guru 60865 points

    Hi Bob,

    The TUSB8041 (like all USB 3.0 hubs)  reports two separate VID/PID.  The USB 3.0 hub instance reports 0451/8140 and the USB 2.0 hub reports 0451/8142.  The TUSB4041 uses the same VID/PID as the USB 2.0 hub instance of the TUSB8041.  The information you are seeing reported with the lsusb command is just a device capability descriptor, it doesn't indicate the actual speed of the device connection. TI USB hubs use generic drivers, not custom ones, and if you are able to see the hub report descriptors and downstream mass storage devices, then a USB 2.0 hub driver was correctly loaded for the TUSB4041.  

    The camera issue does not appear to be a hub driver issue.  Can you confirm that the hub is providing enough power to the camera?  Are you able to use the other ports on the hub while the camera is connected?  Can you check the DP/DM line states?

    Regards,

    JMMN

  • 0 in reply to JMMN
    TI__Guru 60865 points
    Hi,

    Is there any update on this issue?

    Regards,
    JMMN