• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 261 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.

Touch screen driver on OMAP3530 EVM

mursel yildiz
Prodigy 150 points
Other Parts Discussed in Thread: OMAP3530

Hi everyone,

I am using omap3530 EVM board of mistral solutions company. In my company we are trying to use all drivers for the board that are supplied by SDK.1.0.2. Nowadays I am interested in using touch screen drivers (McSPI 1). I could not find unfortunately any documents related to the subject.

Could someone please suggest me a solution for this problem ? For example what should be the steps that are followed for reading x and y coordinates at the instant user touches the screen?

Regards...

  • 0
    TI__Mastermind 41665 points

    There is some minimal documentation on the touch screen driver for the OMAP3 in the OMAP35x_SDK_1.0.2\docs\OMAP35x\DataSheet_1_0_2.pdf section 2.11, but it only really describes that the driver exists and how some of it works underneath. Typically as a user you would not be taking the input data directly from the touch screen, rather the touch screen driver interfaces with a higher level graphical display, essentially your desktop windowing system, such as X. I am not very familiar with the APIs it uses at that interface but I can say I have seen it working before, just like a mouse.

  • 0 in reply to Bernie Thompson TI
    Prodigy 150 points

    I actually tried to use SPI driver in order to directly communicate with touch screen controller IC. I tried to read TX and RX registers of McSPI1 however got always segmentation fault errors. Morever, looking at the devices and drivers sections inside linux while EVM operates, it is obvious that event1 of inputs is directly related with this IC. Trying to read and observe event1 data, it was clear that there exists 256 B changing when touchscreen is touched and this is exactly what hardware user guide explains in memory map section for McSPI1. I could not be sure about which element of event1 is related with RX and TX registers.