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.

Linux/AM3354: Starter Kit touchscreen issue

Part Number: AM3354

Tool/software: Linux

Hi,
I am running some evaluation tests on "AM335x Starter Kit" board.

The board is shipped with the SDK version "ti-sdk-am335x-evm-06.00.00.00", and the demo program related ti this SDK works fine.
Anyway, being this SDK version quite old, I downloaded the SDK version "ti-processor-sdk-linux-am335x-evm-05.02.00.10" (from http://software-dl.ti.com/processor-sdk-linux/esd/AM335X/latest/index_FDS.html).

The demo program related to this SDK shows the following problem.
The touch on the demo program main screen (matrix-gui-2.0 application) does not work properly, it is very hard (I would say impossible) to navigate the demo program selecting the icons. Even pressing the icons hard nothing happens.

Anyway, entering the other applications reachable by main screen (for example connecting a mouse or connecting via web page to the board), as Touch/Interaction of Qt for example, the touch works properly.
I have already tried the recalibration of the touchscreen (both deleting calibration file then restarting, and running "weston-calibrator" program), but there was no improvement.

This behaviuor is the same on both the board we have, and it is the same with SDK version "ti-processor-sdk-linux-am335x-evm-05.03.00.07".

Can you please help me with this issue?

Thanks.

  • Hello Paolo,

    Checking to see if I can replicate your observations on my side.

    Regards,
    Nick
  • Hello Paolo,

    I am able to replicate your observations on SDK 4.3 and SDK 5.2. It looks like this is known behavior - apparently it is difficult to get a clean power-up touchscreen calibration on this board. If you are able to get a clean calibration (maybe with a stylus?) then the touchscreen is supposed to work properly. I have not gotten a clean calibration in my limited tests.

    I do not fully understand why the resistive touchscreen does not work well on this EVM, but I think it is related to the touchscreen or the board design rather than the AM335x itself.

    Do you need to be able to use the resistive touchscreen in your development?

    Regards,
    Nick
  • Hello Nick,
    thanks for your quick response.

    I tried to recalibrate the touchscreen with a stylus, and the result is slightly better, especially if you then use the stylus to select icons (instead of the fingers).

    Anyway the SDK version "ti-sdk-am335x-evm-06.00.00.00" works much better from touchscreen point of view.

    During the first part of the development we are going to use the resistive touchscreen.

    Thanks,
    Paolo

  • Hello Paolo,

    Got it. FYI, progression is SDK 6 -> 7 -> 8 -> Processor SDK 1 -> 2 -> ... -> Processor SDK 5.2, so SDK 6 came out many years back.

    We did not use Weston in that old software release. I have not tested, but I have heard that touchscreen performance on SDK 6 was not good, and then when Weston was introduced the increased sensitivity made touchscreen performance much worse.

    If the stylus is good enough for your development, I will close this thread. If it is gating development, I can do a bit more digging to see what our options are.

    Regards,
    Nick
  • Hello,
    at current stage of the project we are not yet developing the touchscreen application, so I am not able to answer, maybe I'll get in touch later with more details or requests.

    Anyway, generally speaking, it would be good to have an evaluation board + demo program working better.

    Thanks and regards,
    Paolo
  • Hello Paolo,

    Got it. I will go ahead and mark this thread resolved for now. If you need to continue the conversation later in development, please feel free to reply on this thread or create a new thread.

    Regards,
    Nick
  • Hello Paolo,

    Final note: there is a way to revert from wayland/weston to the older UI configuration used in amsdk-6.0. I am not the expert on that process, but I believe it involves making changes to the Yocto build. If you want to use the older UI configuration later in your testing, please create a new e2e thread to ask about how to make those changes. E.g., you could go to the top of this page and click the "Ask a related question" button. That way there will be a link to this thread in your new thread.

    Regards,
    Nick