• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 373 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.

USB In OMAP L137

Ted10200
Prodigy 10 points
Other Parts Discussed in Thread: OMAP-L137

Hi,

I am planning to use OMAP L137 based platform (EVMOMAPL137) In my project. I learnt from internet that GA-SDK release of the stack (and its previous version) will have USB driver included.

My question is related to USB. If I want to configure my device as USB mass storage device and also compatible to printer class device(USB OTG functionality) what will be the effort for application development when I use the GA SDK driver stack? Does it include some sample code for USB OTG device and host? Can you comment on the complexity?

One more question on the LCD driver: It is a 16 bit LCD controller, can you indicate some of  the compatible LCD display devices that it can connect to?

Regards.

  • 0
    TI__Expert 7435 points

    Ted,

    If I understand you want to do thw following witht the L137 based product in USB device mode

    1. Mass Storage device

    2. Printer class device

    In both the above 2 cases you are using the product as USB device and hence would not need OTG as an functionality to be supported.  Am I right in assuming this or have I missed something.

    If I have missed out some details pl. educated me on the same.

     

    regards

    swami

  • 0
    TI__Mastermind 37340 points

    To add to Swami' comments, our hardware supports OTG (see data-sheet); however, Swami is a better person to comment on the software support that will be included in our USB driver. 

    That said, once the USB driver is available, your application would simply use standardized Linux API to access devices.  For example, for a mass storage device you would use open(/dev/sda1) API (or similar device name) to get a handle to mass storage device and use read() and write() APIs to access device (among other APIs).  The point is that it should be as easy as writting your application in any other Linux platform, simply use the APIs available for the OS.

    With regards to LCD hardware, yes it is 16-bit.  It is actually to LCD controllers in one; one provides a synchronous interface and the other a asychronous interface; this provides compatibility with a good array of LCDs out there (see http://focus.ti.com/lit/ug/sprugb7/sprugb7.pdf for more details).  Unfortunately, I am not aware of any reference designs I can refer you to at the moment.

  • 0 in reply to Juan Gonzales
    Intellectual 805 points

    Hi

    One more question regarding the USB2.0 reference clock,
    The reference clock can be sourced from either USB_REFCLKIN pin or from the AUXCLK,
    what should be the amplitude of the clock when an external oscillator (USB_REFCLKIN pin)is
    used.Is there any reference circuit(with load capacitance).
    *It seems OMAP-L137 EVM is using AUXCLK

    Thankyou.