STM32 MPUs

1. Qt6 Multimedia (PySide6) – 1080p Video Playback RequirementOur application requires smooth video playback using Qt Multimedia with PySide6 at resolutions up to 1080p.I understand that Qt6 supports hardware acceleration for 3D graphics through the GPU, but I was unable to find confirmation regarding hardware-accelerated video decoding specifically for QtMultimedia.Could you please confirm whether the STM32MP257 series supports:Hardware-accelerated video decoding at 1080pIntegration of QtMultimedia with the hardware video pipelineSupport through OpenSTLinux / Yocto2. Chromium Browser – GPU-Accelerated Video PlaybackWe also require GPU-accelerated HTML5 video playback (1080p) in the Chromium browser.Please confirm whether the STM32MP257 series provides:A Video Processing Unit (VPU) or dedicated hardware decoderGPU acceleration support within Chromium (ANGLE / EGL / GStreamer backend)Hardware-offloaded 1080p video decoding for browser playback3. Requirement Summary (for confirmation)We

Dear ST Support Team, I am seeking technical assistance for two critical issues I am encountering while developing on the STM32MP157F-DK2 (Kernel 5.10.61, Ecosystem v3.1). Issue 1: GLIBC Compatibility When running applications compiled on my host machine, I receive the error: /lib/libc.so.6: version 'GLIBC_2.34' not found. I am attempting to cross-compile using the correct SDK for Ecosystem v3.1, but I am struggling to locate the compatible toolchain/environment for my specific kernel version (5.10.61). Issue 2: Device Tree (.dts) Configuration I am unable to enable additional peripherals (specifically UART7). Despite updating the .dts file to set status = "okay", the peripheral remains disabled on the target board (verified via cat /sys/firmware/devicetree/base/soc/.../status). It appears the system is ignoring my device tree updates and defaulting to the internal bootloader configuration. Attachments:Screenshot showing the GLIBC error on the board.Screenshot of th

Following the guide for the Developer Package, it describes creating a helper script for your custom board.  Thhat works great and helps get you going. So, I generated a STM32CubeMX project and built it.  Device Tree files are generated accordingly.  STM32CubeMX gives them names of the format <device>-<stm32cubemx proj name>-mx.  These names cannot be changed as the dts files include each other.The helper script lets you set names for all these files e.g.# Name of devicetree to use # Optee dt name optee_dt_name=$your_board_name optee_dt_programmer_name=$your_board_name # U-boot dt name uboot_defconfig=${your_soc_name}_defconfig uboot_dt_name=$your_board_name uboot_programmer_dt_name=$your_board_name # TF-A dt name tfa_dt_name=$your_board_name tfa_dt_programmer_name=$your_board_name # Linux kernel dt name # linux linux_dtb_name=$your_board_nameBy default, these do not match the names generated by stm32cubemx.  Even if I change the entries to mat

Hi STM32Community,i am currently trying to build openSTLinux using the STM32CubeMX (6.17.0) generated device tree files with the yocto build process.For this I am using the STM32MPU Distribution Package. (stm32mp-openstlinux-6.6-yocto-scarthgap-mpu-v26.02.18)I set up the Distribution Package according your Wiki Installing_the_OpenSTLinux_distribution and I have set up the STM32CubeMX Project according How_to_create_your_own_machine  :I created the STM32CubeMX project directory "mx" /layers/meta-st/meta-st-stm32mp-addons and generated the project filesI created a new machine config file under /layers/meta-st/meta-st-stm32mp-addons/conf/machine, using the example stm32mp25-mx.conf as a template.I created the symlink for the EULAI modified the cubemx class accordingly under <STM32MP BSP layer addons>/classes/cubemx-stm32mp.bbclass and started the build process withsource layers/meta-st/scripts/envsetup.shbitbake st-image-core The buildprocess runs fine until it t

