Linux/TDA2P-ACD: VisionSDK 3.0.4 Failed to start the weston

user5312037

Part Number: TDA2P-ACD

Tool/software: Linux

Hello:

The latest release of VisionSDK release that:

Major New Features in the Release New features in the release vs previous Vision SDK release are:  vDRM Display distributor links for HLOS compositor (Weston) with M4 display

and how we can setup the weston environment properly?

when run " weston --tty=1 --backend=drm-backend.so"

Date: 2018-06-11 UTC
[20:00:40.154] weston 1.9.0
               http://wayland.freedesktop.org
               Bug reports to: bugs.freedesktop.org/enter_bug.cgi
               Build: 1.8.93-2-gb05cdb8 configure.ac: bump to version 1.9.0 for the official release (2015-09-21 18:11:26 -0700)
[20:00:40.154] OS: Linux, 4.4.84-00110-g27dd75b-dirty, #18 SMP PREEMPT Mon Jul 2 23:32:04 PDT 2018, armv7l
[20:00:40.155] Using config file '/etc//weston.ini'
[20:00:40.155] Loading module '/usr/lib/weston/drm-backend.so'
[20:00:40.159] Output repaint window is 7 ms maximum.
[20:00:40.159] initializing drm backend
[20:00:40.161] using /dev/dri/card0
[20:00:40.161] Loading module '/usr/lib/weston/gl-renderer.so'
loaded module : gbm_pvr.so
found valid GBM backend : gbm_pvr.so
PVR:(Error): [  800->  800] <              gbm_pvr_create_device():645|ERROR> Failed to create DBM device: No such device [0, ]
[20:00:40.165] failed to initialize egl
[20:00:40.165] fatal: failed to create compositor backend

over 8 years ago

0 user5312037 over 8 years ago

Genius 4320 points

Hello:
we expect to run the QT application on VisionSDK...

0 Subhajit Paul over 8 years ago in reply to user5312037

TI__Expert 7015 points

Weston is running by default after the system boots to prompt. Nothing will be visible unless the weston buffers are routed to M4. This is done when apps.out is launched and usecase 1 -> 8 is started.

The default bootargs must be modified to enable weston. Add cma=128M to kernel bootargs

To relaunch weston manually, first kill weston by executing
# /etc/init.d/weston stop
and then launch
# weston --tty=1 --idle-time=0 --backend=drm-backend.so &

QT application can run on weston, after weston is started

Regards,
Subhajit

0 user5312037 over 8 years ago in reply to Subhajit Paul

Genius 4320 points

Hello:

when i run my qt application got error:

root@dra7xx-evm:~/build-avm_qt_app-TI_QT5_ARM-Debug# ./avm_qt_app
[AVMS]log_init. server log_to_console=1, log_to_shm=1
This application failed to start because it could not find or load the Qt platform plugin "wayland"
in "".

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen.

Reinstalling the application may fix this problem.
Aborted (core dumped)

and the environment is:

export EDITOR="vi"
export HOME="/home/root"
export HUSHLOGIN="FALSE"
export LOGNAME="root"
export MAIL="/var/spool/mail/root"
export OLDPWD="/home/root"
export OPIEDIR
export PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin"
export PS1="\\u@\\h:\\w\\\$ "
export PWD="/home/root/build-avm_qt_app-TI_QT5_ARM-Debug"
export QPEDIR
export QTDIR
export QT_QPA_GENERIC_PLUGINS="Auto"
export SHELL="/bin/sh"
export SHLVL="1"
export TERM="xterm"
export TZ="UTC"
export USER="root"
export WAYLAND_DISPLAY="wayland-0"
export WS_CALUDEV_FILE="/etc/udev/rules.d/ws-calibrate.rules"
export XDG_CONFIG_HOME="/etc/"
export XDG_RUNTIME_DIR="/tmp/0-runtime-dir"
export XDG_SESSION_ID="c1"

Any suggestion, thanks

0 user5312037 over 8 years ago in reply to Subhajit Paul

Genius 4320 points

Hello:

when i run my qt application got error:

root@dra7xx-evm:~/build-avm_qt_app-TI_QT5_ARM-Debug# ./avm_qt_app
[AVMS]log_init. server log_to_console=1, log_to_shm=1
This application failed to start because it could not find or load the Qt platform plugin "wayland"
in "".

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen.

