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

AM3517 USB0(OTG) port Chirp handshake issue

Daisuke Maeda
Guru 20205 points
Other Parts Discussed in Thread: AM3517, AM3505

USB0(OTG) port of AM3517 cannot connect specific USB memory.
When the USB memory cannot be connected, it seems to start a handshake again that the USB memory outputs first Chirp K two times during Chirp handshake.

In most cases, it may be said that the USB memory has some problem.
However I have concern for USB0(OTG) port of AM3517.

It is too early that the USB0(OTG) port starts Chirp KJKJKJ after first Chirp K.
Time between Chirp K and Chirp KJKJKJ is 2.22usec.

In the case of AM3517 HSUSB port , it is 92.99usec.
In the case of PC USB port, it is 3.2usec.

Is it bad to be 2.22usec?
If it is bad, is there the method to extend it?

Best regards,

Daisuke

 

  • 0
    Guru 20205 points

    Linux dmesg logs are below:

    [ 73.532958] usb 2-1: new high speed USB device using musb-hdrc and address 2
    [ 76.618774] hub 2-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
    [ 79.705108] hub 2-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
    [ 82.790740] hub 2-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
    [ 85.876617] hub 2-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
    [ 85.884155] hub 2-0:1.0: unable to enumerate USB device on port 1

    HSUSB port of AM3517 can connect the same USB memory without the problem.

    Linux dmesg logs in case of HSUSB port are below:

    [ 75.025268] usb 1-1: new high speed USB device using ehci-omap and address 2
    [ 75.270080] usb 1-1: New USB device found, idVendor=067b, idProduct=2517
    [ 75.277252] usb 1-1: New USB device strings: Mfr=1, Product=4, SerialNumber=6
    [ 75.284881] usb 1-1: Product: ClipDrive
    [ 75.288940] usb 1-1: Manufacturer: BUFFALO
    [ 75.293304] usb 1-1: SerialNumber: AE200506240000021
    [ 75.384735] scsi0 : usb-storage 1-1:1.0
    [ 76.478851] scsi 0:0:0:0: Direct-Access BUFFALO ClipDrive 1.00 PQ: 0 ANSI: 0 CCS
    [ 76.615539] sd 0:0:0:0: [sda] 507904 512-byte logical blocks: (260 MB/248 MiB)
    [ 76.681579] sd 0:0:0:0: [sda] Write Protect is off
    [ 76.686676] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
    [ 76.686706] sd 0:0:0:0: [sda] Assuming drive cache: write through
    [ 76.787292] sd 0:0:0:0: [sda] Assuming drive cache: write through
    [ 76.836273] sda: sda1
    [ 76.924560] sd 0:0:0:0: [sda] Assuming drive cache: write through
    [ 76.931152] sd 0:0:0:0: [sda] Attached SCSI removable disk

    This problem occurs in the AM3505 custom board and AM3517EVM.

    Best regards,

    Daisuke

     

  • 0
    TI__Mastermind 27890 points

    Daisuke,

    There is no defined minimum time for a hub port to begin sending Chirp JK after receiving the device Chirp K. Chirp K must be from 1-7ms after Reset begins and Chirp JK must begin no later than 100us after the bus has left the Chirp K state.

  • 0 in reply to -DK-
    Guru 20205 points

    Hi DK,

    Thank you for the reply.

    I could see that the AM35x boards and the USB memory follow the timing specification that you said.
    However, the problem is not yet solved.

    I must prove it for our customer that the USB memory has the problem and the AM35x does not have the problem.

    Have you seen the state such as the first image which I attached?
    If you have seen it, do you know the workaround?

    Best regards,

    Daisuke

     

  • 0 in reply to Daisuke Maeda
    TI__Mastermind 27890 points

    Daisuke,

    I have not seen this issue before.

    Does the issue occur with other memory devices, or just this one? 

    Is the failing MSC a USB Certified device?

  • 0 in reply to -DK-
    Guru 20205 points

    Hi DK,

    Thank you for the reply.

    The issue does not occur with other memory devices and occurs with just this one.

    Please see the above dmesg logs.
    The logs in case of HSUSB port show the information of issue USB device.

    I don't know this device is a USB Certified device.

    By the way, for this issue our local TI employee is working.
    Therefore, they might have contacted you.

    Best regards,

    Daisuke

     

  • 0 in reply to Daisuke Maeda
    TI__Mastermind 27890 points

    Daisuke,

    This is a very old device, and from what I can tell, is not USB certified to be compliant to the specification. Is there more than one failing example of this device, or is there only one example that has been tested?

  • 0 in reply to -DK-
    Guru 20205 points

    Hi DK,

    Thank you for the reply.

    I know only one failing example that has been tested.
    I don't know whether our customer have more than one same device.

    This device, and other vendor devices which do not fail are going to be tested on AM3517EVM by our local TI engineer.
    I wait for the test result.

    Best regards,

    Daisuke