Following the tutorial here, when I get to the step "To generate binary to flashing via Cortex-A", the helper script fails to build when given the 'programmer' argument.  The problem appears to be incorrect configuration of the path to a device tree file.  All other steps in the tutorial build correctly using the device tree files given, just not the programmer step fails.The output is shown below.  In it you can see the following paths are supplied:EXTDT_DIR=/home/ashley/STM32MPU-Ecosystem-v6.2.0/Developer-Package/stm32mp2-openstlinux-26.02.18/sources/STM32MP215DK-AshMX EXTDT_DIR_OPTEE=CA35/DeviceTree/STM32MP215DK-AshMX/optee-osThe correct path to the dts file is ${EXT_DIR}/${EXTDIR_DIR_OPTEE}, but the path actually searched for the dts file is (refer line 58 in the log below):/home/ashley/STM32MPU-Ecosystem-v6.2.0/Developer-Package/stm32mp2-openstlinux-26.02.18/sources/STM32MP215DK-AshMX/stm32mp2/a35-td/optee/Full log is:sdk_compilation-stm32mp2-mx-my-custom-board

We have a custom stm32mp25 board. On Mickledore we were able to create a/b partitions in our machine conf doing the following:   PARTITIONS_IMAGES += "tc-appfs-a tc-appfs-b" STM32MP_TCFS_IMAGE ?= "ti-tc-appfs" STM32MP_TCFS_LABEL_A ?= "tc-appfs-a" STM32MP_TCFS_LABEL_B ?= "tc-appfs-b" STM32MP_TCFS_MOUNTPOINT ?= "/tc-apps" # Proposed value for tc-appfs is 150MB STM32MP_TCFS_SIZE ?= "153600" PARTITIONS_IMAGES[tc-appfs-a] ?= "${STM32MP_TCFS_IMAGE},${STM32MP_TCFS_LABEL_A},${STM32MP_TCFS_MOUNTPOINT},${STM32MP_TCFS_SIZE},FileSystem" PARTITIONS_IMAGES[tc-appfs-b] ?= "${STM32MP_TCFS_IMAGE},${STM32MP_TCFS_LABEL_B},${STM32MP_TCFS_MOUNTPOINT},${STM32MP_TCFS_SIZE},FileSystem" PARTITIONS_LIST += "tc-appfs-a tc-appfs-b"  However, in scarthgap this no longer works. We are getting the following error:Cannot generate FlashLayout_emmc_stm32mp257f-m670-optee.tsv file: the ti-tc-appfs-ti-linux-stm32mp25-m670.tc-appfs-a.ext4 binary for tc-appfs-a partition is missing in deplo

Hi everyone,I have recently upgraded from openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11 to openstlinux-6.6-yocto-scarthgap-mpu-v26.02.18 of the meta-st-stm32mp layer.I am using a custom board based on a STM32MP157 MPU.With the previous revision, my board booted fine but since I updated to the new version it is stuck during boot. Here are the boot logs I got after enabling the early console:Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 6.6.116 (oe-user@oe-host) (arm-oe-linux-gnueabi-gcc (GCC) 13.4.0, GNU ld (GNU Binutils) 2.42.0.20240723) #1 SMP PREEMPT Sun Nov 2 13:14:42 UTC 2025 [ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=50c5387d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: Eaton Machine [ 0.000000] earlycon: stm32 at MMIO 0x40011000 (options '115200n8') [ 0.00000

I get this issue. I don't know why the GPU and CPU is considered deferred by op-tee.I think this is a configuration issue, but I don't know what need to be done. I have tried stm32mp257f-dk device treee and it still gives the same error. Notice that I'm not using LSE.So any suggestion? Enable something in RIF?D/TC:0 0 dt_stm32_gpio_bank:1176 Bank name gpio@442b0000 D/TC:0 0 firewall_dt_controller_register:289 Registering gpio-bank-H firewall controller D/TC:0 0 dt_stm32_gpio_bank:1176 Bank name gpio@442c0000 D/TC:0 0 firewall_dt_controller_register:289 Registering gpio-bank-I firewall controller D/TC:0 0 probe_driver_node:550 element: stm32_gpio-pinctrl on node pinctrl@44240000 initialized F/TC:0 0 probe_driver_node:543 Probing stm32-rtc on node rtc@46000000 D/TC:0 0 probe_driver_node:556 element: stm32-rtc on node rtc@46000000 deferred 2 time(s) F/TC:0 0 probe_driver_node:543 Probing stm32_gpio-pinctrl on node pinctrl-z@46200000 D/TC:0 0 dt_stm32_gpio_bank:1176 Bank name gpio@46200000

