Other Parts Discussed in Thread: TPS65219, TFP410
We are running the TI Processor SDK 8.0.filesystem on a custom board with a modified device tree.
We have tried 8.0.3.0.19 and 8.4.1.9 releases of the EVK filesystem.
We cannot get weston to start up. The error log is shown below. If we boot the same SD card and use the DTB for the devkit, weston starts up.
[16:23:46.273] weston 8.0.0
wayland.freedesktop.org
Bug reports to: gitlab.freedesktop.org/.../
Build: 8.0.0
[16:23:46.273] Command line: weston --tty=1
[16:23:46.273] OS: Linux, 5.10.145-g8b51d20b6e, #1 SMP PREEMPT Mon Nov 7 06:25:03 UTC 2022, aarch64
[16:23:46.274] Using config file '/etc//weston.ini'
[16:23:46.274] Output repaint window is 7 ms maximum.
[16:23:46.274] Loading module '/usr/lib/libweston-8/drm-backend.so'
[16:23:46.279] initializing drm backend
[16:23:46.280] logind: failed to get session seat
[16:23:46.280] logind: cannot setup systemd-logind helper (-61), using legacy fallback
[16:23:46.280] /dev/tty1 is already in graphics mode, is another display server running?
[16:23:46.280] fatal: drm backend should be run using weston-launch binary, or your system should provide the logind D-Bus API.
[16:23:46.280] fatal: failed to create compositor backend
Internal warning: debug scope 'drm-backend' has not been destroyed.[1]+ Done(1) weston --tty=1
The /etc/dri contents appear to indicate that the drivers are available and dmesg shows that the various out of tree drivers are loading (pvr, etc.).
Here are the modetest results:
root@am62xx-evm:~# modetest -M tidss
failed to open device 'tidss': No such file or directory
root@am62xx-evm:~# modetest
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
Can someone advise how to troubleshoot this?
At one point, the custom board had a working display, but we can no longer reproduce the behavior. We are also noting, on boot, the following text:
U-Boot SPL 2021.01-g1c0d06c606 (Nov 07 2022 - 06:22:13 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.4.7--v08.04.07 (Jolly Jellyfi')
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loading Environment from MMC... *** Warning - No MMC card found, using default environment
These warnings were not present before.
With regards,
Mike