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.

TUSB4041I: Linux connect to 4041 successful,but device do not

Part Number: TUSB4041I
Other Parts Discussed in Thread: TUSB4041PAPEVM

Hi,

    We using tusb4041 with arm Linux. Sch and BOM reference with tusb4041papevm.

    We got kernel log:

    [ 14.212241] usb 1-1: new high-speed USB device number 5 using ambarella-ehci
    [ 14.348079] usb 1-1: New USB device found, idVendor=0451, idProduct=8142, bcdDevice= 1.00
    [ 14.356247] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=1
    [ 14.363371] usb 1-1: SerialNumber: 29050841A7A1
    [ 14.368453] hub 1-1:1.0: USB hub found
    [ 14.372326] hub 1-1:1.0: 4 ports detected

    It looks like linux has successfully connect to 4041 .But if we add a usb device such as flash disk,there is nothing connectted.

   We capture the waves of upstream D+ and D-:

    

  

  • Hello Xiaoyan,

    It looks like there is a lot of USB resets occurring.  Are you seeing anything in the log?  Can you use USBMON to get more verbose USB?

    Can you check the downstream DP/DM lines?

    Regards,

    JMMN

  • Hi,

    Thanks for reply.There's nothing print on log.I will try to install usbmon.

    Downstream DP is hang on 3.3v and DM is 0.

  • Ok, if downstream DP is 3.3V and DM is 0V, the devices are enabling their pullups but the hub / host is not responding.  Debug statements would be helpful.  Also check that the OVERCURz input is not getting set on any port.

    Regards,

    JMMN

  • Hi,I've got usb log with tcpdump usbmon.1_0 is flash disk insrted.1_1 is hub only.

    I don't know why I can't upload pcap file .So I change it to .txt . You should change it back to .pcap .

    �ò��8�g@@9
    ����S�<8�g�����8�gDD9
    ����C�-8�g8h@@�,����S�-<8h����8.h@@9
    ����S�<8.h�����88hDD9
    ����C�-88h8Ah@@9
    ����S8Ah����#8Jh@@9
    ����C->8Jh8BiAA�,����C�-8Bi8Ji@@�,����S�-<8Ji����8��AA�,����C�-8��8��@@�,����S�-<8������8s	@@9
    ����S�<8s	�����8�	DD9
    ����C�-8�	8_4AA�,����C�-8_48e4@@�,����S�-<8e4����8I8@@9
    ����S8I8����#8T8@@9
    ����C->8T88_8@@9
    ����S�	<8_8�����8�8BB9
    ����C�	-8�88�8@@9
    ����S	8�8����819@@9
    ����C	->8198G9@@9
    ����S�<8G9�����8S9DD9
    ����C�-8S98g9@@9
    ����S�	<8g9�����8�9DD9
    ����C�	-8�98�9@@9
    ����S�	<8�9�����8,:DD9
    ����C�	-8,:8::@@9
    ����S�	<8::�����8�:DD9
    ����C�	-8�:8�:@@9
    ����S�	<8�:�����8&;DD9
    ����C�	-8&;83;@@<����S�	-<83;����8f;@@9
    ����S�	<8f;����(�(8�;RR9
    ����C�	-8�;	@QB�8"D@@<����C�	-8"D����84D@@9
    ����S	84D����8kD@@9
    ����C	->8kD8zD@@9
    ����S8zD����#8�D@@9
    ����C->8�D8�r@@�,����C�-8�r����8<�@@:
    ����S�<8<������8G�DD:
    ����C�-8G�8O�@@�,����S�-<8O�����8r�@@:
    ����S�<8r�����(�(8|�RR:
    ����C�-8|�	@k8��@@�,����C�-8������

    usbmon1_1.txt

  • Hi Xiaoyan,

    Reviewing the log, the host keeps cycling through suspending and resuming the hub, but I don't see any reason for that behavior.  It is normal for the host to suspend a hub with no downstream devices and then wake when a device is inserted, but in this case the host just reads the port status and suspends the hub.  Can you try booting the system with a device connected to a hub downstream port?

    Regards,

    JMMN

  • Hi,Blow is system booting with device inserted :

    usbmon1_2.txt

  • Very strange, I'm seeing the exact same behavior in this trace.  Have you checked the overcurrent inputs to the hub to see if they are accidentally being flagged?

    Regards,

    JMMN