Platform:SoC: STM32MP257Sensor: GC05A2 (5MP)Interface: CSI-2 Issue:I'm working on camera integration with GC05A2 on STM32MP257. The raw image quality is acceptable, but after enabling AWB and CCM in the ISP pipeline, the output image shows severe noise (both luminance and color noise), especially in low-light conditions (<300 Lux) or shadow areas.Questions:Where is the noise reduction? Does STM32MP257 ISP have built-in hardware noise reduction (2D/3D NR)? If yes, how do I enable and control it through V4L2 or the driver? 

Hello everyone,I have a custom board based on STM32MP157A (rev. Z) and I am trying to boot from emmc; I am able to boot sucessfully from SD card; I flashed the same image to the emmc with the ST MX Cube Programmer and, if get into u-boot from SD card, I am able to inspect the partitions and information of the emmc (see below), but whenever I set the boot pins to 010 I get no messages on the serial UART, while the emmc seems to be powered. STM32MP> mmc list STM32 SD/MMC: 0 (SD) STM32 SD/MMC: 1 (eMMC) STM32MP> mmc info Device: STM32 SD/MMC Manufacturer ID: 2 OEM: 544d Name: SA04G Bus Speed: 50000000 Mode: SD High Speed (50MHz) Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 3.6 GiB Bus Width: 4-bit Erase Group Size: 512 Bytes STM32MP> mmc dev 1 switch to partitions #0, OK mmc1(part 0) is current device STM32MP> mmc info Device: STM32 SD/MMC Manufacturer ID: 45 OEM: 100 Name: DG400 Bus Speed: 52000000 Mode: MMC High Speed (52MHz) Rd Block Len: 512 MMC version 5.1

STM32MP151 is a PTP slave clock, and the master clock is correctly determined and configured. In the same network, multicast, E2E, and one-step configuration modes are used. Run ptp4l，Output prompt: "Received SYNC without timestamp". the actual SYNC message of the main clock has a hardware timestamp.Other relevant information can be found in the info1. log file.STM32MP151 is the PTP slave clock IP: 192.168.1.251, the PTP master clock IP: 192.168.1.3, Captured data packet shows that the master clock has a timestamp, and the slave clock DELAY_REQ  has no timestamp.翻译搜索复制

I'd like to move from mickledore to the current ST offering on scarthgap.  We are using the STM32MP157D.We require a web browser, and WebKit worked well for us on mickledore using QT5.Since QT has been spun out to a plug-in and it is unclear how well-supported it is (ST's documentation seems lagging), I decided to go with Weston/Wayland and use a simple GTK/GDK app.Westion is working - the GPU `/usr/local/demo/bin/weston-st-egl-cube-tex` runs nicely.  Simple apps using GDK are also working.Sadly, though, the app embedding a WebKit view has a hard-to-describe random flickering issue.  It renders the page but then randomly overlays a white screen that occasionally flashes on and off. Anyone able to offer some experience:- Has anyone got a lightweight browser working on the STM32MP1 using the GPU and the recent ST scarthgap releases?- Or got QT6 working on STM32MP1.  Did you use the ST's "QT plug-in"?- Any advice for configuring webkitgtk3 (found in meta-oe)?&nbsp

I am trying to follow getting started document for X-LINUX-GNSS1At Step 4.Add a layer (recipes-gnss1).of section 5.2.1 I am getting below error.  ERROR: Layer meta-gnss1 is not compatible with the core layer which only supports these series: scarthgap (layer is compatible with mickledore)   

I would like to use MDMA on Cortex M4 to move data from DDR to SRAM in order to overcome the SRAM size limitation, especially in Ecosystem 6 secure context when a SYSRAM bank is dedicated to OPTEE.My idea is to move to DDR some data structures used by code running on Cortex M4 and, when needed by the code, to use MDMA to move such data from DDR to SRAM and then to unload such same structures from SRAM to DDR.I found that MDMA is the preferred way to move data DDR <-> SRAM, but it isn't supported by STM32 MCUs Embedded Software.https://wiki.stmicroelectronics.cn/stm32mpu/wiki/MDMA_internal_peripheral#Software_frameworks_and_driversDo you have any suggestion about how to proceed ?

