STM32 MPUs Embedded software and solutions

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

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

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.

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!

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, 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

Hi ST Community,I'm developing a custom AI application on the STM32MP257F-DK using the following software stack:Software EnvironmentBoard: STM32MP257F-DK Starter Package: OpenSTLinux 6.6 X-LINUX-AI Expansion Package: v6.0 X-LINUX-QT: v2.1 SDK: STM32MP2 SDK (cross-compilation on Ubuntu) Qt: Qt 6.6 (cross compiled) Language: C++ IDE: Qt Creator Application GoalI want to develop my own Qt Quick application (not modify the Python demo) with the following architecture:USB Camera │ ▼Camera Capture │ ▼AI Inference (ST AI Runtime / NPU) │ ▼Bounding Boxes │ ▼Qt Quick GUIThe objective is to build a modular C++ application that can later be extended with multiple AI models. What I have already verifiedThe Logitech C270 webcam is correctly detected./dev/video7v4l2-ctl --all reports:Resolution: 640x480 Format: YUYV 30 FPSI can also run:gst-launch-1.0 v4l2src device=/dev/video7 ! videoconvert ! autovideosinkand the pipeline reaches the PLAYING state. What I di

Dear ST Support Team,I am using the STM32MP157F-DK2 evaluation board with OpenSTLinux (Linux kernel 5.15).I am interfacing a Telit LE910C1-IN LTE modem through the USB Host interface. The modem is successfully detected by lsusb (VID:PID 1bc7:1201), and dmesg confirms successful USB enumeration. However, no /dev/ttyUSB* devices are created, preventing AT command communication.I also verified that the kernel configuration shows:# CONFIG_USB_SERIAL is not setCould you please provide the recommended procedure to enable USB modem support for the Telit LE910 on STM32MP157F-DK2? Specifically, I would like to know the required kernel configuration, drivers, packages, or any additional Device Tree or software changes needed to create the /dev/ttyUSB* interfaces.Below is relevant screenshot for reference.Thank you.

Hi!I have a custom board with STM32MP257F. I have the same electrical setup for HDMI as STM32MP257-DK board have. Hence, the HDMI output is working. But playing sound through HDMI does not work very well. It sounds like the mono .wav files from /etc/share/sound/alsa are recorded under water.I play these sounds by using instructions from https://wiki.st.com/stm32mpu/wiki/How_to_play_audioHere is my sound card. I can play test sounds like pink noise, PWM and sine waves from speaker-test. Here is my hardware setup. I'm using the same HDMI and I2S Device Tree setup as STM32MP257-DK.(No, in mobile view, I cannot post this as a code block because the button "..." is not available)root@watermelon-wine-1aunknown:/usr/share/sounds/alsa# aplay -l**** List of PLAYBACK Hardware Devices ****card 0: STM32MP25DK [STM32MP25-DK], device 0: 400b0000.audio-controller-i2s-hifi i2s-hifi-0 [400b0000.audio-controller-i2s-hifi i2s-hifi-0]  Subdevices: 1/1  Subdevice #0: subdevice #0root@watermelon-wine-1aunkn

Hi everyone,I am new to Android development, and I have two questions about OpenSTDroid v6.2.0.I followed the official documentation to build OpenSTDroid, but I encountered a build error. The details are shown in the attached error.txt.How to build OpenSTDroid distribution - stm32mpu   For OpenSTDroid, is the Device Tree workflow similar to Yocto? In other words, should the Device Tree be generated by STM32CubeMX and then integrated into the OpenSTDroid source tree?Any guidance or suggestions would be greatly appreciated.Thank you.

Hi! We are using the STM32MP153 with FreeRTOS on the CoPro side and OpenEmbedded/Yocto Linux on A7 side. To save power, the CStop mode is used. We go to CStop using`HAL_PWR_EnterSTOPMode(PWR_MAINREGULATOR_ON, PWR_STOPENTRY_WFI);`on the CoPro side and using`echo deep > /sys/power/mem_sleepsystemctl suspend`on Linux side.The CoPro is waken up by a falling edge on pin PI8 via an EXTI interrupt.The Linux also wakes up using a falling edge on pin PI8 (modified device tree).Sometimes (approx. every 10 wakeups, but I can’t reliably tell), a Hard Fault occurs on the CoPro shortly after waking up. I noticed that, when that happens, the memory area 0x10040000 through (at least) 0x10042a80 is overwritten with 0xFF. This is where the IPC shared memory is, which leads to an invalid load operation, causing the Hard Fault. Also, on Linux side, a message occurs `[  272.028406] virtio_rpmsg_bus virtio0: output:id 4294967295 out of range`.Sometimes, the memory area of approx. 0x1003D000 through 0x100

