Greetings @lisandropm,
I don’t see anything obvious in your recipe that could lead to this issue. Though it’s hard to predict every change on the yocto level just looking at the recipe itself. What might help is taking the manifest from your custom build with the list of all the installed packages and comparing it to the default manifest list for tdx-reference-multimedia-image.
Perhaps this would help you notice a difference in packages being installed that might be related to the issue you’re seeing.
Another thing I noticed is that in your Weston logs this line:
[17:56:09.881] Failed to load module: /usr/lib/libweston-10/wayland-backend.so: cannot open shared object file: No such file or directory
First of all, does this file actually exist or not in your filesystem?
If yes, then I found another thread on our community where another customer got the same message: Weston not starting on Verdin Dahlia
If you see the answer in this thread, it turns out the customer did some device tree changes that caused the DRM subsystem to not initialize correctly. Did you do any device tree changes in addition to your custom image?
If no, then can you confirm the DRM subsystem is even initialized in your system? Try checking dmesg for any troubling logs related to DRM or similar.
Best Regards,
Jeremias