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.

USB3.0 host support on EVM ES2.0

Hi,

I'm trying to build the latest kernel from ti-linux-3-8-y-kernel git and I'd like to get at least MSC support on USB3.0 host.

Is there any other TI git I can use to get USB3.0 in any working shape?

Is it possible to state what .config flags I need in order to get USB3.0 host compiled in properly?

I'm after legitimate combination of XHCI, DWC3 and any relevant flags. Do I need any PALMAS_USB flags for this HW?

  • Hi Alexey,

    The support for USB3.0 is answered in this thread http://e2e.ti.com/support/omap/f/885/t/275115.aspx

  • Well, it's not the answer I'm looking for.

    On the page http://www.ti.com/tool/omap5432-evm TI claims that OMAP5432 has HS USB 3.0 OTG Port among its features. And it was the reason this development board was purchased.

    - Are HW issues with USB 3.0 IP block the reason of lack of software?

    Even if USB3.0 was not tested yet, it would still be nice to know:

    - when will support for USB 3.0 host be added to SDK?

    - Is there any additional git branch to get early (unstable) versions to try?

    Regards,

    Alexey

  • Hi Alexey,

    the USB 3.0 controller is functional in gadget and host mode here on the uEVM using Linux based on the ti-linux-3-8-y-kernel tree (i.e., the GLSDK 6.01 kernel). With certain combinations of adapters (USB 3.0 micro to USB 3.0 A female) and devices, SuperSpeed does not work. We haven't noticed any issues with HighSpeed, though.

    Excerpts from our config:

    CONFIG_USB_XHCI_HCD=y
    CONFIG_USB_XHCI_PLATFORM=y
    CONFIG_USB_DWC3=y
    CONFIG_USB_DWC3_DUAL_ROLE=y
    CONFIG_PALMAS_USB=y
    CONFIG_OMAP_USB2=y
    CONFIG_OMAP_USB3=y
    CONFIG_OMAP_CONTROL_USB=y
    CONFIG_USB_GADGET=y

    We had to make the following changes to get host mode working:

    • switch controller to host mode by setting mode = <1> for /ocp/omap_dwc3@4a020000/dwc3@4a030000 in the device tree
    • disable XHCI reset: remove the CMD_RESET part from xhci_reset() in drivers/usb/host/xhci.c, see http://comments.gmane.org/gmane.linux.usb.general/86065
    • make sure the ID pin is grounded (J10 can be used for that, IIRC) or alternatively, force smps10_out1 on in the kernel

    Regards,
    Jürg