• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 123 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.

PROCESSOR-SDK-AM62X: How to get tidss_dri.so in buildroot

zhaohang lai
Prodigy 130 points
Part Number: PROCESSOR-SDK-AM62X

Tool/software:

For some reason, I used the buildroot to build the rootfs, and the customer asked to use the wayland protocol and qt3dds, and I configured it to run weston, but the following questions were encountered, how should I solve it?


[19:20:01.961] weston 12.0.1
wayland.freedesktop.org
Bug reports to: gitlab.freedesktop.org/.../
Build: 12.0.1
[19:20:01.966] Command line: weston
[19:20:01.966] OS: Linux, 6.6.58-rt45+, #176 SMP PREEMPT_RT Thu Jul 3 18:09:19 CST 2025, aarch64
[19:20:01.966] Flight recorder: enabled
[19:20:01.974] Using config file '/etc/xdg/weston/weston.ini'
[19:20:01.976] Output repaint window is 7 ms maximum.
[19:20:01.978] Loading module '/usr/lib/libweston-12/drm-backend.so'
[19:20:01.996] initializing drm backend
[19:20:01.996] Trying libseat launcher...
[19:20:01.997] [libseat/libseat.c:73] Seat opened with backend 'seatd'
[19:20:01.997] [libseat/backend/seatd.c:212] Enabling seat
[19:20:01.997] libseat: session control granted
[19:20:02.000] using /dev/dri/card0
[19:20:02.000] DRM: supports atomic modesetting
[19:20:02.000] DRM: supports GBM modifiers
[19:20:02.000] DRM: supports picture aspect ratio
MESA-LOADER: failed to open tidss: /usr/lib/dri/tidss_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)
MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)
MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)
[19:20:02.059] failed to initialize egl
[19:20:02.098] fatal: failed to create compositor backend
Internal warning: debug scope 'drm-backend' has not been destroyed.

  • 0
    TI__Guru 69652 points

    Please provide exact steps to re-create this, based on our current/latest Buildroot SDK for AM62x.

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Prodigy 130 points

    Hi Andreas Dannenberg:

    I will re-create this, but if I want to install QT5, qt53d and QT5 OpenGL in Buildroot, which configurations do I need to enable? The main issue is that I don't know which options I should select in → Target packages → Graphic libraries and applications (graphic/text) → mesa3d. Also, do I need to configure additional drivers in the Linux kernel to start the GPU?Please tell me, thank you.

  • +1 in reply to zhaohang lai
    TI__Guru 69652 points

    Setting up the graphics stack to work correctly is not an easy task. I had previously discussed about your inquiry with one of our developers, and he pointed to this documentation page which is hopefully helpful:

    https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/11_01_05_03/exports/docs/linux/Foundational_Components/Graphics/Rogue/Build_Guide.html#proprietary-mesa-components

    Unfortunately we cannot provide additional guidance on this at the moment in the context of Buildroot. If you want to use Qt our currently supported approach is through our Yocto SDK.

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Prodigy 130 points

    Hi Andreas
    Understood. Additionally, I would like to make a suggestion. Since I am in China, many software sources cannot be downloaded when using the yocto SDK, which results in the inability to compile the file yocto file system. I hope that the software sources in China can be updated in the future.

  • 0 in reply to zhaohang lai
    TI__Guru 69652 points
    zhaohang lai said:
    ce I am in China, many software sources cannot be downloaded when using the yocto SDK, which results in the inability to compile the file yocto file system. I hope that the software sources in China can be updated in the future.

    Thank you for the suggestion. We are aware of such issues which impact China in a disproportional way it seems. Previously (years ago) TI actually hosted a "Yocto Source Mirror" that would be used as a fallback in cases where the original source server for a certain recipe was inaccessible, but this effort was stopped for reasons I don't know. However there's new urgency to re-start such a source mirror (or a similar solution), so I just added your feedback to the internal ticket tracking this effort (ref: SITREQ-1352) for additional perspective.

    Thanks, Andreas