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

TDA4x: weston/wayland support

Madhav Chamle
Intellectual 800 points

Dear Sir,

I have installed 

processor SDK RTOS j721E (version-7.01.00.11) on

Ubuntu Version - 18.04

Mode : Linux+RTOS 

I am trying launch weston and tried to run graphics demos.

i am getting the error elow for checking modetest

root@j7-evm:/opt/vision_apps# modetest -c
trying to open device 'i915'...failed
trying to open device 'amdgpu'...failed
trying to open device 'radeon'...failed
trying to open device 'nouveau'...failed
trying to open device 'vmwgfx'...failed
trying to open device 'omapdrm'...failed
trying to open device 'exynos'...failed
trying to open device 'tilcdc'...failed
trying to open device 'msm'...failed
trying to open device 'sti'...failed
trying to open device 'tegra'...failed
trying to open device 'imx-drm'...failed
trying to open device 'rockchip'...failed
trying to open device 'atmel-hlcdc'...failed
trying to open device 'fsl-dcu-drm'...failed
trying to open device 'vc4'...failed
trying to open device 'virtio_gpu'...failed
trying to open device 'mediatek'...failed
trying to open device 'meson'...failed
trying to open device 'pl111'...failed
trying to open device 'stm'...failed
trying to open device 'sun4i-drm'...failed
trying to open device 'armada-drm'...failed
no device found

and getting eeror while weston launch

root@j7-evm:/usr/bin# weston-launch
weston: failed to get current keyboard mode: Inappropriate ioctl for device

Thanks,

Madhav

  • 0
    Intellectual 800 points

    please find the weston log

    root@j7-evm:/opt/vision_apps# cat /var/log/weston.log
    Date: 2020-11-19 UTC
    [18:09:28.097] weston 8.0.0
    wayland.freedesktop.org
    Bug reports to: gitlab.freedesktop.org/.../
    Build: 8.0.0
    [18:09:28.097] Command line: /usr/bin/weston --log=/var/log/weston.log
    [18:09:28.097] OS: Linux, 5.4.74-g9574bba32a, #1 SMP PREEMPT Thu Nov 19 18:30:39 UTC 2020, aarch64
    [18:09:28.106] Using config file '/etc/xdg/weston/weston.ini'
    [18:09:28.108] Output repaint window is 7 ms maximum.
    [18:09:28.112] Loading module '/usr/lib/libweston-8/drm-backend.so'
    [18:09:28.117] initializing drm backend
    [18:09:28.117] logind: failed to get session seat
    [18:09:28.117] logind: cannot setup systemd-logind helper (-61), using legacy fallback
    [18:09:28.166] no drm device found
    [18:09:28.166] fatal: failed to create compositor backend
    Date: 2020-11-19 UTC
    [18:09:28.675] weston 8.0.0
    wayland.freedesktop.org
    Bug reports to: gitlab.freedesktop.org/.../
    Build: 8.0.0
    [18:09:28.675] Command line: weston --idle-time=0
    [18:09:28.675] OS: Linux, 5.4.74-g9574bba32a, #1 SMP PREEMPT Thu Nov 19 18:30:39 UTC 2020, aarch64
    [18:09:28.678] Using config file '/etc//weston.ini'
    [18:09:28.679] Output repaint window is 7 ms maximum.
    [18:09:28.679] Loading module '/usr/lib/libweston-8/drm-backend.so'
    [18:09:28.682] initializing drm backend
    [18:09:28.682] logind: not running in a systemd session
    [18:09:28.682] logind: cannot setup systemd-logind helper (-61), using legacy fallback
    [18:09:28.683] no drm device found
    [18:09:28.683] fatal: failed to create compositor backend
    Internal warning: debug scope 'drm-backend' has not been destroyed.
    Date: 2020-11-19 UTC
    [18:10:28.914] weston 8.0.0
    wayland.freedesktop.org
    Bug reports to: gitlab.freedesktop.org/.../
    Build: 8.0.0
    [18:10:28.914] Command line: weston --idle-time=0
    [18:10:28.914] OS: Linux, 5.4.74-g9574bba32a, #1 SMP PREEMPT Thu Nov 19 18:30:39 UTC 2020, aarch64
    [18:10:28.914] Using config file '/etc//weston.ini'
    [18:10:28.914] Output repaint window is 7 ms maximum.
    [18:10:28.914] Loading module '/usr/lib/libweston-8/drm-backend.so'
    [18:10:28.917] initializing drm backend
    [18:10:28.918] logind: failed to get session seat
    [18:10:28.918] logind: cannot setup systemd-logind helper (-61), using legacy fallback
    [18:10:28.918] <stdin> is already in graphics mode, is another display server running?
    [18:10:28.918] fatal: drm backend should be run using weston-launch binary, or your system should provide the logind D-Bus API.
    [18:10:28.918] fatal: failed to create compositor backend
    Internal warning: debug scope 'drm-backend' has not been destroyed.

  • 0 in reply to Madhav Chamle
    Intellectual 800 points

    Dear Sir,

    Any update on this thread

    Thanks,

    Madhav

  • 0 in reply to Madhav Chamle
    TI__Mastermind 36307 points

    Hello Madhav,

    This issue is because the display driver is disabled in the Linux+RTOS configuration. The Display is given to the R5 core, thus Linux has no control.You will not be able to use Wayland/Weston if you are running in the Linux+RTOS due to this.

    The Linux+RTOS method of sending GPU framebuffers to the display is to use an OpenVX graph with the GPU and the Display node. There are examples of this in Vision Apps documentation like this:

    https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/08_02_00_05/exports/docs/vision_apps/docs/user_guide/group_apps_basic_demos_app_arm_mosaic.html

    Regards,

    Erick