• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 97 subscribers
  • Views 1233 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.

Linux/TDA2EX17EVM: USB DTS in TDA2EX17EVM

Chih-Kuo Hsu
Expert 1885 points

Part Number: TDA2EX17EVM

Tool/software: Linux

Dear Sirs:

  We are trying to use the USB HOST mode in TDA2EX17EVM, and we modify the USB1 and USB2 dr_mode from "otg" to "host" as requests in the below link:

  I see the DT in TDA2EX17 has the following:

&extcon_usb1 {
    vbus-gpio = <&pcf_lcd 14 GPIO_ACTIVE_HIGH>;
};

&extcon_usb2 {
    vbus-gpio = <&pcf_lcd 15 GPIO_ACTIVE_HIGH>;
};

In its SCHEMATIC file:

However, the PCF_LCD Pin 14 is EXP_ETH1_RSTn, Pin 15 USB1_VBUS_OCN, Pin 16 USB2_VBUS_OCN

Here comes my question: Why the extcon_usb1vbus gpio is 14 and extcon_usb2 vbus gpio is 15?

We always see lots of the following errors :

[  112.049373] usb 1-1: Device not responding to setup address.
[  112.262805] usb 1-1: Device not responding to setup address.
[  112.472743] usb 1-1: device not accepting address 6, error -71
[  113.742733] usb 1-1: new full-speed USB device number 8 using xhci-hcd
[  113.749363] usb 1-1: Device not responding to setup address.
[  113.962800] usb 1-1: Device not responding to setup address.
[  114.172743] usb 1-1: device not accepting address 8, error -71
[  114.692733] usb 1-1: new full-speed USB device number 10 using xhci-hcd
[  114.699453] usb 1-1: Device not responding to setup address.
[  114.912800] usb 1-1: Device not responding to setup address.
[  115.122744] usb 1-1: device not accepting address 10, error -71

We read the the forum and most threads describe the dr_mode is the only place to modify but did not see any success in our test. We use a USB stick and will later to use a self-power USB device. Any comments are welcome.

Regards,

