2024-10-06 11:59 PM - edited 2024-10-07 02:25 AM
hi
i am using stm32mp157d-dk1 and i have downloaded qt creator and i have created a simple hello world window now how to display it in the stm32mp157d-dk1?
how to set up cross compilation in order to deploy Qt projects directly from a host Linux machine to the embedded target using qtcreator.
Solved! Go to Solution.
2024-10-16 01:19 AM - edited 2024-10-16 01:22 AM
i hope i have got the steps right and for any of the steps bellow does it require internet 1.cd <working directory path>/Distribution-Package
2.repo init -u https://github.com/STMicroelectronics/oe-manifest.git -b refs/tags/openstlinux-6.1-yocto-mickledore-mpu-v24.06.26
3.repo sync
4. DISTRO=openstlinux-weston MACHINE=stm32mp15-disco source layers/meta-st/scripts/envsetup.sh
5.bitbake st-image-weston
7. cd <Distribution Package installation directory>
8.git clone -b v1.0.0 https://github.com/STMicroelectronics/meta-st-x-linux-qt.git layers/meta-st/meta-st-x-linux-qt
9. git clone -b scarthgap https://github.com/meta-qt5/meta-qt5.git layers/meta-qt5
10. source layers/meta-st/scripts/envsetup.sh
11.bitbake-layers add-layer ../layers/meta-qt5 ../layers/meta-st/meta-st-x-linux-qt
12.bitbake st-image-qt
13.bitbake st-image-qt -c populate_sdk
14.execute "xxx.sh" script available in: build-openstlinuxweston-stm32mp15-disco/tmp-glibc/deploy/sdk
15.setup qt
2024-10-07 04:55 AM
Duplicated:
2024-10-07 06:02 AM
i was downloading distribution package ,while using this command "repo init -u https://github.com/STMicroelectronics/oe-manifest.git -b refs/tags/openstlinux-6.1-yocto-mickledore-mpu-v24.06.26" i am getting error as bellow
emertxe@ubuntu:~/STM32MPU/Distribution-Package$ repo init -u https://github.com/STMicroelectronics/oe-manifest.git -b refs/tags/openstlinux-6.1-yocto-mickledore-mpu-v24.06.26
File "/home/emertxe/STM32MPU/Distribution-Package/.repo/repo/main.py", line 95
)
^
SyntaxError: invalid syntax
2024-10-08 12:40 AM
Hello @Sharan ,
I guess this is a repo tool issue, please have a look at : https://wiki.st.com/stm32mpu/wiki/PC_prerequisites.
(note: remove ".repo" directory if you do a new trail)
BR,
Philippe.
2024-10-08 12:43 AM
yes i was able to solve the repo issue by changing the shebang line but now bitbake st-image-weston requires python 3.8.0 what to do
2024-10-08 12:46 AM
you had mentioned "If you get the SDK with Developper Package and X-LINUX-Qt SDK add-on, the installation automatically configures Qt creator with the MP1 kit." but for X-LINUX-QT is for stm32mp25x lines can u use that add on for stm32mp15x lines?
2024-10-08 12:59 AM
Hello @Sharan
X-LINUX-Qt will officially supports MP1x series in a few weeks.
But with the current delivery you can compile Distribution Package for "stm32mp15-disco" MACHINE.
Then when you run application on target, please use EGLFS configuration. In Wayland configuration you might face display synchronization we have fixed in the next coming delivery.
Philippe.
2024-10-09 05:43 AM
https://barenakedembedded.com/how-to-set-up-stm32mp1-with-qt/
using this can i set up my stm with qt?
2024-10-09 05:51 AM
Hello @Sharan ,
no, please use official and updated documentation:
https://wiki.st.com/stm32mpu/wiki/X-LINUX-QT_Expansion_Package
Philippe.
2024-10-09 10:57 PM
i am getting bitbake error please help me
NOTE: Fetching uninative binary shim http://downloads.yoctoproject.org/releases/uninative/4.3/x86_64-nativesdk-libc-4.3.tar.xz;sha256sum=1c35f09a75c4096749bbe1e009df4e3968cde151424062cf4aa3ed89db22b030 (will check PREMIRRORS first)
WARNING: Your host glibc version (2.39) is newer than that in uninative (2.38). Disabling uninative so that sstate is not corrupted.
Initialising tasks: 100% |###############################################################################################################################################| Time: 0:00:11
Sstate summary: Wanted 3246 Local 0 Mirrors 0 Missed 3246 Current 0 (0% match, 0% complete)
NOTE: Executing Tasks
ERROR: PermissionError: [Errno 1] Operation not permitted
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/sharan/STM32MPU_workspace/STM32MPU-Ecosystem-v5.1.0/Distribution-Package/layers/openembedded-core/bitbake/bin/bitbake-worker", line 275, in child
bb.utils.disable_network(uid, gid)
File "/home/sharan/STM32MPU_workspace/STM32MPU-Ecosystem-v5.1.0/Distribution-Package/layers/openembedded-core/bitbake/lib/bb/utils.py", line 1693, in disable_network
with open("/proc/self/uid_map", "w") as f:
PermissionError: [Errno 1] Operation not permitted
ERROR: Task (/home/sharan/STM32MPU_workspace/STM32MPU-Ecosystem-v5.1.0/Distribution-Package/layers/openembedded-core/meta/recipes-devtools/gcc/gcc-source_12.3.bb:do_rm_work) failed with exit code '1'
ERROR: PermissionError: [Errno 1] Operation not permitted
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/sharan/STM32MPU_workspace/STM32MPU-Ecosystem-v5.1.0/Distribution-Package/layers/openembedded-core/bitbake/bin/bitbake-worker", line 275, in child
bb.utils.disable_network(uid, gid)
File "/home/sharan/STM32MPU_workspace/STM32MPU-Ecosystem-v5.1.0/Distribution-Package/layers/openembedded-core/bitbake/lib/bb/utils.py", line 1693, in disable_network
with open("/proc/self/uid_map", "w") as f:
PermissionError: [Errno 1] Operation not permitted
ERROR: Task (/home/sharan/STM32MPU_workspace/STM32MPU-Ecosystem-v5.1.0/Distribution-Package/layers/meta-st/meta-st-stm32mp/recipes-kernel/linux/linux-stm32mp_6.1.bb:do_rm_work) failed with exit code '1'
NOTE: Tasks Summary: Attempted 6 tasks of which 0 didn't need to be rerun and 2 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 3 seconds
Summary: 2 tasks failed:
/home/sharan/STM32MPU_workspace/STM32MPU-Ecosystem-v5.1.0/Distribution-Package/layers/openembedded-core/meta/recipes-devtools/gcc/gcc-source_12.3.bb:do_rm_work
/home/sharan/STM32MPU_workspace/STM32MPU-Ecosystem-v5.1.0/Distribution-Package/layers/meta-st/meta-st-stm32mp/recipes-kernel/linux/linux-stm32mp_6.1.bb:do_rm_work
Summary: There was 1 WARNING message.
Summary: There were 2 ERROR messages, returning a non-zero exit code.