Hello everyone,I'm a beginner in the STM32 world,A teacher has lent us a STM32MP157C-DK2 board (with a A7 and  a M4) for a challenge,and I am currently trying to upload a program for the MCU (a button which switches the color of a RGB LED).As I'll first describe my complete setup and what I have already done, so you can directly go to the end of the post if you want to see the main problem I'm facing which is :To "import an OpenSTLinux Project" into cubeIDE,to ultimately update the device tree of the Cortex-A7 into cubeIDE.My setup:A x64 computer running on Windows 11 with WSL 2 Ubuntu 24.04.01 LTS.The STM32MP157C-DK2 board connected to my PC with ST-LINK and by network.On WSL :I downloaded here and installed the STM32 cube IDE 2.1.0 for Debian.I downloaded here and installed the STM32 cube MX 6.17.0 for Linux.I downloaded here and installed the STM32MP1 OpenSTLinux Developer Package for x86.I turned my terminal from Dash to Bash.I added these lines to my /.bas

ST Dev team have successfully created a web browser with Qt WebEngine and deployed that into the MP257 processor.The browser has been made in kiosk mode. There is no official benchmark about that scenario.My question is how well supported is the MP257 from Qt6 WebEngine? By looking at the Qt WebEngine features https://doc.qt.io/qt-6/qtwebengine-features.html It seems that the Qt WebEngine have lots of stuff in the box. Are all features from Qt WebEngine possible to enable inside a web browser for MP257?I'm more interested in WebRTC, HTML5 DRM, Hardware acceleration, WebGL, WebSockets. DOM Extensions, Vulkan support API.This is a question about hardware, rather than software. My goal is to create optimized kiosk mode web browser of specific dynamical web pages.I'm targeting web pages such as Netflix, GeForce Now, Spotify etc. I don't have any high requirements on resolution. Max 1080p, which is supported by MP257. 

Hi Community,We are encountering an issue with the SD-Card on our STM32MP15x board. The problem is, that writing to the SD card works well but the reading does show sporadic errors.In our configuration, we use 1TB MicroSD-Cards in the DDR50 Mode. In DDR25 mode, the SD card is working fine. Unfortunately, we need the DDR50 Mode (or faster) for our product.First, let me describe the test scenario: I wrote ~500GB uint64_t ramp data in little endian byte order to a SD-Card, and verified on an external device, that the ramp data have been written correctly. A dump of the first 64 bytes looks as follows:root@gdl1-31:~# hexdump -C -n 64 /dev/mmcblk0 00000000 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 |................| 00000010 02 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 |................| 00000020 04 00 00 00 00 00 00 00 05 00 00 00 00 00 00 00 |................| 00000030 06 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 |................| 00000040In the next step, I wrote a little te

I am stuck trying to run STM32MP215DK M33 firmware examples on an (unmodified) ostl distribution I built.I went through the getting started tutorials no problems, now starting to experiment with customisation, but have got myself stuck.  Some advice would be appreciated.  This STM32MP ecosystem is quite overwhelming to the uninitiated, especially once you add in trusted firmware.As per this page, I loaded the image FlashLayout_sdcard_stm32mp215f-dk-ca35tdcid-ostl-m33-examples-optee.tsv.  I have been playing with building and debugging the various example projects for M33.When trying to alter the M33 examples, I came up against the hardware firewall.  It became clear that I was going to need M33 access to ports and peripherals that were currently allocated to the A35 core.  I still haven't worked out how to solve that yet.  But ultimately a custom kernel layer will be required, so I started looking into that.As per this page, I built the default linux

Hello,I am testing a custom board based on STM32MP257FAI3 with two DDR4 MT40A512G16And STM32DDRFW-UTIL cann't pass through PHY initialization. I found that CubeMX 6.17.0 still allows DDR A19 pin mapping, despite the pin A19 isn't assignable for both DDR3 and DDR4. (STM32CubeMX 6.12.1 released). So I've assigned BA0 signal to it on PCB. And I think this cause STM32DDRFW-UTIL to be failed.Is there any way to resolve this programmatically?

