• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 52 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.

AM62L-PROCESSOR-SDK: Polling Method in ILITEK Touch Driver

Dheeraj K
Intellectual 750 points
Part Number: AM62L-PROCESSOR-SDK

Tool/software:

Dear TI Support Team,

I am currently working with the ILITEK2130 touchscreen controller on the AM62Lx platform. Due to hardware limitations, the CPU does not have a dedicated interrupt line available for the touch interface. As a workaround, I initially configured a GPIO as a touch interrupt, and this approach works correctly with some additional hardware wiring.

To simplify the hardware setup, I wanted to explore the possibility of using the polling method with an interval of 17 ms. However, while testing this approach, I encountered the following error from the touch driver.

--ilitek_ts 1-0041: get touch info failed. Wrong id: 0x00--

I would like to understand whether this issue is related to the CPU’s capabilities (e.g., limitations in I2C polling or timing behavior), or if it is entirely dependent on how the ILITEK2130 driver is implemented.

Could you please provide some guidance on whether polling mode is supported and stable for this use case on the AM62Lx platform? Any suggestions to resolve or debug this issue would be greatly appreciated.

Regards,
Dheeraj K

  • 0
    TI__Guru** 101030 points

    Hello Dheeraj,

    Just to set support expectations, we can answer questions about TI hardware and TI software on this forum, but we cannot answer questions about modifying drivers or writing custom kernel code. We will be limited in the support that we can offer.

    First off, keep in mind that even if you are using RT Linux, RT Linux is not a true real-time OS. 17 msec is not a latency that you can guarantee with regular Linux, but I would expect it to be a pretty reasonable target with RT Linux if you adjust the real-time priority of your code properly. I would be more concerned if you were trying to guarantee a response time within tens or hundreds of microseconds (usec).

    Without looking at the touch driver, that looks like a programming issue rather than a timing issue. I'll pass your thread over to one of my team mates for any followup questions.

    Regards,

    Nick