STM32 MPUs Embedded software and solutions

Hi team, I am able to successfully use pre-build binary from this https://github.com/STMicroelectronics/STM32DDRFW-UTIL.git repo for DDR4 with stm32mp257f-evk . but the generated artifacts with stm32 header by manually compiling in stm32cubeide I am facing the issue, After flashing I am not able to enter any command in the serial monitor window. I followed the build procedure explained in the repo's README.mdAs you can see in attached image only this DDR> prompt line is printed in serial port but not accepting any input from user , when I try to enter some command it reinitialized stdin to the same DDR> prompt line.Thank you in advance...!!hoping for a quick reply. 

Hi all,I’m working with the STM32MP135DF board and trying to use a fully custom stack including Machine/Device Tree, Kernel, U-Boot, TF-A, and OP-TEE.Here’s my setup:Poky / Yocto version: kirkstone-4.0.27CubeMX version: openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11Added CubeMX generated files under: meta-st/meta-st-stm32-Addons/mx/ └── stm32mp135df-comtrol ├── kernel │ ├── Makefile │ └── stm32mp135f-stm32mp135df-comtrol-mx.dts ├── optee-os │ ├── conf.mk │ └── stm32mp135f-stm32mp135df-comtrol-mx.dts ├── tf-a │ ├── stm32mp135f-stm32mp135df-comtrol-mx.dts │ ├── stm32mp135f-stm32mp135df-comtrol-mx-fw-config.dts │ └── stm32mp13-mx.dtsi └── u-boot ├── Makefile ├── stm32mp135f-stm32mp135df-comtrol-mx.dts └── stm32mp135f-stm32mp135df-comtrol-mx-u-boot.dtsi Generated custom machine by copying stm32mp13-disco-mx.conf.sample.Successfully built the image. Problem:When I try to flash using the STM32 flashing tool Using Usb, it gets stuck after the 0x03 partition.I suspe

Hello ST Community, We are developing a product based on STM32MP151 which requires detecting what caused the device to wakeup from sleep. With this device, we are setting up 2 wakeup sources - RTC and 2 WKUP GPIOs and we have to execute specific functions in our C application based on which GPIO triggered wakeup (or if it was RTC). We are using latest openstlinux distribution package. Right now, we have no clue as to if it is even possible somehow, some help will be appreciated a lot from ST regarding this... Best Regards,Ayush Sharma

Cannot boot an m33 TA app from the RFS on a STM32mp257f-DK board running latest OpenSTLinux starter package image.Any assistance would be appreciated. Please see details and boot error below.STEPS USED:1) build a TA m33 application in STM32CubeIDE2) from PC ssh .elf file - 73551a82-b721-4e53-9c84-c962e172c8ad.elf to target dir /lib/firmware3) from PC ssh .ta file - 73551a82-b721-4e53-9c84-c962e172c8ad.ta to target dir /lib/optee_armtz/4) from target terminal invoke command: root@stm32mp2unknownunknown:/lib/firmware# echo 73551a82-b721-4e53-9c84-c962e172c8ad.elf > /sys/class/remoteproc/remoteproc0/firmware5) from target terminal invoke command: root@stm32mp2unknownunknown:/lib/firmware# echo start > /sys/class/remoteproc/remoteproc0/stateTARGET TERMIAL OUTPUT:root@stm32mp2unknownunknown:/lib/firmware# ls73551a82-b721-4e53-9c84-c962e172c8ad.elf DKfullTest_CM33.elf LICENCE.cypress_bcm4373 regulatory.db73551a82-b721-4e53-9c84-c962e172c8ad.stripped.elf LICENCE.cypress_bcm4343 brcm reg

