Ask questions and find answers on STM32 microprocessors and dedicated embedded software solutions, such as Yocto SDK, Qt, and OP-TEE.
Most recent activity
SetupSTM32MP157, Cortex-A7, bare-metal SDMMC1 → eMMC (61071360 blocks, 512B), CardType 1 Kernel clock: pll4_p_ck (125MHz) via RCC_SDMMC12CKSELR IDMA: single-buffer mode Test: single-block write (512B) to block 4096, then read-back + compare Problem After a cold power-on, the first HAL_MMC_WriteBlocks_DMA() intermittently fails with TX FIFO underrun. Not every cold boot — boot-to-boot random, same config either way.On a boot where it fails, it fails on every retry (tested 5x), even with a full peripheral reset (RCC AHB6 reset + reinit) between each attempt — card info (BlockNbr etc.) verified correct every time, so it's not stale driver/card state.Read never fails, on the same bad boot, same clock, same peripheral.Register data — same board/config, two different cold bootsPassing boot:DCOUNT@DataEnd: 0x0, STA@DataEnd: 0x100 → RESULT: PASSFailing boot (5 attempts, each after full reinit):Attempt 0: DCOUNT@Err=0x098, STA@Err=0x1010, ErrCode=0x10(TXUNDERR)→0x14 (+CMD timeout on stop)Attem
Hello ST Team,I am working on the STM32MP257F , using OpenSTLinux 5.0.17 and the ST TSN switch stack v6.I would like to confirm whether the TSN Ethernet switch is officially supported on the STM32MP257F-DK boardNOTE:I understand that the DK board has only one externally accessible Ethernet port and that it can be used as a TSN endpoint. I have enabled the TSN switch, and the following interfaces are available:lowlan0end0sw0p1sw0p2sw0p3sw0epWith the TSN switch enabled, the switch interfaces are created and sw0p1, sw0p2, and sw0p3 are visible. I have connected an external PHY to sw0p3.root@stm32mp2-e3-d2-99:~# ethtool sw0p3Settings for sw0p3:Supported ports: [ TP MII ]Supported link modes: 10baseT/Full100baseT/Full1000baseT/FullSupported pause frame use: NoSupports auto-negotiation: YesSupported FEC modes: Not reportedAdvertised link modes: 10baseT/Full100baseT/Full1000baseT/FullAdvertised pause frame use: NoAdvertised auto-negotiation: YesAdvertised FEC modes: Not reportedLink partner
Hello ST Team,I am working on an AI-based Driver Monitoring System on an STM32MP257F board using an IMX335 MIPI CSI camera, libcamera,GStreamer and STAI-MPU.I am facing a memory allocation / segmentation fault issue when using a custom STAI-MPU application.------------------------------------------------------------HARDWARE------------------------------------------------------------Board:STM32MP257FCamera:Sony IMX335 MIPI CSICamera interface:CSI / DCMIPPDisplay:Weston / WaylandCamera source:LIBCAMERA------------------------------------------------------------SOFTWARE------------------------------------------------------------libcamera:0.3.0+dirtyPython:3.12The exact OpenSTLinux/X-LINUX-AI version and other system information can be provided if required.------------------------------------------------------------KNOWN-GOOD ST APPLICATION------------------------------------------------------------I tested the official ST face-recognition example:https://github.com/STMicroelectronics/meta
Hi everyone,I’m working on a small STM32 project using a piezo buzzer and would like to generate a simple melody from different frequency tones.I can already generate individual tones by changing the timer frequency, but I’m not sure what the best approach is for playing a sequence of notes with different durations.For example, I would like to create a short melody such as:Note A → short duration Note B → short duration Note C → longer duration Pause → short duration RepeatWould it be better to use a timer with PWM and change the frequency for each note, or is there another recommended approach for generating melodies on STM32?I’m mainly looking for guidance on the structure of the code and how to handle the note frequency and duration cleanly.Thanks in advance for any suggestions!
Hello,I am working with an STM32MP135DAF on a custom board and am trying to boot OpenSTLinux/Yocto from eMMC.My setup is:MPU: STM32MP135DAFCustom hardware/boardCustom Yocto machineSTM32CubeMX used to generate the Device Tree filesOpenSTLinux / YoctoBoot device: MMCImage: `core-image-minimal`I have created a custom machine configuration and integrated the CubeMX-generated Device Tree files into my Yocto build.The Yocto build completes successfully with: “bitbake core-image-minimal”. The image and flashlayout files are generated successfully.However, when I try to program the board using STM32CubeProgrammer in USB DFU mode, CubeProgrammer reports that it cannot reconnect to the device.I also connected a serial terminal to the debug UART. During the boot/programming sequence, I see:PANIC at PC : 0x2ffe6405Exception mode=0x00000016 at: 0x2ffe6405The relevant CubeMX-generated DTS files, machine `.conf`, and `local.conf` are attached below.Could someone please help me identify what could ca
Is it possible to start the HDMI from U-boot in STM32MP2?I want to see the start up log.
Hi everyone,I am working on the STM32MP257-EVAL board, where my Cortex-M33 application requires both FreeRTOS and OpenAMP middleware to run together.After referring to the STM32CubeMPU packages, I found separate example projects:One for FreeRTOSOne for OpenAMP (running in bare-metal environment)I tried combining both examples into a single application. The FreeRTOS part is working correctly, but OpenAMP hangs during initialization.After debugging, I noticed that libmetal is getting compiled for the generic platform instead of the FreeRTOS platform. To address this, I changed the toolchain configuration from:-DCMAKE_TOOLCHAIN_FILE=cmake/platforms/stm32mp-generic-gcc.cmaketo:-DCMAKE_TOOLCHAIN_FILE=cmake/platforms/stm32mp-freertos-gcc.cmakeHowever, this results in multiple compilation errors. It seems the provided libmetal port may not be fully compatible with the FreeRTOS platform setup.Has anyone successfully integrated FreeRTOS + OpenAMP together on STM32MP257 (M33 core)?Are there any
Hi!I've found good programs for surfing on the web (Google, wikipedia, MSN, News etc.) and playing Youtube videos in full 1080p HD. No heavy JavaScript is enabled. Those programs requires an update of the extremely light weight GUI library FLTK 1.3.8 to 1.5.x. Is there anyway I could do that in OpenSTLinux Yocto SDK? The name of these programs are: - FLTube Youtube Player - Dillo Web Browser These are old technologies from late 90's, but they are extremely optimized to run on low, slow and old hardware. Still maintaining by developers.
On the STM32MP257F-EV1 evaluation board, configuring SPI3 in slave mode (spi-slave;) works correctly for the SCK, MOSI, and MISO signals, but the NSS (chip select) pin — PB1, using the documented-correct AF1 alternate function — silently fails to be claimed by the pin controller. No error or warning is logged anywhere. All three other SPI3 pins on the same bus, using the same AF1 value, claim successfully.
I am trying to increase the cpu speed of a custom board with stm32h743VIT6 and 16mhz crystal. However, once I change the speed, the UART output prints out gibberish. I have verified the UART works with the HSI at default speed of 64Mhz. Attached is the code and board schematics. Thanks for the help.
Hello, I have a TFT LCD display that uses a ST7789v controller. I would like to interface with it using the KMS DRM subsystem in Linux. I have been having issues getting this to work though.So far I have confirmed that the default driver to ST7789v controllers is running, but it only seems to create a drm_panel. I am having trouble creating/linking it to a connector/CRTC/encoder. I have any DBI related options enabled in menuconfig, but I don’t see any way to interface with DBI displays when running modetest. Does anyone have any advice as to what I need to do to get DRM working with this display? Will I need to write my own drivers? I can provide any existing code/devicetree configurations if need be.
Hi,I'm bringing up Ethernet (RGMII) on a custom STM32MP257 board using a Marvell 88E1512 PHY.The MAC driver loads successfully, the PHY is detected, but bringing the interface up fails with a timeout.I have attached the driver code, dts and pinctrl.dtsi for you reference. eth1_mdio_pins_mx: eth1_mdio_mx-0 {pins1 {pinmux = <STM32_PINMUX('A', 9, AF10)>; /* ETH1_MDC */bias-disable;drive-push-pull;slew-rate = <2>;st,io-clk-edge = <0>;st,io-retime = <0>;st,io-delay-path = <0>;st,io-delay = <0>;};pins2 {pinmux = <STM32_PINMUX('A', 10, AF10)>; /* ETH1_MDIO */bias-disable;drive-push-pull;slew-rate = <0>;st,io-clk-edge = <0>;st,io-retime = <0>;st,io-delay-path = <0>;st,io-delay = <0>;};};eth1_mdio_sleep_pins_mx: eth1_mdio_sleep_mx-0 {pins {pinmux = <STM32_PINMUX('A', 9, ANALOG)>, /* ETH1_MDC */<STM32_PINMUX('A', 10, ANALOG)>; /* ETH1_MDIO */};}; eth1_rgmii_pins_b: eth1-rgmii-1 {pins1 {pinmux = <STM32_PINMUX('
Hi community,I am using yocto build ( version - openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11) in this I am facing challenge over below build time error.Exception: subprocess.CalledProcessError: Command 'tar --exclude=./sysroot-only -cf - -C .../linux-libc-headers/6.6/image -p -S . | tar -xf - -C .../linux-libc-headers/6.6/package' returned non-zero exit status 2. got *at() syscall for unknown directory, fd 4 unknown base path for fd 4, path include couldn't allocate absolute path for 'include'. function package_prepare_pkgdata finished DEBUG: Executing python function perform_packagecopy ERROR: Error executing a python function in exec_func_python() autogenerated:The stack trace of python calls that resulted in this exception/failure was: File: 'exec_func_python() autogenerated', lineno: 2, function: <module> 0001: *** 0002:perform_packagecopy(d) 0003: File: '/home/datadir/EVK-build-CMS/layers/openembedded-core/meta/classes-global/package.bbclass', lineno: 363, function: perform
Hi ST Team,I am facing an issue while building an OpenSTLinux project for STM32MP255.EnvironmentBoard: STM32MP255 OpenSTLinux: 5.0.8 Yocto Distribution: openstlinux-weston Ubuntu: 22.04 LTS Kernel: 6.8.0-124-generic pseudo version: 1.9.0+git pseudo SRCREV: 28dcefb809ce95db997811b5662f0b893b9923e0 ProblemThe build fails during:build-info-openstlinux.bb:do_packageThe failure occurs inside Yocto's standard perform_packagecopy() while executing:tar --exclude=./sysroot-only \-cf - \-C image \-p -S . |tar -xf - \-C packageThe error is:got *at() syscall for unknown directory, fd 4unknown base path for fd 4, path buildcouldn't allocate absolute path for 'build'tar: ./etc/build: Cannot open: Bad addresstar: Exiting with failure status due to previous errors Investigation PerformedI verified the following:1. RecipeThe build-info-openstlinux.bb recipe is unchanged and only creates the /etc directory.The /etc/build file is generated by image-buildinfo.bbclass.2. Generated fileVerified that:ima
WebKit is now releasing a new upgrade for their WPE WebKit API so the web browser can run on the GPU instead of CPU.Here is what the WPE WebKit Dev Team is writing:In any case, try the new WPEPlatform API (https://wpewebkit.org/) instead of Cog, and that suggestion still stands. Cog is currently at the end of its lifetime and won't see more stable versions, as we are fully focused on this new API that will not only make integration much simpler but will also allow making the most of more modern features like dmabuf, which enables zero-copy buffer sharing both at the graphics and multimedia layers of WPE, therefore increasing performance, stability and smoothness.Now, while the new WPEPlatform API will be released as stable in September, it's still fairly mature and you can already try it out with ToT or with the latest unstable releases, as well with the latest stable release (2.52.3). See some links to the API docs below:https://wpewebkit.org/reference/unstablehttps://wpewebkit.org/re
I am working on camera integration with both the STM32MP257F-DK and STM32N6570-DK development boards and would appreciate some guidance from the community.My setup Boards: STM32MP257F-DK STM32N6570-DK Camera sensor: Suggest One camera Sensor for both, currently I have VD55G1 and VD66GY Software: ST OpenSTLinux (Yocto) on STM32MP257F-DK My questions Is it possible to interface a camera to the STM32MP257F-DK using the DCMI peripheral, or is MIPI CSI-2 the only supported camera interface for this board? For the STM32N6570-DK, what is the recommended approach for connecting a camera through DCMI? Are there any supported camera modules or reference designs? Are there example projects available for image capture using DCMI? If the camera sensor provides only MIPI CSI-2 output (such as the VD55G1 and VD66GY), is an external bridge/converter required to use it with DCMI? Are there any ST application notes, reference designs, or GitHub examples demonstrating camera i
We are experiencing issues on STM32MP13 when using TF-A with OP-TEE due to an "Undefined instruction" exception during low-power entry.When TF-A is built with a standard arm-*-gnueabihf toolchain, the compiler is allowed to generate NEON instructions because the STM32MP1 platform enables:ARM_WITH_NEON := yesIn our case, GCC generates NEON instructions when compiling lib/compiler-rt/builtins/udivmoddi4.c, which is reached from udelay() during the low-power sequence. At that point, however, the VFP/NEON unit is disabled, so execution aborts with an "Undefined instruction" exception.Relevant TF-A build settings:ARM_CORTEX_A7 := yes (from STM32MP1 platform settings) ARM_WITH_NEON := yes (from STM32MP1 platform settings) AARCH32_SP := optee CTX_INCLUDE_FPREGS=0Relevant compiler options:-mcpu=cortex-a7 (generated by TF-A from ARM_CORTEX_A7 := yes) -mfpu=neon (generated by TF-A from ARM_WITH_NEON := yes) -ffreestanding -fno-builtin -OsWe have verified that replacing udelay() with a simple
Hi ST,We have developed a custom board based on the STM32MP257F-DK design, with the primary difference being the use of the STM32MP255DAK3 processor in place of the STM32MP257F. All other components and configurations—such as RAM, eMMC, and SD card interface—remain the same as the original DK board.We generated the device tree source (DTS) using STM32CubeMX; however, we are currently unable to boot the board successfully. Initially, we encountered an error related to the RISAF component, which we managed to resolve. Unfortunately, we are now facing a new issue resulting in a Panic in EL3 error.Despite our efforts, we have not been able to determine the exact root cause of the problem. Given that only the processor has changed and all other hardware remains identical, we would appreciate any guidance or suggestions you could provide to help us resolve this issue and complete the bring-up process.NOTE: the 1st error ################################################NOTICE: CPU: STM32
Hi ST Team,We are developing a custom Qt 6 + OpenGL object detection application on the STM32MP257F-DK using OpenSTLinux 6.6, X-LINUX-AI, and the ONNX Runtime (stai_mpu) backend.Our application architecture is based on the official ST object detection example. We use the same stai_mpu_wrapper and ssd_mobilenet_pp.hpp post-processing implementation from the stai_mpu_object_detection example, while replacing the GTK/Cairo UI with our own Qt/OpenGL application.Application Architecture Board: STM32MP257F-DK OS: OpenSTLinux 6.6 AI Backend: ONNX Runtime (libstai_mpu_ort.so.6) Camera: libcamera + DCMIPP Display: Qt 6 + OpenGL (Wayland/Weston) Camera Pipeline: Viewfinder stream → RGB565 → OpenGL live preview AI stream → RGB888 → STAI inference Inference: stai_mpu_wrapper::RunInference() Post-processing: Official ssd_mobilenet_pp.hpp from the ST stai_mpu_object_detection example. 1. DCMIPP camera configuration issueOur AI model requires a 300×300 RGB888 input, so we conf
Hi ST Support,I would like to know whether there is a supported mechanism to enable or disable debug console output at runtime across the entire boot chain, including the following components:TF-A (Trusted Firmware-A) OP-TEE U-Boot Linux Kernel Root File System (user space)Use case:I connect to the target board through the serial console to monitor boot logs. After the system has booted, I access the board over USB SSH. From the Linux shell, I would like to execute a command that enables or disables debug messages on the serial console.My goal is to control the debug console output without rebuilding or reflashing any of the bootloader or firmware components.Could you please let me know:Is there a supported way to enable or disable debug console output for all boot stages at runtime? If this is not possible, what is the recommended approach to achieve similar functionality? Does ST provide any framework or utility to control console logging across TF-A, OP-TEE, U-Boot, the Linux kernel
We are trying to build BL2 for STM32MP13 with `TRUSTED_BOARD_BOOT=1` and mbedTLS 3.6.6, using a standard `arm-*-gnueabihf` toolchain. The build fails while compiling the first mbedTLS source file:...In file included from /src/mbedtls-3.6.6/library/aes.c:14:/src/mbedtls-3.6.6/library/common.h:23:10: fatal error: arm_neon.h: No such file or directory 23 | #include <arm_neon.h> |...The failure occurs as follows. The STM32MP1 platform enables:ARM_WITH_NEON := yes This adds `-mcpu=cortex-a7 -mfpu=neon` to the compiler flags. When using a hard-float toolchain such as `arm-linux-gnueabihf`, GCC consequently defines `__ARM_NEON`.Since library/common.h is included by every mbedTLS source file, mbedTLS then tries to include:#if defined(__ARM_NEON)#include <arm_neon.h>However, TF-A builds with -`nostdinc` and uses its own libc headers. As a result, arm_neon.h cannot be found and the build fails.The same configuration builds fine with a soft-float toolchain, where `__ARM_NEON` i
I have replicated the MB1936 Schematic for a dash-cam system based on the MP257FAIx series by choosing the relevant circuits from the reference to design my custom PCB. I would love to seek help from the community for the following requirement. If anything pops up my mind, I shall update on this thread - Can I use the 5-pin MOLEX/JST GH Signal Connectors to interface the Waveshare IMX335 USB Camera Module? I have used the USB Host Port Architecture to implement my logic, and it has worked well. Kindly find the Schematics PDF for your reference. Thank You!
Hi ST, Actually , In my Correct Project, i need Small SIZE PCB , So there is no left space in my PCB , So can i replace this PMIC to another PMIC which is in small Size, please Suggest me Any PMIC which is compatible with MP257,
Hi there, I found several issues in the STM32CubeMP2 CMSIS headers as follows:1. Missing opening parenthesis in bitmask macrosIn stm32mp21*xx.h, _Msk macro definitions were missing the opening parenthesis, leaving a dangling closing parenthesis with no matching open:// Before #define USB_OTG_GCCFG_FSVMINUS_Msk 0x1UL << USB_OTG_GCCFG_FSVMINUS_Pos) // After #define USB_OTG_GCCFG_FSVMINUS_Msk (0x1UL << USB_OTG_GCCFG_FSVMINUS_Pos)While the C preprocessor performs simple text substitution and the shift operation may still evaluate correctly at the call site depending on context, the unbalanced parentheses break static analyzers, automated code-generation tools, and linters that parse these headers. Adding the opening parenthesis also makes operator precedence explicit and unambiguous.2. Malformed comment delimitersAll of header files involves inline comments used *!< instead of the correct /*!< Doxygen-style comment opener, missing the l
Dear Team,I hope this email finds you well. I am writing to seek your expert clarification on a critical hardware design decision we are currently evaluating for our STM32MP257-based custom board. --- Current Memory Configuration --- • SoC : STM32MP257• Memory Part : Micron MT53E1G32D2FW-046 WT:C• Type : LPDDR4• Density : 32 Gbit (4 GB)• Organization: 1 x32 (Dual Channel — Channel A + Channel B) --- Our Understanding from ST Documentation --- Based on our research of the following official ST documents: 1. AN5723 (Rev 3, Aug 2024) : "Interface width is 32-bit when full-populated, or 16-bit when half-populated." 2. AN5724 — DDR Routing Guide: "For the 16-bit LPDDR4 interface, one 16-bit LPDDR4 is used in point-to-point connection. With this configuration it can drive up to 2 Gbyte memory." 3. AN5489 (Rev 6, Sep 2025) : STM32MP257 supports both 16-bit (half-populated) and 32-bit (full-populated) LPDDR4 configurations. Our understanding is:• If using a native x1
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.