Can't run st-example-image-qt QT examples on a custom board based on STM32MP153C with RGB panel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-12-02 9:54 AM
I'm trying to run QT examples on a build created using st-example-image-qt (Ecosystem v2.1) on our custom board. We have a simple RGB display 800x480 resolution, so I modified the cursor.json on the board as follows
{
"device": "/dev/dri/card0",
"outputs": [
{ "name": "DPI1", "mode": "800x480", "size": "800x480" }
],
"hwcursor": false
But when I try to run any QT example I get the following error
root@stm32mp1-midmark:/usr/share# psplash-drm-quit
root@stm32mp1-midmark:/usr/share# export QT_QPA_EGLFS_ALWAYS_SET_MODE="1"
root@stm32mp1-midmark:/usr/share# examples/opengl/hellowindow/hellowindow
[ 1] Failed to open device: No such file or directory, Try again...
[ 2] Failed to open device: No such file or directory, Try again...
[ 3] Failed to open device: No such file or directory, Try again...
[ 4] Failed to open device: No such file or directory, Try again...
[ 5] _OpenDevice(1086): FATAL: Failed to open device, errno=No such file or directory.
[ 6] Failed to open device: No such file or directory, Try again...
[ 7] Failed to open device: No such file or directory, Try again...
[ 8] Failed to open device: No such file or directory, Try again...
[ 9] Failed to open device: No such file or directory, Try again...
[ 10] _OpenDevice(1086): FATAL: Failed to open device, errno=No such file or directory.
root@stm32mp1-midmark:/usr/share#
What do I need to do to run QT examples on a simple RGB panel?
Thanks.
Solved! Go to Solution.
- Labels:
-
STM32MP15 Lines
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-12-16 8:10 AM
Hi,
For reference for anyone interested.
Issue was due to dependances of QT with GPU ... not present on MP153.
To make it work, follow the sequence in :
https://wiki.st.com/stm32mpu/wiki/How_to_build_and_use_an_SDK_for_QT#QT_image_and_SDK_with_EGLFS
but DO NOT ACCEPT EULA !!!
Without EULA the vivante driver and the associated libraries are not built.
The "mesa" package is installed in place of vivante's stuff.
Mesa is able to deal with GPU-less devices.
The example
/usr/share/examples/opengl/hellowindow/hellowindow
works fine. Slow because fully SW emulated, but it works!
Olivier
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-12-09 8:36 AM
Hi @NBhat.1​ ,
Same issue has already been enter by our local FAE.
We will first answer by this thread.
Olivier
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-12-16 8:10 AM
Hi,
For reference for anyone interested.
Issue was due to dependances of QT with GPU ... not present on MP153.
To make it work, follow the sequence in :
https://wiki.st.com/stm32mpu/wiki/How_to_build_and_use_an_SDK_for_QT#QT_image_and_SDK_with_EGLFS
but DO NOT ACCEPT EULA !!!
Without EULA the vivante driver and the associated libraries are not built.
The "mesa" package is installed in place of vivante's stuff.
Mesa is able to deal with GPU-less devices.
The example
/usr/share/examples/opengl/hellowindow/hellowindow
works fine. Slow because fully SW emulated, but it works!
Olivier
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-04-15 3:07 AM
In my case it seems Qt is trying to run on /dev/fb0 which is not defined, instead of /dev/dri/card0
Any ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-08-09 1:33 AM
seems that your default platform is linuxfb
QT_QPA_PLATFORM=eglfs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-04-21 8:53 PM
Would this also be relevant to the stm32mp151 as well?