Hi!I think there is some display issues with STM32CubeMX with the cr_ker_ltdc If I look in the clock summary, I csn see that the ck_ker_ltdc is set to 100 MHz."ck_flexgen_27 0 0 0 100000000 0 0 0 Y deviceless no_connection_id             ck_ker_ltdc 0 0 0 100000000 0 0 50000 N 48010000.display-controller lcd                                                                                                                                    48000000.dsi px_clk                                                                                                                                 deviceless no_connection_id                clk_pix_ltdc 0 0 0 100000000 0 0 50000 Y 48010000.display-controller ref                                                                                                                                       deviceless no_connection_id         "In this case, I need to increase the cr_pix_ltdc to above 148.5 MHz to achieve full HD at the HDMI output.But in the CubeMX,

I have an EtherCAT project that uses the open-source software EtherCAT master station IGH.Currently, my platform is the main controller STM32MP257, and the relative jitter of IGH--enable-generic is relatively large.I would like to inquire if ST has provided corresponding real-time network card driver patches for the EtherCAT master station IGH?If there are any other better solutions, please let me know. Thank you~

HI How are you!I am using the SAI interface on the STM32MP257F-DK to connect directly to an external ADC and acquire data in frame mode. I have assigned SAI3 to the M33 domain and run the firmware under FreeRTOS. Despite following all resource isolation configurations specified in the reference manual and conducting a full week of detailed debugging and security settings, launching the M33 firmware remotely from the A35 Linux domain always results in an IAC error. Is it not possible to assign the SAI peripheral to the M33 core?  thanks !

CM33 FIRMWARE SIGNING KEY MISMATCH---We have successfully flashed OpenSTLinux v26.02.18 with the full optee layout and confirmed:- remoteproc0 fw_format = TEE- The pre-built example firmware (USBPD_DRP_UCSI_CM33_NonSecure_sign.bin) loads and runs correctly- STM32CubeIDE debugger successfully attaches to the running CM33However, when we sign our own CM33 firmware using sign_rproc_fw.py, OP-TEE rejects it:   tee_remoteproc: TA_RPROC_FW_CMD_LOAD_FW invoke failed TEE err: ffff0006   remoteproc remoteproc0: Boot failed: -5Error 0xffff0006 = TEE_ERROR_SECURITY (signature verification failure)Signing command used:   python3 sign_rproc_fw.py --in CM33_LED_CM33_NonSecure.elf --out CM33_LED_sign.bin --key default.pemKeys tried (all have identical MD5: c5254a254e63da936a640d0a0093bcf0):- STM32CubeMP2-1.3.0/Utilities/optee_os/keys/default.pem- sdk/sysroots/cortexa35-ostl-linux/usr/include/optee/export-user_ta_arm64/keys/default.pem- sdk/sysroots/cortexa35-ostl-linux/usr/include/optee/export-user_t

Dear ST Support Team,Thank you for your continued support. We are working with the STM32MP257F-EV1 evaluation board and have two issues we need help resolving.Hardware: STM32MP257F-EV1 Evaluation Board (MB1936D)Software Package: OpenSTLinux v26.02.18 (stm32mp2-openstlinux-6.6-yocto-scarthgap-mpu-v26.02.18)Host OS: Ubuntu 26.04STM32CubeIDE: v2.1.1STM32CubeProgrammer: v2.22.0Flash Layout Used: FlashLayout_sdcard_stm32mp257f-ev1-ca35tdcid-ostl-m33-examples-optee.tsv---ISSUE 1: ETHERNET PORT (end0 / ETH1) NOT WORKING---The Ethernet interface end0 shows NO-CARRIER even when a cable is physically connected.Observations:- ip link show end0 → state DOWN, NO-CARRIER- cat /sys/class/net/end0/carrier → 0- ethtool end0 | grep 'Link detected' → Link detected: no- udhcpc -i end0 → broadcasts DHCP but gets no response- The Ethernet driver loads correctly: stm32-dwmac 482d0000.eth2 end0- We have tried ETH1 and ETH2 ports on the board- We have tried different cables and different router ports- The boar

