I’m building my custom Yocto image for Verdin iMX8MM on Dahlia board. When I’m booting my system with the DeviceTree for Dahlia Board, I don’t have any output on HDMI (native on board or the DSI-to-HDMI expansion board). However, when I select the devicetree for Development Board, I’m getting the output on the DSI-to-HDMI.
Using the Dahlia device tree, I see the Weston service is failing
Oct 30 12:17:03 verdin-imx8mm-07237522 systemd: Starting Weston, a Wayland compositor, as a system service...
Oct 30 12:17:04 verdin-imx8mm-07237522 systemd: weston.service: Main process exited, code=exited, status=1/FAILURE
Oct 30 12:17:04 verdin-imx8mm-07237522 systemd: weston.service: Failed with result 'exit-code'.
Oct 30 12:17:04 verdin-imx8mm-07237522 systemd: Failed to start Weston, a Wayland compositor, as a system service
When I try to run Weston manually, I’m getting the following error:
root@verdin-imx8mm-07237522:~# /usr/bin/weston --modules=systemd-notify.so
Date: 2023-10-30 UTC
[12:17:26.567] weston 10.0.1
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
[12:17:26.568] Command line: /usr/bin/weston --modules=systemd-notify.so
[12:17:26.568] OS: Linux, 5.15.129-6.4.0-devel+git.67c3153d20ff, #1 SMP PREEMPT Wed Sep 27 12:30:36 UTC 2023, aarch64
[12:17:26.568] Flight recorder: enabled
[12:17:26.568] Using config file '/etc/xdg/weston/weston.ini'
[12:17:26.568] Output repaint window is 16 ms maximum.
[12:17:26.568] Loading module '/usr/lib/libweston-10/wayland-backend.so'
[12:17:26.568] Failed to load module: /usr/lib/libweston-10/wayland-backend.so: cannot open shared object file: No such file or directory
[12:17:26.568] fatal: failed to create compositor backend
Of course, this file exists: /usr/lib/libweston-10/wayland-backend.so
Comparing the dev and dahlia devicetrees, I don’t see any significant differences related to DSI/HDMI.
So, my question is: what could be wrong?
The HDMI over DSI converter is working fine. When I use imx8mm-verdin-wifi-dahlia.dtb (which is the same as for dev board, except for audio codec on I2C, some minor differences in UART and one USB clock) then there is no output on the HDMI (and of course, Weston is failing).
I’m just curious what Weston is looking for in the DeviceTree.
@seasoned_geek , from the thread you shared (and the thread you reference there), @jeremias.tx explained to you exactly what is going on. Your statement about the presence of a hack/security risk on U-boot related to this is certainly misguiding and unfair. In order to not hijack this thread, I sent you a private message about this, so you can explain what you mean.
I checked reference images built with Yocto, and both are working (dev and dahlia device trees).
I’m going to investigate the differences in my devicetrees. I will let you know what I will find.