Showing results for 
Search instead for 
Did you mean: 

Qt 5 (5.14.2) imports from adobe XD stm32mp151

Associate II

As the title describes, for my project which is based on an stm32mp151 embedded device, we are needing to import in Adobe XD generated .xd files into Qt design studio however, currently board packages only provide support up to v5.14.2. There may be considerable effort in getting more recent packages (Qt6).

Is there a way to get qt bridge files imported into Qt 5.14.2? Or is this just flat-out not supported?

If this isn't possible and we are forced into using more recent versions of Qt (Qt 6.7 etc.), how well supported is this currently in stm32mp151 mpu yocto builds?

Looking for a way forward on this.

Regards and thanks in advance.

ST Employee

Hello @joshd ,


Unfortunately neither Qt5 nor Qt6 imports are supported by ST.
Do you have some issues regarding the yocto build itself?


David B.

Hi @DBELL.1 , 

Though ST does support the packages for Qt 5.14.2 as that is what the BSP comes with as I have found.

Would it be difficult to build in the necessary support for Qt 6.7.0?


I have not yet started venturing down this path.

Hello Joshua,

I don't know much about importing Qt bridge files with Qt5 or Qt6, so please ask Qt support for this.

But if you need to move to Qt6 on STM32MP157 this should not require too much effort. I have only made the exercise on our next MP2 generation, and task is mainly to replace Qt5 reference by Qt6 in Yocto setup:

- meta-qt5 layer to be replaced by meta-qt6 layer

- in meta-st/meta-st-openstlinux layer: change files name or reference to Qt6

There is no need to dig into BSP.

But please consider there is no official support from STM for Qt6 on STM32MP157, so you will have to do it by yourself.



Hello PPAGE.13,

Thanks for your response. We are using an STM32MP151, not a STM32MP157 but I imagine this should be almost identical in approach. It may be possible for us to continue on QT5 for now so this may be a non-issue.


Currently I have been facing issues trying to display example QT applications on our display panel (which is proven to be working). Sorry if this should be in another post.

We can use a command like this to display an image:


gst-launch-1.0 filesrc location=/mnt/sda1/test-image.png ! pngdec ! videoconvert ! imagefreeze ! kmssink driver-name=stm


The application can be built and run on the host machine just fine. It cross-compiles without error for the target.

I have these variables set:


export QT_LOGGING_RULES=qt.qpa.egldeviceintegration=true
export QT_LOGGING_RULES=qt.qpa.eglfs.kms=true
export EGL_LOG_LEVEL=debug
export MESA_DEBUG=1
export LIBGL_DEBUG=1


and my /usr/share/qt5/cursor.json file looks like this:


 "device": "/dev/dri/card0",
 "outputs": [
   { "name": "DPI-1", "mode": "800x480", "size": "800x480" }
 "hwcursor": false,
 "pbuffers": true


Log output returns this




I can just give you some clue to run a simple test that works with kmssink on regular Weston build:

systemctl stop weston-graphical-session.service

gst-launch-1.0 videotestsrc ! kmssink driver-name=stm