• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 585 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.

Linux/AM5718: problem in custom application

ALWALA MOUNIKA
Intellectual 280 points

Part Number: AM5718

Tool/software: Linux

Hi,

We have customised the am5718 processor using sdk ti-processor-sdk-linux-am57xx-evm-05.02.00.10. We are able to enter in to the root successfully and after loading TFT application we are facing the problem related to the navigation keys. The navigation keys will get disappear for a while and that particular key spot will remain black for sometime after pressing that particular key. Kindly suggest us how can we resolve the issue with the custom application and the navigation keys.

Thanks and Regards,

A.Mounika.

  • 0
    TI__Guru 55345 points

    Hello A.Mounika,

    Your navigation keys are probably falling into race condition with an another application like seen in this thread. Please, check this out.

    Best regards,
    Kemal

  • 0 in reply to Kemal R. Shakir
    Intellectual 280 points

    Hi,

    I have gone through the thread and in that they are having the weston application running but whereas the application which we are using doesn't have weston services as it is based on systemd services. So kindly suggest what might be the problem.

    Thanks and Regards,

    A.Mounika.

  • 0 in reply to ALWALA MOUNIKA
    Intellectual 280 points

    And the below listed processes are running while the application is running.

    root@am57xx-evm:~# ps -aef
    UID        PID  PPID  C STIME TTY          TIME CMD
    root         1     0  0 03:33 ?        00:00:05 /sbin/init
    root         2     0  0 03:33 ?        00:00:00 [kthreadd]
    root         4     2  0 03:33 ?        00:00:00 [kworker/0:0H]
    root         6     2  0 03:33 ?        00:00:00 [mm_percpu_wq]
    root         7     2  0 03:33 ?        00:00:00 [ksoftirqd/0]
    root         8     2  0 03:33 ?        00:00:01 [rcu_preempt]
    root         9     2  0 03:33 ?        00:00:00 [rcu_sched]
    root        10     2  0 03:33 ?        00:00:00 [rcu_bh]
    root        11     2  0 03:33 ?        00:00:00 [migration/0]
    root        12     2  0 03:33 ?        00:00:00 [cpuhp/0]
    root        13     2  0 03:33 ?        00:00:00 [kdevtmpfs]
    root        14     2  0 03:33 ?        00:00:00 [netns]
    root        16     2  0 03:33 ?        00:00:00 [oom_reaper]
    root        17     2  0 03:33 ?        00:00:00 [writeback]
    root        18     2  0 03:33 ?        00:00:00 [kcompactd0]
    root        19     2  0 03:33 ?        00:00:00 [crypto]
    root        20     2  0 03:33 ?        00:00:00 [kblockd]
    root        21     2  0 03:33 ?        00:00:00 [irq/80-48070000]
    root        22     2  0 03:33 ?        00:00:00 [edac-poller]
    root        23     2  0 03:33 ?        00:00:00 [watchdogd]
    root        24     2  0 03:33 ?        00:00:00 [rpciod]
    root        25     2  0 03:33 ?        00:00:00 [xprtiod]
    root        26     2  0 03:33 ?        00:00:00 [kswapd0]
    root        27     2  0 03:33 ?        00:00:00 [nfsiod]
    root        39     2  0 03:33 ?        00:00:00 [kpcitest]
    root        41     2  0 03:33 ?        00:00:00 [irq/25-talert]
    root        42     2  0 03:33 ?        00:00:00 [irq/81-mmc0]
    root        43     2  0 03:33 ?        00:00:00 [irq/173-4809c00]
    root        45     2  0 03:33 ?        00:00:00 [irq/82-mmc1]
    root        46     2  0 03:33 ?        00:00:01 [kworker/0:3]
    root        47     2  0 03:33 ?        00:00:00 [irq/91-48468000]
    root        48     2  0 03:33 ?        00:00:00 [irq/90-48468000]
    root        49     2  0 03:33 ?        00:00:00 [ipv6_addrconf]
    root        50     2  0 03:33 ?        00:00:00 [mmcqd/1]
    root        51     2  0 03:33 ?        00:00:00 [mmcqd/1boot0]
    root        52     2  0 03:33 ?        00:00:00 [mmcqd/1boot1]
    root        53     2  0 03:33 ?        00:00:00 [mmcqd/1rpmb]
    root        54     2  0 03:33 ?        00:00:00 [kworker/0:1H]
    root        55     2  0 03:33 ?        00:00:00 [jbd2/mmcblk1p2-]
    root        56     2  0 03:33 ?        00:00:00 [ext4-rsv-conver]
    root        69     1  0 03:33 ?        00:00:04 /lib/systemd/systemd-journald
    root        79     2  0 03:33 ?        00:00:00 [cryptodev_queue]
    root        88     2  0 03:33 ?        00:00:00 [kworker/u2:2]
    root        91     1  0 03:33 ?        00:00:00 /lib/systemd/systemd-udevd
    systemd+   102     1  0 03:33 ?        00:00:00 /lib/systemd/systemd-timesyncd
    root       179     2  0 03:34 ?        00:00:00 [480a5000.des-en]
    root       215     2  0 03:34 ?        00:00:00 [irq/88-dwc3-oma]
    root       218     2  0 03:34 ?        00:00:00 [irq/89-dwc3-oma]
    systemd+   223     1  0 03:34 ?        00:00:00 /lib/systemd/systemd-networkd
    root       240     2  0 03:34 ?        00:00:00 [ptp0]
    root       284     2  0 03:34 ?        00:00:00 [ata_sff]
    root       314     2  0 03:34 ?        00:00:00 [4b500000.aes-en]
    root       323     2  0 03:34 ?        00:00:00 [4b700000.aes-en]
    root       327     2  0 03:34 ?        00:00:00 [scsi_eh_0]
    root       332     2  0 03:34 ?        00:00:00 [scsi_tmf_0]
    root       503     1  0 03:34 ?        00:00:00 /usr/sbin/atd -f
    root       513     1  0 03:34 ?        00:00:00 /usr/sbin/crond -n
    rpc        518     1  0 03:34 ?        00:00:00 /usr/sbin/rpcbind
    message+   523     1  0 03:34 ?        00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
    root       524     1  0 03:34 ?        00:00:00 /usr/bin/lad_dra7xx -g -l lad.txt
    root       528     1  0 03:34 ?        00:00:00 /usr/sbin/telnetd
    root       529     1  0 03:34 ?        00:00:00 /lib/systemd/systemd-logind
    root       530     1  0 03:34 ?        00:00:00 /sbin/klogd -n
    root       531     1  0 03:34 ?        00:00:00 /sbin/syslogd -n
    root       533     1  0 03:34 ?        00:00:00 /usr/sbin/rngd -f -r /dev/urandom
    nobody     640     1  0 03:34 ?        00:00:00 /usr/sbin/thttpd -d /srv/www -p 8080
    systemd+   642     1  0 03:34 ?        00:00:00 /lib/systemd/systemd-resolved
    root       644     1  0 03:34 ttyS0    00:00:00 /bin/login -f
    rpcuser    650     1  0 03:34 ?        00:00:00 /usr/sbin/rpc.statd -F
    root       653     1  0 03:34 ?        00:00:00 /bin/sh /etc/init.d/App.sh
    root       663     1  0 03:34 ?        00:00:00 /lib/systemd/systemd --user
    root       665   663  0 03:34 ?        00:00:00 (sd-pam)
    root       669   644  0 03:34 ttyS0    00:00:00 -sh
    root       679     2  0 03:34 ?        00:00:00 [kworker/u2:3]
    root       691   653 98 03:34 ?        00:15:22 /home/medha/TFTSoft/TFTAPP -qws
    root       857     2  0 03:39 ?        00:00:01 [kworker/0:0]
    root       913     2  0 03:45 ?        00:00:00 [kworker/0:1]
    root       934     2  0 03:48 ?        00:00:00 [kworker/0:2]
    root       941   669  0 03:49 ttyS0    00:00:00 ps -aef
    root@am57xx-evm:~#

  • 0 in reply to ALWALA MOUNIKA
    TI__Guru 55345 points

    ALWALA MOUNIKA said:
    root       691   653 98 03:34 ?        00:15:22 /home/medha/TFTSoft/TFTAPP -qws


    Can you change this command to root       691   653 98 03:34 ?        00:15:22 /home/medha/TFTSoft/TFTAPP -platform eglfs and retry?

  • 0 in reply to Kemal R. Shakir
    Intellectual 820 points

    Hi Sir,

    We tried as you suggested and the application didn't run and we have observed the below messages in the console.

    root@am57xx-evm:~# TFT_DISPLAY/CONFIG_SOFTWARE -platform eglfs &
    [1] 864
    root@am57xx-evm:~# QWSSocket::connectToLocalFile could not connect:: No such file or directory
    QWSSocket::connectToLocalFile could not connect:: No such file or directory
    QWSSocket::connectToLocalFile could not connect:: No such file or directory
    QWSSocket::connectToLocalFile could not connect:: No such file or directory
    QWSSocket::connectToLocalFile could not connect:: No such file or directory
    QWSSocket::connectToLocalFile could not connect:: No such file or directory
    No Qt for Embedded Linux server appears to be running.
    If you want to run this program as a server,
    add the "-qws" command-line option.

    Thanks and Regards,

    A.Mounika

  • 0 in reply to Potturu Venkata Prasad
    TI__Guru 55345 points

    Can you recompile this application against ti-processor-sdk-linux-am57xx-evm-05.02.00.10 Qt environment? These two links might be in helpful.

    processors.wiki.ti.com/.../Qt_4_to_5_Migration
    wiki.qt.io/Transition_from_Qt_4.x_to_Qt5

  • 0 in reply to Kemal R. Shakir
    Intellectual 820 points

    Hi Sir,

    As our custom application is compiled with Qt4 libraries and due to the time constraint presently recompiling

    the application with the Qt5 libraries may not be possible. So, kindly can you help us where can we get the

    Qt4 libraries inorder to rebuild the application with Qt4 libraries.

    Thanks and Regards,

    A.Mounika.

  • 0 in reply to Potturu Venkata Prasad
    TI__Guru 55345 points

    Hello A.Mounika,

    AM57xx is a quite a new platform so that there is no old Processor SDK version with Qt4 support for it.

    Best regards,
    Kemal

  • 0 in reply to Kemal R. Shakir
    TI__Guru 55345 points

    Hello A.Mounika,

    Please, close this thread by clicking on "This resolved my issue" button if you are done with it.

    Best regards,
    Kemal