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.

AM3352 does not detect the usb devices

Other Parts Discussed in Thread: AM3352, AM3359

My customer(borad) can not connect usb host port to USB device (with HUB[Cypress]), and will display follow message in console

 

ti81xx_interrupt 955: CAUTION: musb1: Babble Interrupt Occured

ti81xx_interrupt 956: Please issue long reset to make usb functional !!

usb 1-1: reset high-speed USB device number 2 using musb-hdrc

usb 1-1: device descriptor read/64, error -110

usb 1-1: device descriptor read/64, error -110

usb 1-1: reset high-speed USB device number 2 using musb-hdrc

usb 1-1: device descriptor read/64, error -110

usb 1-1: device descriptor read/64, error -110

usb 1-1: reset high-speed USB device number 2 using musb-hdrc

usb 1-1: device not accepting address 2, error -110

usb 1-1: reset high-speed USB device number 2 using musb-hdrc

usb 1-1: device not accepting address 2, error -110

usb 1-1: USB disconnect, device number 2

usb 1-1: new high-speed USB device number 3 using musb-hdrc

usb 1-1: device descriptor read/64, error -110

 

However the custom board detected USB device when AM3352 start to connect USB device to the hub.

Could you tell me what is the wrong ? Does the same problem occur ?

Best regards

Chi

  • Hi Chi,
     
    Could you give more details:
    - USB part of board schematics
    - Software that you use
    - Does the board connect with USB devices without the hub
  • Hi Chi,
     
    I received the schematics from your FAE Akira Kawakami. Here is a copy of my response to him:
     
    It's quite clear what is happening here. They have left USB1_VBUS (AM3352 pin T18) unconnected. Lucky that they have provided a testpoint on it (TP32). They should try one of 3 possibilities:

    1. Supply 5V to USB1_VBUS from board power supply.
    2. Follow the Starter Kit example (schematics can be downloaded from here: http://processors.wiki.ti.com/index.php/AM335x_StarterKit_Board_Design_Files). They should check how USB0_VBUS is driven by the USB hub on the Starter Kit (schematics pages 2 and 16) and design a similar circuit.
    3. They could use 4 Schottky diodes to inject VBUS voltage from the 4 USB connectors back to USB1_VBUS.

    The AM335X USB peripheral requires external VBUS voltage to be present at USBX_VBUS pin for proper operation.
  • Hi, Biser

    Thank you for your reply. and Kawakami-san

    They confirmed three proposals that I got from you.

    But, situation has not changed, USB device can not connect.

     

    AM335xEVM + Hub EVM(Cypress) can be connected to USB device with same software that is used customer board.

    AM335xEVM use AM3359 device, The customer board use AM3352 device.

    So, Is there a problem that depends on the difference of the device ?

    Are there any other issues to be considered ?

     

    Best regards

    Chi

  • Hi Chi,
     
    There is no difference in the USB peripheral of the processors. However new information has come from the factory team on your issue. Kawakami-san should have it by now. Please contact him.
  • Hi Biser,

    Thank you for helping.

    I received the information from your factory team.

    And, I told that information to customers.

    Currently, they are checking whether there is a problem with the configuration of the Hub and their software.

    Best regards,

    Chi

  • Hi,

    My customer has been progress on their situation.

    Customers were using the WindRiver BSP so far.

    This software could connect USB device at customer board.

     

    TI-SDK(LINUXEZSDK-AM335X : v05.06.00) can connect USB device at customer board that was found now.

    In addition, When Kernel configuration was set as follow, USB device can be connected at customer board.

     - Linux:Kernel Configuration at WindRiver BSP

           [-] USB runtime power management (autosuspend) and wakup

           (Disable)

    Also, when "USB runtime power management (autosuspend) and wakup" is Enable(built-in),

    Suspend bit of USB Port Status is 1(Suspended or resuming.) and cannot connect USB device.

     

    However, TI-SDK does not depend on the above Kernel setting.

     

    So, I have a question.

    Although TI-SDK is always Suspend bit = 0(Not suspended), is this expected behavior ?

     

    Best Regards

    Chi

  • Hi Chi,
     
    Here is the answer from factory team:
     
    On TI-SDK kernel, the Suspend bit in Port Status is 0 (not suspended) if no device is plugged, and 1 (suspended) if a device is plugged and in idle. This is right behavior. By USB2.0 Specs, the port should be in Disconnected state if nothing is plugged.
     
    The “USB runtime power management (autosuspend) and wakup” option mentioned in the post is to control the ‘selective suspend’ on the connected USB device, it should not affect the state of the USB port which has nothing connected.