• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 100 subscribers
  • Views 753 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.

OMA-L137 USB Enumaration fails in DEVICE Mode.

GovindaRao Gotta
Prodigy 50 points
Other Parts Discussed in Thread: OMAP-L137, OMAP-L138

Please find the board details and issue in USB(device mode) below. EVM Board: OMAP-L137 EVIM from spectrum digital. REV-E

Requirement: EVM Board needs to be configured as a bulk device (device mode only, no otg support needed).

Steps taken in the firmware:

- Configured the USB0 and powered up the PHY.

- Able to read the PHY and ctrl registers successfully

- Set the SOFTCON bit. - Enabled all DEVICE and EP# related interrupts.

- Observed(using Osc Scope) the DP(D+) and DM(D-) line in idle state i.e DP-HIGH and DM-LOW And then when connect the EVM board to the host

- DP is pulling down to LOW for some and remained in the same state (DP-Low and DM-Low) around ~18 secs moving back to idle state.

- Results in failing enumeration and windows HOST come up with “USB Device not Recognized” notification.

Please help me to move further

  • 0
    TI__Genius 14545 points

    GovindaRao Gotta said:
    Observed(using Osc Scope) the DP(D+) and DM(D-) line in idle state i.e DP-HIGH and DM-LOW And then when connect the EVM board to the host

    I'll assume for now that you desire to run as a Full Speed USB Device due to D+ being pulled up, but please confirm.

     

    GovindaRao Gotta said:
    DP is pulling down to LOW for some and remained in the same state (DP-Low and DM-Low) around ~18 secs moving back to idle state.

    If both D+/D- are both low for an extended period of time, this typically is a bus Reset, however 18 seconds is way to long. You might want to verify that you are getting the interrupts from the Host as expected by setting breakpoints in your firmware and reading the standard requests received by OMAP-L137.

  • 0 in reply to dabuan
    Prodigy 50 points

    Hi ,

    1. Yes, I am trying to configure as a Full Speed device.

    2. When conneting the cable D+/D- both low for some time. let us take this condition as bus RESET, 

    for same condition there is an interrrupt expected at the device-end and the respective handler should be invoked.

    (I am using the OMAP-L138 starterware code for AINTC initilazation and USB enumaration testing purpose)

    And also tried to poll the reset bit in POWER register, no success. Not able to understand waht is missing to get the interrupt generated.

    (...unfortunately my debugger is not working, expected to be made OK in 3 days )

    Thanks &

    Regards.,

    Govinda

  • 0 in reply to GovindaRao Gotta
    TI__Intellectual 880 points

    Hello Govinda,

                               Any update on this. Your Debugger is ready to Debug.

     

    ----- Abhijit

  • 0 in reply to Abhijit Das84416
    Prodigy 50 points

    Hi Abhijit,

    I  got informed by TI-supporting team that, there is an issues in packing unaligned structures used by USB and another suspection is some clock related issues in CCS GEL files.

    (Regarding debugger... as per the latest information from the TI we have to use CCS5.x.x from now on...We are trying to migrate to latest CCS5.x.x, in tis we are facing issues, we are in touch base with support team.)

    Mean time any valueble suggestion would be great help to move further... please post if there are any.

    Thanks &

    Regards

    Govinda.

  • 0 in reply to GovindaRao Gotta
    Intellectual 500 points

    Govinda,

    I hope this is helpful, but the company I work for has gone through all the pain of getting the USB to work on the C674x DSPs and we have a working bulk in and bulk out device.

    It can be accessed using a standard CDC-ACM / virtual serial port / virtual COM port driver to transfer data to and from the DSP. This means that there is no need for custom device drivers on normal operating systems (Windows/Linux/MacOS/e.t.c.). Alternatively, we have also used LibUsb to implement a driver that is more resilient than the standard Windows device driver and has support for passing messages over the USB in a packetised manner.

    If you really need to get the USB working quickly, then we will be able to help you. If you want further information please look at :

    http://focus.ti.com/dsp/docs/thirdparty/catalog/companyfolder.tsp?actionPerformed=companyFolder&companyId=1898

    and our direct web-site link:

    http://www.macltd.com/products_usbdriver.php

    We gave it to one customer and they had the test application working the next day, and very rapidly integrated it into their own product. The documentation is very good, and hopefully any queries you would have will be answered very rapidly. We have a demo version as well. Please email me if you are interested.

    Yours,

    Peter

    -------

    Dr Peter Myerscough-Jackopson  -  Principal Engineer

    Tel: +44 (0)23 8076 7808 Fax: +44 (0)23 8076 0602
    Web: http://www.macltd.com/  Email: peter.myerscough-jackopson@macltd.com
    MULTIPLE ACCESS COMMUNICATIONS LIMITED is a company registered in
    England at Delta House, The University of Southampton Science Park,
    Southampton, SO16 7NS, United Kingdom with Company Number 1979185 and
    VAT Number GB 411942866