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.

AM6548: USB0 Device enumeration issue

Part Number: AM6548


Hi Team,

We have designed a board with AM6548 Processor. We are in board bring up stage.

Currently, we are facing an issue with AM6548 USB0 Interface.

USB0 is working fine in Host Mode. However in device mode we are facing an issue with device enumeration.

We have followed EVM as reference for schematic design.

Kindly share your thoughts on this.

Thank you.

Regards,

Sushruta

  • Please post what software you are using, and which version.

  • We are using RTOS and below is the file that we are referring to.

    ti-processor-sdk-rtos-am65xx-evm-05.03.00.07-Linux-x86-Install.bin

    Regards,

    Sushruta

  • Hi,

    I thought you must be quite familiar with the IDK or GP EVM schematics. And you used the USB_DevMsc_TestApp or the baremetal one? Build by CCS project or gmake? Is the USB instance set to 0? Is USB 3.0 or 2.0 for this test? Have you attached a USB trace analyzer to see what LTSSM state it stuck?

    Regards, Eric  

  • Hi,

    On the EVM we tested USB port 0 in host mode and USB port 1 in device mode. It seems you need to enable USB Serdes when you using USB port 0 as the device mode.

    So, 

    1. in ti\drv\usb\soc\am65xx\usb_wrapper.c, function void usbClockCfg(uint32_t portNumber) 

    if ((portNumber == 0) && /* only port #0 supports SS */
    //(usbConfig->usb30Enabled == TRUE) /* user asks for USB3.0 */) ======> comment out this line so always enable USB port 0 serdes clock
    {
    if (usbClockSSCfg() != 0)
    {
    debug_printf("Error when enabling Super Speed\n");
    }
    }

    2. ti\drv\usb\example\usb_dev\msc\dev_msc.c, 

    #define USB_DEV_INSTANCE                     1 ========> change this to 0

    Then, rebuild USB library and application, try and let us know if it works.

    Regards, Eric

  • Thank you for your support.

    This resolved our issue.

    Regards,

    Sushruta