Hi everyone,we applied the ST FWU reference solution on our own platform based on the STM32MP157F.The solution was taken and adapted from the ST Yocto layer meta-st-ota (https://github.com/PRG-MPU-CUST/meta-st-ota). SummaryWhen performing consecutive updates using the ST FWU reference implementation (TF-A FWU metadata + RAUC + post-install.sh + rauc-mark-good.service), the FWU rollback boot counter keeps decreasing across successful updates. Expectation: after each successful boot of a newly updated bank (and rauc-mark-good.service finishing successfully), the FWU boot counter should be reset to the initial value (4 in this setup).Actual: the FWU boot counter is decremented (4 → 3 → 2) with each update cycle, even though the system was marked good. This suggests that the rollback counter is not being reset by the rauc-mark-good integration in the ST FWU reference solution.(full log is attached, including metadata content printed in hexa after each step) Reproduction

Hi,I am working with the STM32MP135F-DK board and built an SD card image using Yocto Scarthgap (openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06).The image boots successfully. To prevent the Year 2038 (Y2038) problem, I confirmed that require conf/distro/include/time64.inc is already included and processed in the distro configuration.To test Y2038 compliance, I manually set the system time to the year 2040.The time was set successfully, and verifying it via the date command showed the correct time (2040).Checking the RTC using hwclock --show --verbose also returned the correct time in 2040.NTP is explicitly disabled via timedatectl set-ntp false, so network time synchronization is not causing any interference.The Problem:The issue occurs upon a reboot. After the system reboots, the time rolls back to the year 2024.My Analysis:Upon looking into the Linux kernel source (drivers/rtc/class.c), it appears that the kernel clamps or prevents system time overflow. This seems to be a fallback mech

hi team,I'm facing issue in enabling usart6 of the expansion connector of stm32mp257f-ev1, All i did was to enable the &usart6 via DT overlay, even tried disabling dmas, but no luck.I have attached the kernel log and also attached the RIFSC debug log FYRHoping for a quick reply, thanks in advance./dts-v1/; /plugin/; / { compatible = "st,stm32mp257f-ev1"; fragment@0 { target = <&usart6>; __overlay__ { status = "okay"; }; }; };$ stty -F /dev/ttySTM1 115200 E/TC:0 stm32_serc_handle_ilac:133 SERC exceptions [63:32]: 0x10 E/TC:0 stm32_serc_handle_ilac:139 SERC exception ID: 36 [ 39.106314] SError Interrupt on CPU0, code 0x00000000bf000002 -- SError [ 39.106336] CPU: 0 PID: 1618 Comm: stty Tainted: G O 6.6.78 #1 [ 39.106344] Hardware name: STMicroelectronics STM32MP257F-EV1 Evaluation Board (DT) [ 39.106348] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 39.106357] pc : stm32_usart_rx_dma_start_or_resume+0x80/0x234 [ 39.106375] lr : stm32_usart

I ported PPSSPP 1.20.3 to run on the STM32MP257D platform.With the GLES backend, everything looks fine and normal games run without issues. But when I try heavier 3D games like Tekken 6, it gets extremely choppy – single-core CPU usage stays around 95%.Then I tried switching to Vulkan. At first, the emulator crashed on startup. I debugged it by adding some print statements and found that a function call was returning an incorrect value – which shouldn't happen according to the Vulkan spec. Because of that, another function (vkCreateSwapchainKHR) ended up failing. 1) PPSSPP Crash Log:Spoiler (Highlight to read)08:00:074 Vulkan/VulkanContext.cpp:1416 I[G3D]: surfCapabilities_.current: 960x544 min: 1x1 max: -1x-1 computed: -1x-1 08:00:079 Vulkan/VulkanContext.cpp:1579 E[G3D]: vkCreateSwapchainKHR failed! VK_ERROR_DEVICE_LOST08:00:074 Vulkan/VulkanContext.cpp:1416 I[G3D]: surfCapabilities_.current: 960x544 min: 1x1 max: -1x-1 computed: -1x-1 08:00:079 Vulkan/VulkanConte