• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 100 subscribers
  • Views 662 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

[DM8168] USB overcurrent issue in DVRRDK-03.00.00.00

Jason9296
Intellectual 330 points

Hi, all,

 

        We are using DVRRDK-03.00.00.00 on  P.G. 2.0 of DM8168,  when usb overcurrent occurs, USB_DRVVBUS(Pin P35, R35) output Low Signal to disable external usb power, and then resume to normal mode ( remove overcurrnt device), USB_DRVVBUS still output Low Signal,and therefore external USB Power always disabled. Once the usb port encounters overcurrent then resume to normal mode, the usb port can't be used again unless system reboot., 

Unfortunately, everything about overcurrent on USB ports is all right in DVRRDK-02.80.00.10 on P.G. 2.0 of DM8168.

  Any suggestion will be appreciated, thanks.

  • 0
    TI__Expert 7765 points

    Jason,

    RDK 03.00.01.03 patch release was made with USB fixes in the lsp. Please see if that resolves your issue.

  • 0 in reply to Yogesh Marathe
    Intellectual 330 points

    Yogesh, 

    After testing, this USB bug doesn't be fixed in  RDK 03.00.01.03 patch.


    Please help to check this issue, thanks.

  • 0 in reply to Jason9296
    TI__Expert 7765 points

    Thanks for confirmation. I will forward this to our USB team.

  • 0 in reply to Yogesh Marathe
    TI__Expert 7885 points

    Hi

    When the overcurrent occurs, the controller removes the session (bit0 of DEVCTL) and drives the usb_drvbbus to low to switch of vbus supply. When session is removed the controller is not in host mode. You can set the session bit manually by echo "F" > /proc/driver/musb_hdrc.0 or 1 to make the controller enter into host mode.

    Regards

    Ravi B

  • 0 in reply to Ravi B
    TI__Expert 7885 points

    Hi

    As per the spec, the device or port which causing the over-current condition the controller port is disabled. You can revert the patch at

    http://arago-project.org/git/projects/?p=linux-omap3.git;a=commit;h=a7301f628d15508e7639925418058391abf2a45f

    to enable the workaround which enables the port by setting the session bit again when overcurrent condition occur. But it will be annoying as the console will print continuous over-current messages till the over-current device is removed.

    Regards

    Ravi B

  • 0 in reply to Ravi B
    Intellectual 330 points

    Hi, Ravi,

    Thanks for your kindly help, it works correctly now.

    One more question : Is this the spec "disable the host-controller on over-current condition and no more use usb port until system reboot " ?

    Thanks

  • 0 in reply to Jason9296
    TI__Expert 7885 points

    Hi

    If the device is connected through the HUB, then as per spec the hub driver disables the respective port through hub control transfer request. If the device connected directly to root port of the controller (not through HUB), then host controller will be disabled.

    Regards

    Ravi B

  • 0 in reply to Ravi B
    Intellectual 330 points

    Hi, Ravi,

    Thanks for your kindly reply.

    One more question about that patch, if the device connected directly to root port of the controller( not through HUB), the host controller will be disabled and in this case, 

    remove that device, the root port can't be used again, does this  fit  in with plug and play standard of USB ??

    And we will revert that patch that don't disable host on over-current condition.

    Beside the  condition  that  console will print continuous over-current messages till the over-current device is removed,

    is there any other thing we should take care when we use usb function???