/ckhsu

  • 0
    Expert 1885 points
    Dear Sir:
    Also this kind of error message shows in console:
    [ 68.142768] usb 1-1: device descriptor read/64, error -71
    [ 68.372777] usb 1-1: device descriptor read/64, error -71
    [ 69.552730] usb 1-1: new full-speed USB device number 4 using xhci-hcd
    [ 69.672778] usb 1-1: device descriptor read/64, error -71
    [ 69.902760] usb 1-1: device descriptor read/64, error -71

    Regards,
    /ckhsu
  • 0 in reply to Chih-Kuo Hsu
    Expert 1885 points
    No matter set /sys/module/usbcore/parameters/autosuspend to -1 to disable the suspend or set /sys/module/usbcore/parameters/old_scheme_first to Y can not fix this problem.

    The configuration in kernel is

    CONFIG_USB_TI_CPPI41_DMA=y
    CONFIG_USB_DWC3=m
    CONFIG_USB_DWC3_DUAL_ROLE=y
    CONFIG_USB_DWC3_OMAP=m

    CONFIG_EXTCON=m
    CONFIG_EXTCON_USB_GPIO=m

    Regards,
    /ckhsu
  • 0
    TI__Mastermind 48193 points

    Hello,

    Regarding the question: Why the extcon_usb1vbus gpio is 14 and extcon_usb2 vbus gpio is 15?

    The value 14 stands for P16 and 15 stands for P17 which is used for detecting the VBUS.

    Note that PCF value P0 to P7 represented from as value 0 to 7, but when representing the PCF value for the higher P10 to P17, we continue the previous indexing and use value 8 to 15.

    Hope this clarifies.

    regards,

    Praveen

  • 0 in reply to Chih-Kuo Hsu
    TI__Mastermind 48193 points
    From the error shown above , it seems that the device enumeration is failing, Not sure what is the exact root-cause. Is this happening with different USB flash pen-drives (USB stick) or on a specific one?

    Have you verified if the voltage is proper on the VBUS?

    regards,
    Praveen
  • 0 in reply to Praveen Rao
    Expert 1885 points
    Hi Praveen:
    Thank you for the explanation of PCF.
    For the USB, we test on 2 self-powered USB devices including one hard disk and one card reader, both of them are okay in linux PC.
    They can be seen on usb2 interface, but fail on usb1 in TDA2EX17EVM and we also try on our TDA2XXEVM and the situation is exact the same.
    Please be note that both of the dr_mode on usb1 and usb2 are all set to host.

    I will ask our H/W to verify the voltage on VBUS on USB1.

    Meanwhile, do you have any other ideas?

    Regards,
    /ckhsu
  • 0 in reply to Chih-Kuo Hsu
    Expert 1885 points
    root@dra7xx-evm:~# lsusb -t
    /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    |__ Port 1: Dev 6, If 0, Class=Mass Storage, Driver=usb-storage, 480M
    /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M

    The above log shows HDD is connected on usb2.

    [ 1296.488062] usb-storage 3-1:1.0: USB Mass Storage device detected
    [ 1296.506398] scsi host4: usb-storage 3-1:1.0
    [ 1296.512035] cpsw 48484000.ethernet: gpio request failed, ret -517
    [ 1296.531936] cpsw 48484000.ethernet: gpio request failed, ret -517
    [ 1296.683251] usb 3-1: USB disconnect, device number 7
    [ 1296.962754] usb 3-1: new high-speed USB device number 8 using xhci-hcd
    [ 1297.107467] usb-storage 3-1:1.0: USB Mass Storage device detected
    [ 1297.125310] scsi host5: usb-storage 3-1:1.0
    [ 1297.130896] cpsw 48484000.ethernet: gpio request failed, ret -517
    [ 1297.150600] cpsw 48484000.ethernet: gpio request failed, ret -517
    [ 1298.133688] scsi 5:0:0:0: Direct-Access SP CF USB 3.0 0578 PQ: 0 ANSI: 6
    [ 1298.147787] sd 5:0:0:0: [sda] Attached SCSI removable disk
    [ 1298.155461] scsi 5:0:0:1: Direct-Access SP xD USB 3.0 0578 PQ: 0 ANSI: 6
    [ 1298.165525] cpsw 48484000.ethernet: gpio request failed, ret -517
    [ 1298.189626] cpsw 48484000.ethernet: gpio request failed, ret -517
    [ 1298.198881] sd 5:0:0:1: [sdb] Attached SCSI removable disk
    [ 1298.219051] scsi 5:0:0:2: Direct-Access SP SDXC USB 3.0 0578 PQ: 0 ANSI: 6
    [ 1298.259955] cpsw 48484000.ethernet: gpio request failed, ret -517
    [ 1298.374224] scsi 5:0:0:3: Direct-Access SP MSXC USB 3.0 0578 PQ: 0 ANSI: 6
    [ 1298.394534] sd 5:0:0:2: [sdc] 7954432 512-byte logical blocks: (4.07 GB/3.79 GiB)
    [ 1298.426508] sd 5:0:0:3: [sdd] Attached SCSI removable disk
    [ 1298.453141] scsi 5:0:0:4: Direct-Access SP TFXC USB 3.0 0578 PQ: 0 ANSI: 6
    [ 1298.477685] sd 5:0:0:2: [sdc] Write Protect is off
    [ 1298.490726] cpsw 48484000.ethernet: gpio request failed, ret -517
    [ 1298.504748] sd 5:0:0:2: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    [ 1298.530448] sd 5:0:0:4: [sde] Attached SCSI removable disk
    [ 1298.550080] cpsw 48484000.ethernet: gpio request failed, ret -517
    [ 1298.588275] sdc: sdc1 sdc2
    [ 1298.615832] sd 5:0:0:2: [sdc] Attached SCSI removable disk
    [ 1299.534259] EXT4-fs (sdc2): recovery complete
    [ 1299.538665] EXT4-fs (sdc2): mounted filesystem with ordered data mode. Opts: (null)

    root@dra7xx-evm:~#
    root@dra7xx-evm:~#
    root@dra7xx-evm:~#
    root@dra7xx-evm:~# lsusb -t
    /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    |__ Port 1: Dev 8, If 0, Class=Mass Storage, Driver=usb-storage, 480M
    /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    root@dra7xx-evm:~#

    The above log show the self-powered card reader connected on usb2.

    But on usb1, which is also configured as dr_mode="host", can see nothing.

    Regards.
    /ckhsu
  • 0 in reply to Praveen Rao
    Expert 1885 points
    Hi Praveen:
    Our H/W measured the voltage of USB1, and he told me that the voltage is only 0.5V. It is quite weired. Do we need to modify any switch on the EVM board to test on USB?

    If any comments, please let me know.

    Regards,
    /ckhsu
  • 0 in reply to Chih-Kuo Hsu
    TI__Mastermind 48193 points

    Hi,

    There is no switch on the TI EVM board for USB VBUS. But we do have an on-board SW2 switch for forcing the ID pin. Since in your case, the plan to use it as HOST only, the ID pin is a don't care.

    Other way to force the VBUS to be always ON is to use the USB1_DRVVBUS pin. In this case, you may have to force this pinmux to be 1. We can either do it as the u-boot level or the kernel level.

    Thanks

    Praveen