Reinstalling the application may fix this problem.
Aborted (core dumped)

and the environment is:

export EDITOR="vi"
export HOME="/home/root"
export HUSHLOGIN="FALSE"
export LOGNAME="root"
export MAIL="/var/spool/mail/root"
export OLDPWD="/home/root"
export OPIEDIR
export PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin"
export PS1="\\u@\\h:\\w\\\$ "
export PWD="/home/root/build-avm_qt_app-TI_QT5_ARM-Debug"
export QPEDIR
export QTDIR
export QT_QPA_GENERIC_PLUGINS="Auto"
export SHELL="/bin/sh"
export SHLVL="1"
export TERM="xterm"
export TZ="UTC"
export USER="root"
export WAYLAND_DISPLAY="wayland-0"
export WS_CALUDEV_FILE="/etc/udev/rules.d/ws-calibrate.rules"
export XDG_CONFIG_HOME="/etc/"
export XDG_RUNTIME_DIR="/tmp/0-runtime-dir"
export XDG_SESSION_ID="c1"

Any suggestion, thanks

0 Subhajit Paul over 8 years ago in reply to user5312037

TI__Expert 7015 points

Before launching the QT5 application, can you verify that weston is running? You can use "ps" command to verify.

Also, to run any application that uses wayland-egl you will need to add the following lines in /etc/powervr.ini. As an example, to enable weston-simple-egl, I added these lines

[weston-simple-egl]

DbmDriverName=vdrm

Can you also verify that you can run weston-simple-egl and see a rotating cube on screen?

Regards,

Subhajit

0 user5312037 over 8 years ago in reply to Subhajit Paul

Genius 4320 points

[  OK  ] Reached target System Initialization.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timers.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
[  OK  ] Started System Logging Service.
         Starting Permit User Sessions...
         Starting Login Service...
[  OK  ] Started D-Bus System Message Bus.
         Starting Network Service...
         Starting rc.pvr.service...
