From: "Karol P" <karprzy7@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: Issue running GUI application on stm32mp257 due to Vulkan error
Date: Sun, 20 Jul 2025 12:11:56 -0700 [thread overview]
Message-ID: <BkCs.1753038716632461263.NP2P@lists.yoctoproject.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]
Hi everyone, for learning purposes, I’m trying to build meta-doom ( https://github.com/JPEWdev/meta-doom ) for stm32mp257 DK. I previously tried it for RPi4 and after some minor fixes I was able to do it for nanbield/mickledore poky version. I chose those versions since meta-doom is only compatible with them. What I established it is possible to run it and it still works.
My setup for stm32mp2 version is that I cloned mickledore repo manifest and integrated meta-doom layer. Doom wouldn’t build for wayland, so I had to change my display manager to X11. It’s not directly supported but still possible (source: https://community.st.com/t5/stm32-mpus-embedded-software-and/how-to-setup-x11-in-the-distro-instead-of-wayland-on-stm32mp1/td-p/741125 )
Now gzdoom builds, and I’m able to execute on target. However, after uploading proper WAD I get this error:
>
>
>
> no vulkan device found supports minimum requirements of this application
>
>
I installed vulkan-loader and vulkan-tools into the image and vulkaninfo gives me following information:
>
>
>
> root@stm32mp25-disco:~# vulkaninfo WARNING: [Loader Message] Code 0 :
> loader_scanned_icd_add: Driver /vendor/lib/libvulkan_VSI.so.1.3.3 supports
> Vulkan 1.3, but only supports loader interface version 2. Interface
> version 5 or newer required to support this version of Vulkan (Policy
> #LDP_DRIVER_7) WARNING: [Loader Message] Code 0 :
> terminator_CreateInstance: Driver /vendor/lib/libvulkan_VSI.so.1.3.3
> supports interface version 2 but still exposes VkSurfaceKHR create/destroy
> entrypoints
>
>
I’m at a loss on what to do at this point. There seems to be some version mismatch but I can’t figure out how to solve it. And since it worked flawlessly for RPI4 I think this is some configuration related issue, but I couldn’t pinpoint it.
[-- Attachment #2: Type: text/html, Size: 2221 bytes --]
reply other threads:[~2025-07-20 19:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BkCs.1753038716632461263.NP2P@lists.yoctoproject.org \
--to=karprzy7@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.