Go to previous topic
Go to next topic
Last Post 22 Oct 2014 01:08 PM by  bradb
USB Gadget Drivers (Ethernet Gadget (with CDC Ethernet support)) with USB OTG as Host may fail
 0 Replies
Author Messages
bradb
Basic Member
Basic Member
Posts:203


--
22 Oct 2014 01:08 PM
    Subject    
    DM37LINUX-1038: USB Gadget Drivers (Ethernet Gadget (with CDC Ethernet support)) with USB OTG as Host may fail
    Product    
    DM37x Torpedo and DM37x Torpedo + Wireless
    Software OS    
    DM37x Linux 2.4-3 BSP 
    Description    
    Customer's looking to use Ethernet Gadget (with CDC Ethernet support) with USB OTG as Host may see a similar error following a ping when using Linux 2.4-3 release.

    [  112.575347] musb_ep_program 834: broken !rx_reinit, ep2 csr a200
    [  112.586914] musb_ep_program 834: broken !rx_reinit, ep2 csr a000
    [  113.567474] musb_ep_program 834: broken !rx_reinit, ep2 csr a200
    [  114.568634] musb_ep_program 834: broken !rx_reinit, ep2 csr a000
    [  115.569824] musb_ep_program 834: broken !rx_reinit, ep2 csr a200
    [  116.570983] musb_ep_program 834: broken !rx_reinit, ep2 csr a000
    [  117.572326] musb_ep_program 834: broken !rx_reinit, ep2 csr a200
    [  117.599212] musb_ep_program 834: broken !rx_reinit, ep2 csr a000
    [  118.573486] musb_ep_program 834: broken !rx_reinit, ep2 csr a200
    [  119.574676] musb_ep_program 834: broken !rx_reinit, ep2 csr a000

    This error was seen when using the default BSP and only selecting CONFIG_USB_USBNET, CONFIG_USB_NET_CDCETHER, and CONFIG_USB_NET_RNDIS_HOST=y in the USB Network Adapters section of the kernel config file.   Simply connect two DM37x systems together using a USB OTG A to mini-B cable and a USB OTG A to mini-A cable.  Insert the USB mini B plug into the DM37x client system and the USB A plug into the host adapter.  The host adapter's mini A plug is then inserted into the DM37x host system.  

    Selection of the Ethernet Gadget (with CDC Ethernet support)
     Prompt: USB Gadget Drivers                                                                                                                      
       -> Device Drivers   -> USB support (USB_SUPPORT [=y])   -> USB Gadget Support (USB_GADGET [=y])   

    Word-around

    This issue has been reported as being seen when using kernels through 3.3.0.    The suggested workaround is to disable the MUSB DMA.

    Old configuration:
    # CONFIG_MUSB_PIO_ONLY is not set
    # CONFIG_USB_UX500_DMA is not set
    CONFIG_USB_INVENTRA_DMA=y
    CONFIG_MUSB_USE_SYSTEM_DMA_WORKAROUND=y
    # CONFIG_USB_TI_CPPI_DMA is not set

    New configuration:
    CONFIG_MUSB_PIO_ONLY=y
    # CONFIG_USB_INVENTRA_DMA is not set
    # CONFIG_MUSB_USE_SYSTEM_DMA_WORKAROUND is not set



    ---