[  OK  ] Started Kernel Logging Service.
[  OK  ] Started Network Service.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started rc.pvr.service.
[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
         Starting weston.service...
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Network.
         Starting Network Name Resolution...
[  OK  ] Started weston.service.
[  OK  ] Started Login Service.

in startup, we can wenston is started, but later in ps, there is no wenston.

root@dra7xx-evm:~/build-avm_qt_app-TI_QT5_ARM-Debug# ps
  PID USER       VSZ STAT COMMAND
    1 root      4908 S    {systemd} /sbin/init
    2 root         0 SW   [kthreadd]
    3 root         0 SW   [ksoftirqd/0]
    5 root         0 SW<  [kworker/0:0H]
    6 root         0 SW   [kworker/u4:0]
    7 root         0 SW   [rcu_preempt]
    8 root         0 SW   [rcu_sched]
    9 root         0 SW   [rcu_bh]
   10 root         0 SW   [migration/0]
   11 root         0 SW   [migration/1]
   12 root         0 SW   [ksoftirqd/1]
   14 root         0 SW<  [kworker/1:0H]
   15 root         0 SW   [kdevtmpfs]
   16 root         0 SW<  [netns]
   17 root         0 SW<  [perf]
   18 root         0 SW   [kworker/0:1]
   19 root         0 SW<  [writeback]
   20 root         0 SW<  [crypto]
   21 root         0 SW<  [bioset]
   22 root         0 SW<  [kblockd]
   23 root         0 SW   [irq/329-4807000]
   24 root         0 SW   [irq/41-0-0020]
   25 root         0 SW   [irq/41-0-0021]
   26 root         0 SW   [irq/330-4806000]
   27 root         0 SW   [irq/331-4807a00]
   28 root         0 SW<  [edac-poller]
   29 root         0 SW<  [rpciod]
   30 root         0 SW   [kswapd0]
   31 root         0 SW<  [vmstat]
   32 root         0 SW   [fsnotify_mark]
   33 root         0 SW<  [nfsiod]
   42 root         0 SW<  [bioset]
   43 root         0 SW<  [bioset]
   44 root         0 SW<  [bioset]
   45 root         0 SW<  [bioset]
   46 root         0 SW<  [bioset]
   47 root         0 SW<  [bioset]
   48 root         0 SW<  [bioset]
   49 root         0 SW<  [bioset]
   50 root         0 SW   [spi1]
   51 root         0 SW   [spi2]
   52 root         0 SW   [spi32766]
   53 root         0 SW<  [bioset]
   54 root         0 SW<  [bioset]
   55 root         0 SW<  [bioset]
   56 root         0 SW<  [bioset]
   57 root         0 SW<  [bioset]
   58 root         0 SW<  [bioset]
   59 root         0 SW<  [bioset]
   60 root         0 SW   [kworker/u4:1]
   63 root         0 SW<  [kpsmoused]
   64 root         0 SW   [irq/27-talert]
   65 root         0 SW   [irq/230-4809c00]
   68 root         0 SW<  [ipv6_addrconf]
   69 root         0 SW<  [deferwq]
   72 root         0 SW   [kworker/1:1]
   73 root         0 SW<  [bioset]
   74 root         0 SW   [mmcqd/0]
   75 root         0 SW   [jbd2/mmcblk0p2-]
   76 root         0 SW<  [ext4-rsv-conver]
   77 root         0 SW<  [bioset]
   78 root         0 SW   [mmcqd/1]
   79 root         0 SW<  [bioset]
   80 root         0 SW   [mmcqd/1boot0]
   81 root         0 SW<  [bioset]
   82 root         0 SW   [mmcqd/1boot1]
  157 root     10244 S    /lib/systemd/systemd-journald
  176 root     10144 S    /lib/systemd/systemd-udevd
  237 systemd- 11992 S    /lib/systemd/systemd-timesyncd
  258 root         0 SW   [kworker/1:3]
  612 root      1976 S    /sbin/syslogd -n -C
  653 root      2600 S    /lib/systemd/systemd-logind
  657 root         0 SW   [kworker/0:3]
  662 messageb  4192 S    /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
  679 systemd-  2676 S    /lib/systemd/systemd-networkd
  690 root      1960 S    /sbin/klogd -n
  729 root      4864 S    /bin/login --
  734 root      1784 S    /sbin/agetty --noclear tty1 linux
  737 systemd-  2984 S    /lib/systemd/systemd-resolved
  752 root      9756 S    /usr/bin/lad_dra7xx -g -l lad.txt
  757 root      1960 S    /usr/sbin/telnetd
  766 root         0 SW   [irq/495-4806a00]
  768 root      5356 S    /lib/systemd/systemd --user
  772 root      7164 S    (sd-pam)
  778 root      2776 S    -sh
  800 root      2372 R    ps

root@dra7xx-evm:~/build-avm_qt_app-TI_QT5_ARM-Debug# /usr/bin/weston-simple-egl 
weston-simple-egl: ../weston-1.9.0/clients/simple-egl.c:858: main: Assertion `display.display' failed.
Aborted (core dumped)

0 Subhajit Paul over 8 years ago in reply to user5312037

TI__Expert 7015 points

Can you send me the fiel /var/log/weston.log?
Also, launch weston manually by executing <weston --tty=1 --idle-time=0 --backend=drm-backend.so> and send me the output.

Regards,
Subhajit

0 user5312037 over 8 years ago in reply to Subhajit Paul

Genius 4320 points

The /var/log/weston.log

root@dra7xx-evm:~# cat /var/log/weston.log 
Date: 2018-06-11 UTC
[19:54:20.857] weston 1.9.0
               http://wayland.freedesktop.org
               Bug reports to: bugs.freedesktop.org/enter_bug.cgi
               Build: 1.8.93-2-gb05cdb8 configure.ac: bump to version 1.9.0 for the official release (2015-09-21 18:11:26 -0700)
[19:54:20.857] OS: Linux, 4.4.84-00110-g27dd75b-dirty, #18 SMP PREEMPT Mon Jul 2 23:32:04 PDT 2018, armv7l
[19:54:20.864] Using config file '/etc//weston.ini'
[19:54:20.871] Loading module '/usr/lib/weston/drm-backend.so'
[19:54:20.904] Output repaint window is 7 ms maximum.
[19:54:20.904] initializing drm backend
[19:54:20.906] using /dev/dri/card0
[19:54:20.908] Loading module '/usr/lib/weston/gl-renderer.so'
loaded module : gbm_pvr.so
found valid GBM backend : gbm_pvr.so
[19:54:20.942] failed to initialize egl
[19:54:20.942] fatal: failed to create compositor backend
PVR:(Error): [  731->  731] <              gbm_pvr_create_device():645|ERROR> Failed to create DBM device: No such device [0, ]

weston --tty=1 --idle-time=0 --backend=drm-backend.so

Date: 2018-06-11 UTC
[19:55:47.819] weston 1.9.0
               http://wayland.freedesktop.org
               Bug reports to: bugs.freedesktop.org/enter_bug.cgi
               Build: 1.8.93-2-gb05cdb8 configure.ac: bump to version 1.9.0 for the official release (2015-09-21 18:11:26 -0700)
[19:55:47.819] OS: Linux, 4.4.84-00110-g27dd75b-dirty, #18 SMP PREEMPT Mon Jul 2 23:32:04 PDT 2018, armv7l
[19:55:47.819] Using config file '/etc//weston.ini'
[19:55:47.819] Loading module '/usr/lib/weston/drm-backend.so'
[19:55:47.823] Output repaint window is 7 ms maximum.
[19:55:47.823] initializing drm backend
[19:55:47.824] using /dev/dri/card0
[19:55:47.824] Loading module '/usr/lib/weston/gl-renderer.so'
loaded module : gbm_pvr.so
found valid GBM backend : gbm_pvr.so
PVR:(Error): [  791->  791] <              gbm_pvr_create_device():645|ERROR> Failed to create DBM device: No such device [0, ]
[19:55:47.828] failed to initialize egl
[19:55:47.828] fatal: failed to create compositor backend

0 user5312037 over 8 years ago in reply to Subhajit Paul

Genius 4320 points

/var/log/weston.log

Date: 2018-06-11 UTC
[19:54:20.857] weston 1.9.0
               http://wayland.freedesktop.org
               Bug reports to: bugs.freedesktop.org/enter_bug.cgi
               Build: 1.8.93-2-gb05cdb8 configure.ac: bump to version 1.9.0 for the official release (2015-09-21 18:11:26 -0700)
[19:54:20.857] OS: Linux, 4.4.84-00110-g27dd75b-dirty, #18 SMP PREEMPT Mon Jul 2 23:32:04 PDT 2018, armv7l
[19:54:20.864] Using config file '/etc//weston.ini'
[19:54:20.871] Loading module '/usr/lib/weston/drm-backend.so'
[19:54:20.904] Output repaint window is 7 ms maximum.
[19:54:20.904] initializing drm backend
[19:54:20.906] using /dev/dri/card0
[19:54:20.908] Loading module '/usr/lib/weston/gl-renderer.so'
loaded module : gbm_pvr.so
found valid GBM backend : gbm_pvr.so
[19:54:20.942] failed to initialize egl
[19:54:20.942] fatal: failed to create compositor backend
PVR:(Error): [  731->  731] <              gbm_pvr_create_device():645|ERROR> Failed to create DBM device: No such device [0, ]

root@dra7xx-evm:~# weston --tty=1 --idle-time=0 --backend=drm-backend.so

Date: 2018-06-11 UTC
[19:55:47.819] weston 1.9.0
               http://wayland.freedesktop.org
               Bug reports to: bugs.freedesktop.org/enter_bug.cgi
               Build: 1.8.93-2-gb05cdb8 configure.ac: bump to version 1.9.0 for the official release (2015-09-21 18:11:26 -0700)
[19:55:47.819] OS: Linux, 4.4.84-00110-g27dd75b-dirty, #18 SMP PREEMPT Mon Jul 2 23:32:04 PDT 2018, armv7l
[19:55:47.819] Using config file '/etc//weston.ini'
[19:55:47.819] Loading module '/usr/lib/weston/drm-backend.so'
[19:55:47.823] Output repaint window is 7 ms maximum.
[19:55:47.823] initializing drm backend
[19:55:47.824] using /dev/dri/card0
[19:55:47.824] Loading module '/usr/lib/weston/gl-renderer.so'
loaded module : gbm_pvr.so
found valid GBM backend : gbm_pvr.so
PVR:(Error): [  791->  791] <              gbm_pvr_create_device():645|ERROR> Failed to create DBM device: No such device [0, ]
[19:55:47.828] failed to initialize egl
[19:55:47.828] fatal: failed to create compositor backend

0 user5312037 over 8 years ago in reply to user5312037

Genius 4320 points

Date: 2018-06-11 UTC
[19:55:47.819] weston 1.9.0
http://wayland.freedesktop.org
Bug reports to: bugs.freedesktop.org/enter_bug.cgi
Build: 1.8.93-2-gb05cdb8 configure.ac: bump to version 1.9.0 for the official release (2015-09-21 18:11:26 -0700)
[19:55:47.819] OS: Linux, 4.4.84-00110-g27dd75b-dirty, #18 SMP PREEMPT Mon Jul 2 23:32:04 PDT 2018, armv7l
[19:55:47.819] Using config file '/etc//weston.ini'
[19:55:47.819] Loading module '/usr/lib/weston/drm-backend.so'
[19:55:47.823] Output repaint window is 7 ms maximum.
[19:55:47.823] initializing drm backend
[19:55:47.824] using /dev/dri/card0
[19:55:47.824] Loading module '/usr/lib/weston/gl-renderer.so'
loaded module : gbm_pvr.so
found valid GBM backend : gbm_pvr.so
PVR:(Error): [ 791-> 791] < gbm_pvr_create_device():645|ERROR> Failed to create DBM device: No such device [0, ]
[19:55:47.828] failed to initialize egl
[19:55:47.828] fatal: failed to create compositor backend

0 user5312037 over 8 years ago in reply to user5312037

Genius 4320 points

/var/log/weston.log

Date: 2018-06-11 UTC
[19:54:20.857] weston 1.9.0
               http://wayland.freedesktop.org
               Bug reports to: bugs.freedesktop.org/enter_bug.cgi
               Build: 1.8.93-2-gb05cdb8 configure.ac: bump to version 1.9.0 for the official release (2015-09-21 18:11:26 -0700)
[19:54:20.857] OS: Linux, 4.4.84-00110-g27dd75b-dirty, #18 SMP PREEMPT Mon Jul 2 23:32:04 PDT 2018, armv7l
[19:54:20.864] Using config file '/etc//weston.ini'
[19:54:20.871] Loading module '/usr/lib/weston/drm-backend.so'
[19:54:20.904] Output repaint window is 7 ms maximum.
[19:54:20.904] initializing drm backend
[19:54:20.906] using /dev/dri/card0
[19:54:20.908] Loading module '/usr/lib/weston/gl-renderer.so'
loaded module : gbm_pvr.so
found valid GBM backend : gbm_pvr.so
[19:54:20.942] failed to initialize egl
[19:54:20.942] fatal: failed to create compositor backend
PVR:(Error): [  731->  731] <              gbm_pvr_create_device():645|ERROR> Failed to create DBM device: No such device [0, ]
root@dra7xx-evm:~#

0 Subhajit Paul over 8 years ago in reply to user5312037

TI__Expert 7015 points

Do you have the following prerequisites enabled for weston? You must have cma=128M in the kernel bootargs and the following two lines in /etc/powervr.ini

[weston]
DbmDriverName=vdrm

Please send me (attach) the file /etc/powervr.ini

If you are using SD card based boot, send me the uenv.txt file from the SD card boot folder

0 user5312037 over 8 years ago in reply to Subhajit Paul

Genius 4320 points

Fullscreen 0207.uenv.txt Download

fdtfile=dra76-evm-infoadas.dtb
args_mmc=part uuid mmc 0:2 uuid; setenv bootargs "console=ttyO0,115200n8 vram=16M root=PARTUUID=${uuid} rw rootwait ip=none mem=1024M cma=128M"

root@dra7xx-evm:~# cat /proc/cmdline 
console=ttyO0,115200n8 elevator=noop root=/dev/mmcblk0p2 rw rootwait earlyprintk fixrtc omapdrm.num_crtc=2 consoleblank=0 cma=64M rootfstype=ext4 snd.slots_reserved=1,1 loglevel=0 clk_ignore_unused init=/home/root/init-demo.sh

root@dra7xx-evm:~# cat /etc/powervr.ini 
[default]
#WindowSystem=libpvrws_WAYLAND.so

[weston]
DbmDriverName=vdrm

0 Subhajit Paul over 8 years ago in reply to user5312037

TI__Expert 7015 points

Why is the attached uenv.txt different from /proc/cmdline content?

Also, are there any trailing spaces in /etc/powervr.ini?

Regards,

Subhajit

0 user5312037 over 8 years ago in reply to Subhajit Paul

Genius 4320 points

Hi:
I'm also confused that the uenv.txt is 128M but the command line is 64M.
Have check that in host there is no trailing space.

0 user5312037 over 8 years ago in reply to Subhajit Paul

Genius 4320 points

Hello:
In VisionSDK 3.0.4 the uenv.txt is not used again?
when i change t" fdtfile=dra7-evm-infoadas.dtb" (the original configuration from build), the td2px evm board also can boot.

0 user5312037 over 8 years ago in reply to Subhajit Paul

Genius 4320 points

Hello:
when i remove the cma=128m in uenv.txt, the commandline out is still cma=64m

0 Subhajit Paul over 8 years ago in reply to user5312037

TI__Expert 7015 points

Shiju Sivasankaran can you help here? Why the uenv.txt changes are not taking effect?

0 user5312037 over 8 years ago in reply to Subhajit Paul

Genius 4320 points

Hello:
add "cma=128M" work on VisionSDK 3.0.3 but not work on VisionSDK 3.0.4

0 user5312037 over 8 years ago in reply to user5312037

Genius 4320 points

Hi:
@Shiju Sivasankaran @Subhajit Paul
any updates?

0 user5312037 over 8 years ago in reply to Subhajit Paul

Genius 4320 points

Hello All:

Shiju Sivasankaran any update?

0 Subhajit Paul over 8 years ago in reply to user5312037

TI__Expert 7015 points

Hi,

are you validating this on TI EVM? Are you using SD/MMC based booting?

You are reporting that you updated /etc/powervr.ini but the changes are not taking effect. This is not an expected behaviour with SD/MMC boot.

Regards,
Subhajit

0 user5312037 over 8 years ago in reply to Subhajit Paul

Genius 4320 points

Hello :
All test is validate on TI TDA2Px EVM with SDCard booting.

so now, not update the /etc/powervr.ini, we just update the uenv.txt to set the CMA to 128M as discussed above.

0 Subhajit Paul over 8 years ago in reply to user5312037

TI__Expert 7015 points

So, can you see that you have 128 MB of CMA in the system now? you can verify this from the bootlog. It should say "cma: Reserved 128MiB at xxxx".
If you can validate the CMA, you can change the file /etc/powervr.ini and try again

0 user5312037 over 8 years ago in reply to Subhajit Paul

Genius 4320 points

Hello:
I'v post this e2e.ti.com/.../709916
and now weston seem ok.

0 user5312037 over 8 years ago in reply to Subhajit Paul

Genius 4320 points

Hello:

now we can run the weston-simple-egl as following without camera.

root@dra7xx-evm:~/build-avm_qt_app-TI_QT5_ARM-Debug#  weston-simple-egl
wlpvr: PVR Services Initialised

301 frames in 5 seconds: 60.200001 fps
301 frames in 5 seconds: 60.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
297 frames in 5 seconds: 59.400002 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps
296 frames in 5 seconds: 59.200001 fps

and no hdmi output.

for my QT application, how i can run it properly?

root@dra7xx-evm:~/build-avm_qt_app-TI_QT5_ARM-Debug# ./avm_qt_app
[AVMS]log_init. server log_to_console=1, log_to_shm=1
This application failed to start because it could not find or load the Qt platform plugin "wayland"
in "".

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen.

Reinstalling the application may fix this problem.
Aborted (core dumped)
root@dra7xx-evm:~/build-avm_qt_app-TI_QT5_ARM-Debug#

0 Subhajit Paul over 8 years ago in reply to user5312037

TI__Expert 7015 points

Can you add a section in /etc/powervr.ini so that avm_qt_app can use vdrm

[avm_qt_app]
DbmDriverName=vdrm

Processors

Processors forum

Linux/TDA2P-ACD: VisionSDK 3.0.4 Failed to start the weston