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.

AM6526: Difficulty with USB3.0 on different boards

Part Number: AM6526

I have a customer using the AM6526 for a design.
They are having trouble with USB3.0.
They are using multiple boards for testing, but all boards are the same design.

① Some boards work fine - any USB device is properly recognized.
➁ Some boards detect USB3.0 devices as USB2.0
③ Some boards, when a specific device is connected, do not detect the device as either USB2.0 or USB3.0.

The above has been confirmed on multiple boards for each case.

Is there any material relating to such USB3.0 issues available, or any thoughts you have on what could be causing this?

  • Since we are seen inconsistent behavior on boards of the same design, it mostly related to the USB board schematics or USB PHY related. It is rarely due to software. The device enumeration is attributed to the USB PHY unable to negotiate the speed. 

    The first thing will be to check if the board passes the USB characterization. The second is to inspect the USB schematics.

    Please refer to this link (note it is not specific to AM65x, but the ideas still are the same)

    https://training.ti.com/sites/default/files/docs/USB-M1-HW-Design.pdf

    Also, suggest the customer share the kernel log of all the different passing and failing cases to check if it is really a software issue.

    Thanks.


  • The customer has the AM65x GP EVM, but are looking for the "x1 Lane PCIe/USB3 Personality Card" so they can check their software on the EVM; to see if issue is hardware/software.
    - If there is a spare sitting around somewhere, could you let me know off-line? (Also checking our office here) 
    - Was this supposed to be packed with the IDK...?


    Running compliance testing with AM6526 set as USB3.0 Tx Host seems to show no issues with the transceiver. (*Tested on ➁ boards from the first post↑)
    But for some reason, the customer is having trouble using the receiver line to change the output waveform.
    It looks like the issue could be with the receiver line - any thoughts on debugging here?
    Compliance testing couldn't be performed since they can't use the receiver.

    Thanks

  • I have not received a reply to the above - so let me ask this differently. 

    We can provide a register dump to help confirm if the proper register settings for compliance testing are being followed?
    This is a pretty urgent request, so I would really appreciate your thoughts on how to go about validating the setup first.

    Thanks

  • Looping the H/w apps team to help with your query on the board schematics & USB characterization.

    From the software point of view, For the failure case,  Suggest we request the customer to provide the Linux kernel log to see if any error is seen during enumeration.

    Thanks.

  • They are not using Linux. They are actually not using any OS - instead they are running:

    Processor SDK RTOS 06_03_00_106 
    Diag Application: board/diag/usb_host
    xhci driver: drv/usb

    They are basically using the settings as-is from the AM65xx EVM here. Is there somewhere else to look, or some register settings we can check?

  • Darren,  I believe this debug was taken to direct support with the software team.  Closing the thread.

    Thanks,
    Kyle