Hello,I successfully used linuxptp with stm32mp257f-dk board, but now need to do the same with stm32mp157f-dk2. linuxptp was built from the same latest sources for both boards using corresponding SDK for each board. But when ptp4l is running on stm32mp157f-dk2, debug output shows that required clock adjustments are not being applied to raw ptp clock: I tried to rebuild uImage and modules for stm32mp157f-dk2 using latest sources from v.25.08.27, but result was still the same. PTP clock is registered and is using hw timestamping according to ethtool:Time stamping parameters for end0:Capabilities:hardware-transmitsoftware-transmithardware-receivesoftware-receivesoftware-system-clockhardware-raw-clockPTP Hardware Clock: 0Hardware Transmit Timestamp Modes:offonHardware Receive Filter Modes:noneallptpv1-l4-eventptpv1-l4-syncptpv1-l4-delay-reqptpv2-l4-eventptpv2-l4-syncptpv2-l4-delay-reqptpv2-eventptpv2-syncptpv2-delay-req I'm using L2 twostep synchronization mode.Additional linuxptp deb

Hi,Can I use only M33 core as a standalone controller on stm32mp257 evaluation board without need of linux operating system and DDR

I having some issues with nvram in op-tee.I don't know what this happen. It seems that op-tee want to say to me that 0xffff0006 is TEE_ERROR_BAD_PARAMETERS. In this case, I don't use any tamper and don't have LSE.I think this is a bug because my ST TF-A and ST Op-tee assumes that LSE must be available to proceed. I made a specific hack in ST TF-A that avoids the LSE configuration to continue working. When ST TF-A was starting. It was going to enable clock ID 5, which is LSE, no matter if I have LSE disabled or enable. An if-statement solved this issue.Do you have any clue what's can be the cause of this?Processor: STM32MP257FAK F/TC:0 0 process_probe_list:657 Probe loop 6 after 4 for deferral(s) D/TC:0 0 print_probe_list:504 Probe list: 3 elements D/TC:0 0 print_probe_list:506 |- Driver stm32-gpu probes on node gpu@48280000 D/TC:0 0 print_probe_list:506 |- Driver stm32-tamp probes on node tamp@46010000 D/TC:0 0 print_probe_list:506 |- Driver stm32-cpu probes on node cpu@0 D/TC:0 0

I spotted that the documentation and code examples do not match for port pin assignments for LED2 and LED 4.The user manual manual does not match the schematics:Code examples do match the schematics, so just a documentation error I think.EDIT:  There is definitely some sort of misalignment here.  The Linux device tree (stm32mp215f-dk.dts) puts the blue LED on PZ3.  And when controlled on/off or heartbeat through Linux, the blue led labelled LD2 on the dev kit is controlled.  So this seems to match the user manual! gpio-leds { compatible = "gpio-leds"; led-blue { function = LED_FUNCTION_HEARTBEAT; color = <LED_COLOR_ID_BLUE>; gpios = <&gpioz 3 GPIO_ACTIVE_HIGH>; linux,default-trigger = "heartbeat"; default-state = "off"; }; };I can only assume the LED labelled LD4 on the dev kit is wired to pin PF10?

Dear community, I've used yocto as my workhorse in the past a lot for other processor manufacturers. Now as I'm happily joining the STM world for linux I'm stuck. Maybe it is a too easy to miss question, but which steps I have to take for putting all the needed images to the sd-card? I have followed the rules to go for using the create_sdcard_from_flashlayout.sh script with FlashLayout_sdcard_stm32mp257f-dk-optee.tsv as the parameter. After that I've used dd to flash the .raw to the designated sdcard but the board does not start at all. From the provided sdcard it starts without any issue.Where is my mistake? Regards KS

HiI'm trying to configure a camera chip (Nextchip nvp6324) that outputs mediaformat MEDIA_BUS_FMT_UYVY8_2X8.There are examples to setup IMX335 sensor to a CSI-2 interface, but how to configure this format ? BR Raimo