Ask questions and find answers on STM32 microprocessors and dedicated embedded software solutions, such as Yocto SDK, Qt, and OP-TEE.
Most recent activity
HelloI am working on the multi-system in STM32MP257-EV board, I had modified the tsv file to prepare a double system A and B. If using the default metadata.bin file, the A system will be run always. Now I want the B system to be run, I need to modify the metadata.bin file, for example change the "accepted" of B bank to false:If the status of img_0_bank_1 is trial, the B bank system will be run when ev board power up, isn't it?how to modify the metadata.bin?If the status of img_0_bank_1 has been modified to trial, and the B bank system run up normally, is the status of img_0_bank_1 modified automatically by linux? how does the linux system modify the metadata.bin file?
Hello,I want to use a virtual keyboard on STM32MP257 now. Due to the possibility of porting some non Qt applications in the future, it is advisable to avoid using Qt's built-in virtual keyboard as much as possible. Do you have any ideas.My main application requires the use of Wayland2. We plan to port non Qt applications in the future3. What virtual keyboard scheme is used in the facerecognition example?https://wiki.stmicroelectronics.cn/stm32mpu/nsfr_img_auth.php/0/06/Cpp_ovx_face_recognition_application_enrollment.png
Hello We are currently working on reading NOR Flash(MT25QL128) device ID through OSPI interface on our custom board with STM32MP257D processor. During our testing, we observed an issue where no data appears to be written into the OCTOSPI Data Register (OCTOSPI_DR), even though we can see signals on the data lines of the NOR Flash chip. Thanks & RegardsAkshitha Pattem
Hi all,Following the guide at https://wiki.st.com/stm32mpu/index.php/How_to_create_your_own_machine, I generated Device Tree .dts files using STM32CubeMX (version 6.14.1) for the STM32MP257F-EV1 board (selected via Board Selector) in a project named demo, aiming to use a custom device tree setup.In CubeMX, I set the project location to:/Distribution-Package/layers/meta-st/meta-st-stm32mp-addons/mx(I manually created the mx folder beforehand.)This resulted in the expected output files being generated under:Distribution-Package/layers/meta-st/meta-st-stm32mp-addons/mx/demo ├── CA35 │ ├── DeviceTree │ │ └── demo │ │ ├── kernel │ │ │ ├── Makefile │ │ │ ├── stm32mp257f-demo-mx.dts │ │ │ └── stm32mp257f-demo-mx-resmem.dtsi │ │ ├── optee-os │ │ │ ├── conf.mk │ │ │ ├── stm32mp257f-demo-mx.dts │ │ │ ├── stm32mp257f-demo-mx-rcc.dtsi │ │ │ ├── stm32mp257f-demo-mx-resmem.dtsi │ │ │ └── stm32mp257f-demo-mx-rif.dtsi │ │ ├── tf-a │ │ │ ├── stm32mp257f-demo-mx.dts │ │ │ ├── stm32mp257f-demo-mx-fw-conf
Hi I am currently working with an STM32MP135F-DK development board. My goal is to compile and execute a simple C program on this board.While I have successfully booted the board and updated the operating system using my laptop, I am finding it difficult to locate a clear, step-by-step guide that explains how to compile and run a C program (for example, a basic "Hello, World!" program) on the STM32MP135F-DK from the very beginning.Could you please point me towards any helpful articles, tutorials, or resources that detail this process? Any assistance you can provide would be greatly appreciated.Thank you for your time and consideration.RegardsGirish
how to configure the device tree(gpios,timers and other peripheras) of STM32MP257F-EV1 for yacto build custom linux ,core-image-full-cmdline
Dear ST Developer Support,I am currently developing in a bare-metal environment on the STM32MP257F-EV1. I’ve encountered an issue where I am unable to write to RAM or flash memory."Despite using STM32CubeIDE (with ST-Link), memory access to RAM and flash fails, and the binary does not run as expected, even on the Cortex-M33 core."Could you please advise whether it is possible to write and execute a binary directly on the Cortex-M33 core, either using STM32CubeIDE or through other methods? Are there specific initialization steps or boot configurations required for bare-metal development on this platform?Alternatively, is development on this board only supported through OpenSTLinux? Thank you for your support.Best regards,Dahun
Hi all,I'm currently looking to get Trusted Firmware-M (TF-M) running on the Cortex-M33 core of an STM32MP257F-DK board. But I couldn't find an example for it.My plan is to adapt the existing TF-M port for the STM32MP257F-EV1 board as a reference. I'm specifically looking at the STMicroelectronics' TF-M GitHub repository https://github.com/STMicroelectronics/trusted-firmware-m/tree/v1.7.0-stm32mp25-w2441 (platform/ext/target/stm/stm32mp257f_ev1).I understand the DK board has some hardware differences from the EV1, particularly concerning the flash memory available to the M33 (the EV1 has S-NOR, while the DK product page mentions a "Macronix OctaFlash," which I assume is an OctoSPI NOR).Could anyone share any resources or general advice for when porting TF-M to the STM32MP257F-DK?
Hi,I have enabled iwdg2 in tf-a, uboot (PV="v2023.10-stm32mp-r1") , optee (version 4.0.0-stm32mp) and linux kernel(ver. v6.6-stm32mp) device trees for STM32MP133F. iwdg is enabled in non-secure world only.&iwdg2 { status = "okay"; /* USER CODE BEGIN iwdg2 */ timeout-sec = <60>; /* USER CODE END iwdg2 */ };When stopping in u-boot there are 2 scenarios that manifest as watchdog caused reset.1. First scenario is when the system is just stopped and inactive in u-boot.2. Second scenario is when running mtest in u-boot. (mtest writes and reads to addresses from 0xc0000000 to 0xc4000000; excluding the end address) With op-tee watchdog reset there is Panic stack unwind:E/TC:0 Panic 'Watchdog' at /usr/src/debug/optee-os-stm32mp/4.0.0-stm32mp-r1/core/drivers/stm32_iwdg.c:228 <stm32_iwdg_it_handler> E/TC:0 TEE load address @ 0xce000000 E/TC:0 Call stack: E/TC:0 0xce00a1d4 print_kernel_stack at /usr/src/debug/optee-os-stm32mp/4.0.0-stm32mp-r1/core/arch/arm/ker
Hi ST community!I am porting our Yocto bsp to the latest st scarthgap (openstlinux-6.6-yocto-scarthgap-mpu-v25.03.19) for our custom modules based on a stm32mp157c. When I source the Yocto SDK, the error is shown: [SDK ERROR] Issue to optee export-user_ta directory My main issue is that I cannot recompile optee (4.0.0-stm32mp-r1.2) outside of yocto: make PLATFORM=stm32mp1 CFG_EMBED_DTB_SOURCE_FILE=<our-devkit>.dts CFG_TEE_CORE_LOG_LEVEL=2 O=build all ... arm-poky-linux-gnueabi-ld.bfd: cannot find libgcc.a: No such file or directory I have tried to pass the sysroot on the command line (CFLAGS, LDFLAGS, ...) but nothing worked!What is missing during the SDK build?Is there a way to fix this temporarly on the command line?Thanks for the pointers!
I am conducting tests related to ThreadX using the 135 DK as a reference. I'm applying ThreadX-related content through Cube and testing it, but the thread doesn't exit from tx_thread_sleep. I've compared with the demo source and even followed the steps to register Tim6, but the problem persists. Is there a solution to this issue? I hope this helps! Let me know if you need further assistance.
Hello everybody,For the past few days I am trying to setup up an external codec with STM32MP257F-EV1 dev board. The codec of choice is the Cirrus CS47L35 and I can find a driver for in in OpenSTLinux.With my STM32MP25 and SAI2 interface I want to operate in Master Mode with Clock-Out. Right now I only need to read data so the SAI2B is configured as synchronous slave for SAI2A. There is additional codec's I2C configuration interface which will be accessed by i2c8 peripherial. I've already identified needed pins and generated device tree:{ // root sound: sound { compatible = "audio-graph-card"; label = "CS47L35 audio-graph card"; routing = "Playback" , "mclk1", "Capture" , "mclk1"; dais = <&sai2b_port>; status = "okay"; }; sai2a_pins_mx: sai2a_mx-0 { pins { pinmux = <STM32_PINMUX('J', 3, AF3)>, /* SAI2_FS_A */ <STM32_PINMUX('J', 11, AF3)>, /* SAI2_SCK_A */ <STM32_PINMUX('J', 12, AF3)>, /* SAI2_SD_A */ <STM32_PINMUX('J', 13, AF3)>; /* SAI2_
Hi,we are realizing a project in which we show a splashscreen image during startup. This is done in uboot with the command "bmp display" by using the simple-panel and simple-framebuffer driver.This works fine until the kernel starts up to a certain point. Then the screen is cleared and moves to black until the kernel startup reaches a point by when psplash takes over the display output again. This "gap" between these two splash screen outputs is about 3 to 4 seconds. This dark display during startup doesn't look nice. So, I am asking if the is a method to leave the U-Boot splash screen completely active until the kernel DRM or the application is ready to take over the output.Is there anyone who has dealt with a similar problem and has an idea to solve this? Following is given:- STM32MP157- display is attached to LTDC- Kernel 5.4.56- U-Boot 2020-1 Best regards, HAL9000
stm32mp2-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06.tar-gz from ECO 6.0 and only enabling the USB gadget drivers in .config, rebuilding the kernel and modules The board freezes : 1. When the gadget driver is loaded and USB cable to host is plugged in 2. When the gadget driver is loaded w/o USB cable plugged in, the gadget is loaded and board does not freezen When plugging in the USB cable to the host, the board freezes. Another vendor's 64 bit ARM board with kernel 6.6.xx does not freeze. Is there anything to debug with the device tree or otherwise to find the reason for lock up ?
Hi there,We are trying to porting the linux driver of STM32MP257F-DK + CYW55572 based on kernel 6.6.48.The ST Linux SDK kernel 6.6.48 is from https://www.st.com/en/embedded-software/stm32mp2dev.html#The target board image on eMMC is from https://wiki.st.com/stm32mpu/wiki/STM32MP25_Discovery_kits_-_Starter_Package#step3The generated 6.6.48 driver(patched) 3 ko files as the attachment but found the errors as below.insmod ./cfg80211.ko[17917.220084] module cfg80211: .gnu.linkonce.this_module section size must match the kernel's built struct module size at run timeinsmod: ERROR: could not insert module cfg80211.ko: Invalid module formatinsmod ./brcmutil.ko[17998.345277] module brcmutil: .gnu.linkonce.this_module section size must match the kernel's built struct module size at run timeinsmod: ERROR: could not insert module ./brcmutil.ko: Invalid module formatinsmod ./brcmfmac.ko[18031.322200] module brcmfmac: .gnu.linkonce.this_module section size must match the kernel's built s
Hi,I wanted to know if it's possible to read the raw mipi-dsi data dump from the Linux kernel in the STM32MP157DAC board.Thanks,
Hi,I'm trying to change the HDMI output resolution of my STM32MP157F-DK2 board to support a BOE 13.3" Mono IPS LCD (connected via LT6711A HDMI to eDP bridge).What I’ve done so far:Extracted and edited the device tree source:Decompiled stm32mp157f-dk2.dtb using dtc -I dtb -O dts.Modified display-timings node to match my panel:dtsCopyEdittiming0: timing0 { clock-frequency = <74250000>; // or appropriate pixel clock hactive = <1280>; vactive = <720>; hfront-porch = <110>; hback-porch = <220>; hsync-len = <40>; vfront-porch = <5>; vback-porch = <20>; vsync-len = <5>; hsync-active = <0>; vsync-active = <0>; de-active = <1>; pixelclk-active = <0>; }; Recompiled the DTS to DTB:Used: dtc -I dts -O dtb -o stm32mp157f-dk2.dtb stm32mp157f.dtsReplaced DTB on SD card:Mounted bootfs partition.Copied new stm32mp157f-dk2.dtb to /bootfs/Updated extlinux.conf:Ensured that FDT /stm32mp157f-dk2.dtb is set correctly in:bash
HelloWe are testing Memory read and Write in STM32MP257F-DK Board. We are not able to read or write into SRAM1 & SRAM2, but RETRAM and SYSRAM Works. We have enabled SRAM1EN & SRAM2EN in RCC_SRAM1CFGR & RCC_SRAM2CFGR respectively, but read and write of memory doesn't work. Thanks & RegardsAkshitha Pattem
Hi,We have a custom carrier board based on STM32MP157DAC. We have built a custom yocto image.Yocto Version: MickledoreMachine: stm32mp15-discoSoM: STM32MP157DACDistro: openstlinux-westonLinux Kernel: 6.1.82-stm32mp-r2-r0I was able to get a EMMC binaries by adding below line in my local.confSTM32MP_DT_FILES_EMMC += "stm32mp157f-dk2"I have also attached the modified flashlayout for EMMC.I came across a post here saying if default pins are changes we will have to do otp for emmc to be detected.below are the pins we are using:-PB14SDMMC2_D0PB15SDMMC2_D1PB3SDMMC2_D2PB4SDMMC2_D3PA8SDMMC2_D4PA15SDMMC2_D5PC6SDMMC2_D6PC7SDMMC2_D7PE3SDMMC2_CLKPG6SDMMC2_CMDDo we need to do otp for these pins or what can be done for EMMC to be detected during dfu(0,0,0) mode for flashing to emmc.below is my flash layout file for emmc:-#OptIdNameTypeIPOffsetBinary-0x01fsbl-bootBinarynone0x0arm-trusted-firmware/tf-a-stm32mp157f-dk2-usb.stm32-0x03fip-bootFIPnone0x0fip/fip-stm32mp157f-dk2-optee-emmc.binP0x04fsbl1Binar
Hi,We have a custom carrier board based on STM32MP157DAC. We have built a custom yocto image.Yocto Version: MickledoreMachine: stm32mp15-discoSoM: STM32MP157DACDistro: openstlinux-westonLinux Kernel: 6.1.82-stm32mp-r2-r0EMMC : EMMC04G-MT32-FBGA153I was able to flash emmc image in DFU mode (000) after making uboot device tree changes I have done same changes in tfa device tree too. But when trying to boot from EMMC (010) It says SDMMC2 init fails and stops.NOTICE: CPU: STM32MP157DAC Rev.ZNOTICE: Model: STMicroelectronics STM32MP157F-DK2 Discovery BoardINFO: PMIC version = 0x21INFO: Reset reason (0x15):INFO: Power-on Reset (rst_por)INFO: FCONF: Reading TB_FW firmware configuration file from: 0x2ffe2000INFO: FCONF: Reading firmware configuration information for: stm32mp_ioINFO: FCONF: Reading firmware configuration information for: stm32mp_fuseINFO: Using EMMCINFO: Instance 2INFO: Boot used partition fsbl1ERROR: CMD13 failed after 5 retriesERROR: SDMMC2 init failedPANIC at PC : 0x2ffec98b
Hi, I'm building st-image-weston on latest openstlinux scharthgap distribution package, and I got the error mentioned in Subject. All the fetch/compile/install are done, and the last step throw this error. Where is the IMAGE_ROOTFS_MAXSIZE defined? I'd really don't want to override anything in conf/local.conf, the build took so much time. Thanks.
Hello.I am trying to use "openstlinux-6.6-yocto-scarthgap-mpu-v25.03.19".The "revision" of "meta-st-stm32-addons" in "oe-manifest/default.xml" seems to be old, is this the correct setting?In "meta-st-stm32mp-addons/conf/layer.conf", there is the following description.LAYERSERIES_COMPAT_stm-st-stm32mp-mx = “mickledore”ST_OSTL_COMPATIBILITY_VERSION_stm-st-stm32mp-mx = “5.1” Thank you for your assistance.
What method should be used to implement 1-wire communication (master) on STM32MP13x board? After doing the research I've found that:for RPI, kernel module w1-gpio can be used to achive 1-wire communication. It's done on kernel level so those critical 1-wire timings can be met. But this module is not natively availabe for STM32MP1, there is no DT overlay ready (like for RPI)dedicated IC like DS2482-800 can be use as a 1-wire master in-the-middle, from which STM32MP1 can later read out the data using I2Cno M-core co-processor is available for STM32MP13x seriesMaybe there is a chance to port the w1-gpio to STM32MP1. But when using it, or the dedicated IC like DS2492-800 1-wire to I2C, I can only communicate with slaves that perfectly follow all 1-wire slave requirements (reset-present signals, timings, commands etc.). For my usage I need to have more control, because some of the 1-wire slaves I would like to communicate with do not follow those rules (they use custom f
Hello! I have succesfully run some test using the model zoo services repo. For classification and object detection I understand. What I cannot find out is whether it is possible to make a custom inference script. My use case requires to run an object detection and then do binary classification on the cropped objects using a classification model. Is it possible to write such a custom script using models generated from the zoo? Also, can i run inference without a camera on images or video? I have purchased the STM32MP257F-EV1 board.Thanks in advance!
Hello!I'm working on creating a signed FIT image in my Yocto build for the STM32MP1. After reviewing the FIT image build recipes in the meta-st layer, it seems that they only support U-Boot SPL, while my bootchain uses TF-A instead of SPL (I’m new to Yocto, so I might be mistaken). This tutorial did not work anymore.https://wiki.st.com/stm32mpu/wiki/How_to_create_Signed_FIT_image_from_Distribution_package I’ve been unable to find specific documentation on how to build a signed FIT image for STM32MP1 in Yocto. Could anyone provide guidance or direct me to relevant documentation for implementing and signing FIT images in this setup?Thank you in advance for any assistance!
WATCH ON-DEMAND | STM32 Summit 2026
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.