Originally posted in MCUs forum; moved to MPUs, as STM32MP is an MPU - not an MCU.Hello Everyone,I am working with FreeRTOS on an STM32MP157CAA and configuring the CM4 core in engineering mode using CubeIDE. According to the documentation, it's necessary to select a timer other than SysTick for the HAL timebase. However, in CubeIDE, under the SYS settings in the Pinout tab, I only see SysTick available as an option.When I generate the code, I receive the following warning: WARNING:When RTOS is used, it is strongly recommended to use a HAL timebase source other than the SysTick. The HAL time base source can be changed from the Pinout tab under SYS. Despite this, I am unable to select any other timebase source besides SysTick.Could anyone provide guidance on how to configure a different HAL timebase source for FreeRTOS in this setup? Any advice or workaround would be greatly appreciated.Thank you!

Hi, we are trying to enable secure boot on a custom board using STM32MP157C.We are using OpenSTLinux ecosystem v5en.SDK-x86_64-stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21.tar.gzen.sources-stm32mp1-openstlinux-6.1-yocto-mickledore-mp1-v23.06.21.tar.gzWhat we already did:Generated keys using STM32_KeyGen_CLI.exe (publicKeyhash.bin, publicKey.pem, privateKey.pem)Write publicKeyhash.bin to OTP using STM32_Programmer_CLI.exeSign the TF-A (BL2) image(.stm32 file) using STM32_SigningTool_CLI.exeVerify it worked by getting serial output when booting "NOTICE: Bootrom authentication succeeded"Next step was embedding certificates in the FIP binary. Until then we built the FIP binary using Makefile.sdk in sources\arm-ostl-linux-gnueabi\tf-a-stm32mp-v2.8.6-stm32mp-r1-r0. If we understand the documentation correctly (https://wiki.st.com/stm32mpu-ecosystem-v5/wiki/TF-A_BL2_Trusted_Board_Boot) generating a FIP with all certificates has to be done usi

 Description:When attempting to compile a GStreamer "Hello World" example (basic-tutorial-1.c) using the cross-compiler toolchain on STM32MP1 with OpenSTLinux, a fatal error occurs indicating that the limits.h header file is missing.https://gstreamer.freedesktop.org/documentation/tutorials/basic/hello-world.html?gi-language=c Steps to Reproduce:Source the environment setup script: source /opt/st/stm32mp1/5.0.3-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi Check the cross-compiler: echo $CC arm-ostl-linux-gnueabi-gcc -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64 --sysroot=/opt/st/stm32mp1/5.0.3-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06/sysroots/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi Attempt to compile the program: arm-ostl-linux-gnueabi-gcc -Wall basic-tutorial-1.c -o helloworld $(pkg-config --cflags --libs gstreamer-1.0) Error Message:/opt/st/

Hello, I'm currently testing the security features of OP-TEE and need to use the HUK function of SAES(CFG_STM32_SAES ?= y). However, I've found that after enabling OP-TEE, the optee-examples cannot run. May I ask what could be the reason for this? optee_example_secure_storage Prepare session with the TA E/LD: copy_section_headers:1124 sys_copy_from_ta_bin E/TC:? 1 ldelf_init_with_ldelf:152 ldelf failed with res: 0xffff0008 optee_example_secure_storage: TEEC_Opensession failed with code 0xffff0008 origin 0x3ST OpenSTLinux - Weston - (A Yocto Project Based Distro) 5.0.3-snapshot   linux6.6.48

Hi,We are using a display with the Sitronix ST7701S IC. We received the initialization parameters from the vendor and updated our display driver accordingly. After these changes, the psplash screen appears correctly when the driver loads from kernel. However, once psplash exits and Weston starts, the display goes blank and nothing is shown.We are using custom image with custom board with mickeldore yocto branch .Regards,Adnan

Hello everyone,I am currently using the ADV7280A-M with an STM32MP2 YOCTO system. I found the related driver adv7180.c and successfully loaded the driver. Following the instructions in [1], I conducted tests, but I keep encountering the following errors, or the process gets stuck at "New Clock: GstSystemClock". I would like to ask if anyone has experienced similar issues?Below is the output from running the gst-launch command:media-ctl -d platform:48030000.dcmipp -r media-ctl -d platform:48030000.dcmipp -l '"48020000.csi":1->"dcmipp_input":0[1]' media-ctl -d platform:48030000.dcmipp -l "'dcmipp_input':2->'dcmipp_main_isp':0[1]" media-ctl -d platform:48030000.dcmipp --set-v4l2 "'adv7180 2-0021':0[fmt:UYVY8_1X16/720x480]" media-ctl -d platform:48030000.dcmipp --set-v4l2 "'48020000.csi':1[fmt:UYVY8_1X16/720x480]" media-ctl -d platform:48030000.dcmipp --set-v4l2 "'dcmipp_input':2[fmt:UYVY8_1X16/720x480 field:none]" media-ctl -d platform:48030000.dcmipp --set-v4l2 "'dcmipp_main_isp':1

Hello everyone,I'm trying to build X-LINUX-AI, but I'm running into some errors. I'd be grateful for any help with fixing them. Here’s an example of the error message:../git/touch-event-gtk-player/meson.build:25:18: ERROR: Dependency "gstreamer-wayland-1.0" not found, tried pkgconfig Here is my build environment:- Ubuntu 20.04 (wsl)- OpenSTLinux Distribution Package V6.1.1- X-LINUX-AI V6.1.1 Here are the steps I followed:(Installing the OpenSTLinux distribution)$ repo init -u https://github.com/STMicroelectronics/oe-manifest -b refs/tags/openstlinux-6.6-yocto-scarthgap-mpu-v25.08.27$ repo sync(Install X-LINUX-AI environment)$ cd layers/meta-st/$ git clone https://github.com/STMicroelectronics/meta-st-x-linux-ai.git -b v6.1.1$ cd ../..$ DISTRO=openstlinux-weston MACHINE=stm32mp2 BSP_DEPENDENCY='layers/meta-st/meta-st-x-linux-ai' source layers/meta-st/scripts/envsetup.sh(build the image)$ bitbake st-image-ai Here is the resulting log:$ bitbake st-image-ai NOTE: Starte

I'm trying to perform ADC using PA3 (adc1_in15) and PF11(adc1_in2) pins of stm32mp157c-ev1 board but I keep getting "stm32-adc adc@0: Failed to enable vreg: -110"In arch/arm/dts/stm32mp157c-ev1-u-boot.dtsi I added the following:&adc {    /* ANA0, ANA1 are dedicated pins and don't need pinctrl: only in6. */    pinctrl-0 = <&adc1_ain_pins_a>;    pinctrl-names = "default";    vdd-supply = <&vdd>;    vdda-supply = <&vdda>;    vref-supply = <&vdda>;    status = "okay";    adc1: adc@0 {         status = "okay";         /delete-node/ channel@0;        /delete-node/ channel@1;        /delete-node/ channel@6;         channel@2 {             reg = <2>;             /* 16.5 ck_cycles samp

Hi.I'm trying to develop some SW on the M4 core of STM32MP157FAD1 on custom board with custom Linux.After 2 days of fighting I'm finally able to run the tty echo example on it.But I still struggle with connection to the board.Why CubeIDE Debugger requires Serial port?We have the SSH accessible through the USB ETH over IP, that should be enough.The Debugger resolve wrongly IP of the board:We have pppd interface in the Linux. The debugger wrongly detects it's IP as the debugger IP.It results with this error:I'm also getting this error in console, it looks like the script/commands are interpreted wrongly:I'm still not able to get the ST-Link to work. It always ends with this error: Thank youP.S.For others who also struggle to get it to work, check your device tree, CubeMX doesn't generate proper mbox m4_rproc. Add to end of the dts to the user section this:&m4_rproc { mboxes = <&ipcc 0>, <&ipcc 1>, <&ipcc 2>, <&ipcc 3>; mbox-names =

Hello. I am using LVGL to open a USB camera and capture NV12 640*512 video at 30fps.I want to compress NV12 video to H264 using /dev/video1 hantro-vpu stm32mp-venc-enc and save the video to /mnt/sdcard/video.h264.I'm trying to configure /dev/video1 by looking at the kernel driver's stm32mp25_vpu_hw.c, but I can't seem to get it to set up.Below is the source section that has been set.typedef struct {    int fd;    FILE *outfile;    void *out_buf[2];         void *in_buf_y[2];        void *in_buf_uv[2];       size_t in_len_y[2];       size_t in_len_uv[2];      size_t out_len[2];        int width;    int height;} hantro_enc_t;void enc_close(hantro_enc_t *enc){    if (!enc) return;    for (int i = 0; i < 2; i++){        if (enc->out_buf[i]) munmap(enc->out_buf[i], enc->out_len[i]);  &nb

stm32mp251.dtsist,stm32-timers.yamlpinctrl-stm32mp257.cThis is the current implementation of the `panel_lvds_backlight`, i'm trying to implement the pwn brightness control for this.{ /* https://github.com/STMicroelectronics/linux/blob/f01241fb/arch/arm64/boot/dts/st/stm32mp257f-ev1.dts */ .... panel_lvds_backlight: panel-lvds-backlight { compatible = "gpio-backlight"; gpios = <&gpioi 5 GPIO_ACTIVE_HIGH>; default-on; default-brightness-level = <1>; status = "okay"; }; .... } /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/input/input.h> #include <dt-bindings/pinctrl/stm32-pinfunc.h> /* This is required by fragment@3 for pinctrl */ / { compatible = "st,stm32mp257f-ev1"; /* Modify panel timing clock frequency */ fragment@0 { target = <&panel_lvds>; __overlay__ { panel-timing { clock-frequency = <54000000>; }; }; }; /* Replace GPIO backlight with PWM backlight */ fragment@1 { t

According to the datasheet of STM32MP2, it can play 1080p by using Gstreamer: GStreamer overview - stm32mpuQuestions:1. Does that mean it can play pre-downloaded videos on STM32MP2 in 1080p?2. Will Gstreamer be the only option to play 1080p videos?3. If I have a webpage that streaming 1080p real time live action from a camera, e.g inside a facility. If I want to access that web page, would it be possible to watch that live session in 1080p by using Gstreamer or other software that can handle hardware acceleration? I don't know if Chromium can handle the hardware acceleration of the GPU of STM32MP2 yet. Please, let me know. 

Hi ST Community,I'm working with a custom board based on the STM32MP257F and using the stm32mp257f-ev1.dts as the base device tree for development.After flashing the firmware and booting the board, I'm encountering a DDR initialization failure during the BL2 stage. Here's a snippet from the boot log (via UART, Docklight):ERROR: ddrphy_phyinit_usercustom_g_waitfwdone Training has failed.ERROR: DDR PHY init: Error -1 BACKTRACE: START: stm32mp2_ddr_initPANIC at PC : 0x0000000000e01f9fcThe specific error seems related to DDR PHY training failure:ERROR: ddrphy_phyinit_usercustom_g_waitfwdone Training has failed.We're using DDR4 2x16Gbits @ 1200MHz as indicated in the log:and attached a image of boot log and the error what we are getting while booting with custom board, but boots successfully with stm32mp257f-ev1.i performed the DDR utility test on the custom board , the image of ddr test report  also attached for you reference how can i rectify this issue

Hi,I’m planning to use OpenSTLinux for an upcoming project and would like to confirm whether it supports Wi-Fi Direct functionality. Additionally, I would greatly appreciate any references, application note or technical documentation detailing the implementation and operation of Wi-Fi Direct within the OpenSTLinux framework. Thank you so much in advance. 

Hello,I am currently using the DDR Utility in STM32CubeProgrammer to tune the DDR4 on my STM32MP257F-EV1 board.I would like to perform infinite read and write tests on DDR to check the stability over time.From the documentation, I found that there is a flag called TEST_INFINITE_ENABLE that can be defined in the project to enable infinite testing.Could someone please clarify:Where exactly should I define this TEST_INFINITE_ENABLE flag (e.g., in ddr_tests.c or as a project preprocessor define)?How can I start and stop the infinite test when using the DDR Utility or STM32CubeIDE debugger?Are there any example scripts or recommended settings for long-duration DDR stress testing?Thanks in advance for your support

Hello,on a stm32mp257f-ev1 board I'm developing a non secure M33 firmware using hpdma3.I configured hpdma3 on optee RIF DT to be used only by M33 (CID2) for all channels as follow&hpdma3 { st,protreg = < RIFPROT(RIF_HPDMA_CHANNEL(0), RIF_UNUSED, RIF_UNLOCK, RIF_NSEC, RIF_NPRIV, RIF_CID2, RIF_SEM_DIS, RIF_CFEN) ......................................................................................... ......................................................................................... RIFPROT(RIF_HPDMA_CHANNEL(15), RIF_UNUSED, RIF_UNLOCK, RIF_NSEC, RIF_NPRIV, RIF_CID2, RIF_SEM_DIS, RIF_CFEN) >; };When I debug the firmware on CubeIDE if I try to inspect HPDMA3 registers using "SFRs" tab I get on linux console iac exceptions of this type: E/TC:0 stm32_iac_itr:192 IAC exceptions [159:128]: 0x200000 E/TC:0 stm32_iac_itr:197 IAC exception ID: 149 E/TC:1 stm32_iac_itr:192 IAC exceptions [159:128]: 0x10000000 E/TC:1 stm32_iac_itr:197 IAC exception ID: 156 E/TC:1 stm32_i

I want to install the codesys linux SL runtime on a STM32MP157-DK2.Dynamic libraries needed by the CODESYS Control Runtime binary:libm.so.6libpthread.so.0libdl.so.2librt.so.1libc.so.6libgcc_s.so.1Third-party requirements: - libc >= 2.27 (required by CodeMeter Runtime)Is it possible to install this on OpenSTLinux ?

I am trying to decrease the DDR Clock Frequency for STM32MP257F-DK board. I used STM32CubeMX Tool to change clock tree and generate the modified device trees and made the required changes, compiled and flashed, but still the ddr clock remains the same. My question is:1. What are the changes to be done to change the ddr clock frequency and if i am following the right path or not?2. Are there any user space commands I can use to do so?

Hi Team,We are planning to use STM32MP235A for an IP PTZ camera application. Do we have an example code for the same? If yes, kindly share the links to relevant resources.Thanks,Preethi

Hi everyone,I have the STM32MP257F-DK development kit and I'm interested in flashing or building Android OS for it. So far, I've found some resources and guides for the STM32MP257F-EV1, but nothing specifically for the DK variant.From what I understand:The EV1 board is more feature-rich and used as a reference platform.The DK (Discovery Kit) is more compact and may have differences in peripherals or memory layout.My Questions:Is Android (AOSP) officially supported on the STM32MP257F-DK?If not officially supported yet, is there a known working method to port or build Android for it manually?Can I reuse the EV1 build instructions or BSP with some modifications for the DK?Any guidance, links, or shared experience from others who tried Android on the -DK board would be greatly appreciated. I'm comfortable with building U-Boot, TF-A, Linux kernel, and AOSP — just need to know if this effort is currently feasible or if I’m hitting an early-adopter wall.Thanks in advance!

... in order to make a "Hello World" and be able to use it for more applications? Based on the steps of the ST wiki on the stm32mp257f-dk through a VirtualBox to be able to use Linux and configure the A35, we realized that when performing the last steps of the wiki on the M33 we get connection errors with the board. That is why we have not been able to use the M33 independently. Because of this, we want to know how to make the connection between both microprocessors and thus have the possibility of configuring the M33 and being able to give it more uses.