Ask questions and find answers on STM32 microprocessors and dedicated embedded software solutions, such as Yocto SDK, Qt, and OP-TEE.
Most recent activity
I tried installing x-linux-ai by following the instructions in the [X-LINUX-AI Starter package] .but I was unable to install it due to an error. root@192-168-1-59:~# apt-get updateThe software package is provided AS IS, and by downloading it, you agree to bebound to the terms of the software license agreement (SLA).The detailed content licenses can be found athttps://wiki.st.com/stm32mpu/wiki/OpenSTLinux_licenses.https://www.st.com/resource/en/additional_license_terms/additional-license-terms-for-x-linux-isp.htmlHit:1 http://packages.openstlinux.st.com/6.2.1 scarthgap InReleaseHit:2 http://extra.packages.openstlinux.st.com/ISP/6.2.1 scarthgap InReleaseReading package lists... Doneroot@192-168-1-59:~# apt-get install x-linux-ai-toolReading package lists... DoneBuilding dependency tree... DoneReading state information... DoneE: Unable to locate package x-linux-ai-toolroot@192-168-1-59:~# apt-get install x-linux-ai-tool My setup consists of a custom board based on the STM32MP255F, onto w
We recently joined the MFi Apple program needed to create a USB accessory. Does anyone have the iAP2 code needed?
Hello,I am currently porting OpenSTLinux to a custom board based on the STM32MP255F.I successfully built all the required images, wrote them to an SD card, and attempted to boot the board. However, OP-TEE OS crashes just before U-Boot starts, with the following error:E/TC:0 0 stm32_iac_itr:192 IAC exceptions [159:128]: 0x10000000E/TC:0 0 stm32_iac_itr:197 IAC exception ID: 156E/TC:0 0 Panic at /usr/src/debug/optee-os-stm32mp/4.0.0-stm32mp-r3.1/core/drivers/firewall/stm32_iac.c:212 <stm32_iac_itr>As far as I understand, IAC exception ID 156 is related to RCC.I checked the corresponding OP-TEE source code (stm32_iac.c) as well as the RCC-related Device Tree definitions, but so far I have not been able to determine what is causing the IAC exception. Environment- SoC: STM32MP255F- Board: Custom board- OpenSTLinux: openstlinux-6.6-yocto-scarthgap-mpu-v26.06.10- OP-TEE: 4.0.0-stm32mp-r3.1- STM32CubeMX: V6.18.1- STM32Cube FW_MP2: V1.3.2 Device Tree backgroundThe Device Tree used for thi
Hello, I am evaluating whether Ubuntu 26.04 LTS can be used as a host development environment for OpenSTLinux on STM32MP25. My environment is:Ubuntu 26.04.1 LTS (glibc 2.43)STM32MP25 OpenSTLinux Distribution Package(stm32mp2-openstlinux-6.6-yocto-scarthgap-mpu-v26.06.10)BitBake 2.8.1 Initially, BitBake failed with:ERROR: User namespaces are not usable by BitBake, possibly due to AppArmor.This was resolved by disabling:kernel.apparmor_restrict_unprivileged_userns After that,$ bitbake -pcompleted successfully and all recipes were parsed without errors. However, when running:$ bitbake virtual/kernelthe build fails during pseudo-native compilation with the following error:error: conflicting types for 'openat2' The log shows:WARNING: Your host glibc version (2.43) is newer than that in uninative (2.42).Disabling uninative so that sstate is not corrupted.and later:ERROR: pseudo-native-1.9.3+git-r0 do_compilefollowed by the openat2 prototype conflict. My questions are:- Is Ubuntu 26.04 offici
Hi!I'm trying to developing a Qt6 QML application with Vulkan support. But I having some issues. Can ST Dev Team give me an example of an Qt6 QML application that use Vulkan? It must work on STM32MP257. It will be a reference. I think I having wrong code settings on my Qt6 QML application. For OpenGL, it works. But not for Vulkan.Thank you!
Hi! When I run the command "vulkaninfo --summary". I get this critical error."libvulkan_VSI.so.1.3.3 contained a 1.1 or greater API version, but does not support vkEnumerateInstanceVersion, treating as a 1.0 ICD".What this means is that according to the data sheet of STM32MP2, the GPU supports Vulkan 1.3. but due to the lack of support for vkEnumerateInstanceVersion, the Vulkan support falls back to 1.0.Question: is this true that Vulkan falls back to 1.0 fue to this warning?Is there any newer version of libvulkan_VSI.so?Here is the complete output: """WARNING: [Loader Message] Code 0 : loader_scanned_icd_add: Driver /vendor/lib/libvulkan_VSI.so.1.3.3 supports Vulkan 1.3, but only supports loader interface version 2. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Manifest ICD for "/vendor/lib/libvulkan_VSI.so.1.3.3" contained a 1.1 or greater API version, but does not support vk
Hello ST team and community,We are bringing up a custom board based on the STM32MP257F, built with Yocto (OpenSTLinux, linux-stm32mp kernel [version, e.g. 6.6.x]). The board DTS is derived from stm32mp257f-ev1.dts.ProblemWe connected a DFRobot DFR0678 (800x480) MIPI DSI display and get no image. On investigation, the DRM driver for the display controller does not appear to load or probe at all (drivers/gpu/drm/stm/drv.c and ltdc.c).What we have checked1.&ltdc and &dsi are set to status = "okay" in the board DTS, and the LTDC port/endpoint links to dsi_in in both directions.2.Kernel config: CONFIG_DRM_STM=m, CONFIG_DRM_STM_DSI=m, CONFIG_DRM_DW_MIPI_DSI=m, CONFIG_DRM_PANEL=y.3.In /sys/kernel/debug/clk/clk_summary, the clocks related to LTDC are disabled.Our expectationAs far as we understand, drv.c should bind to the st,stm32mp25-ltdc node and run probe() even when no display is physically connected, because the match depends only on the device tree and not on the panel hardware.
Hi!I tried the application open source OpenNOW from Github, for game streaming at my MP2 with 2GB RAM. It worked. I had to modify some parts of OpenNOW e.g run a separate wayland window for video stream because OpenNOW's pipeline streaming directly from video decoder to the GPU and the GPU renders the graphics inside an Qt QML application. So my modification only streams directly from video decoder to a wayland window.Summary:- Input controls feels smooth - Graphic resolution is 1080p- Audio is perfect - About 55-60 FPS The only bad thing is the color. If you look at this game when I stream, you can see that it's quite dark and the color red is very red. Does this has to do something with how the video decoder uses the colors? First, I don't know if it's the video decoder that causing this. When I stream from Gstreamer or Youtube using my Qt Youtube Client (included in the meta-layer) or optimized web browser for MP2 (made with QtWebEngine - included in the meta-layer), then the colors
Hello STMicroelectronics Community,I am working with an STM32MP257DAI3 processor running OpenSTLinux with Linux kernel 6.6.11.I am trying to configure an LT8912B MIPI-DSI to HDMI bridge instead of the ADV7535.and My openstlinux version version openstlinux-6.6-yocto-scarthgap-mpu-v26.I referred to the Linux Device Tree binding documentation:"Documentation/devicetree/bindings/display/bridge/lontium,lt8912b.yaml"I have configured the HDMI connector, MIPI-DSI interface, and LT8912B bridge in my device tree. However, after booting the board with the `st-image-weston` image, the '/sys/class/drm/' directory is empty. 1. Device Tree Configuration HDMI Connector Nodehdmi: connector { compatible = "hdmi-connector"; label = "hdmi"; type = "a"; port { hdmi_connector_in: endpoint { remote-endpoint = <&lt8912_out>; }; };}; MIPI-DSI Node &dsi { vdd-supply = <&scmi_vddcore>; vdda18-supply = <&scmi_v1v8>; status = "
Subject: STM32MP257F-EV1 (MB1936D) not booting after PA6/PA7 MDF1 rework + SAI2 speaker addition — no console output, no USB DFU enumerationBoard: STM32MP257F-EV1, board reference MB1936DBackground — MDF1 microphone rework:We were bringing up PDM microphone capture on MDF1 (channel 6, PA6=SDI6, PA7=CCK0). On this board revision, PA6/PA7 are hardwired only to the onboard RTL8211F Ethernet PHY (ETH3.TXD0/TXD1 via series resistors R169/R175) with no external header access. To route these pins to MDF1 instead, we physically soldered a wire tap onto R169 and R175, and disabled Ethernet in our device tree so MDF1 could claim PA6/PA7 without a pinmux conflict.Background — speaker interface addition (same device tree, added afterward):Separately, we added a playback path using a MAX98357A I2S digital audio amplifier driving a 4Ω/5W speaker, over SAI2A:- CN5 pin 12 (PJ11, SAI2_SCKA) -> MAX98357A BCLK- CN5 pin 35 (PJ3, SAI2_FSA) -> MAX98357A LRCLK- CN5 pin 38 (PJ12, SAI2_SDA) -> MAX9835
Product / board: STM32MP257F-EV1, MB1936 revision, configuration [A35-TD or M33-TD]SummaryThe board worked for one session after two hardware changes, then stopped booting. LD6, LD5 and LD11 light. LD3 and LD4 do not. The Boot ROM gives no response over UART or USB.What was changedA PDM microphone was wired to PA6/PA7 by a wire tap at R169/R175 (MDF1). This was our own design decision, not based on any ST recommendation. A MAX98357A speaker amplifier was added on SAI2A (PJ11, PJ3, PJ12 at AF4), with matching device-tree changes.What I have checkedCheck Result NRST (B1) 3.3 V idle, 0 V pressed, 3.3 V after release VDDIO 3.3 V 1V8 1.8 V VDDCPU 0.8 V VDDCORE 0.8 V VDDGPU 0 V (not treated as a fault) VDD_DDR 0.037 V (not treated as a fault) VDDA1V8_AON 1.8 V VDD3V3USB 3.3 V HSE Not checked; no accessible probe point Boot ROM tests (SW1 all OPEN)STM32_Programmer_CLI -l detects the ST-LINK V3. -c port=/dev/ttyACM0 br=115200 and -c port=/dev/ttyACM1 br=11520
Hi,I am currently using ST’s OpenSTLinux distribution, version 6.2.1, for our STM32MP135F-based custom board.My objective is to customize the boot and operating system components—TF-A, OP-TEE, U-Boot, and the Linux kernel—to meet our board-specific requirements. Boot media is emmc.I have successfully set up the Yocto build environment and can build the complete image. However, to reduce development and debugging time, I would like to build these components individually rather than rebuilding the entire image after every change.I have also set up the environment for building and installing these boot artifacts separately. I would appreciate your guidance on the correct build and deployment sequence, including which source files, configuration files, device trees, and generated binaries are required at each stage.Could you please clarify the recommended workflow for building, integrating, and flashing TF-A, OP-TEE, U-Boot, and Linux independently while ensuring compatibility with ST’s Op
Hello everyone! I am following the tutorial on st wiki on how to work with STM32MP257F-DK board. Everything was going pretty good, until the “Develop on Arm® Cortex®-M33” part. This is a really important part for me, because the main reason I chose this MPU is because of the additional low-power cortex M33 and M0 co-processors. The part where I am stuck is “Modify, rebuild and reload the firmware for A35-TD flavor”. I have successfully built the “*_sign.bin” file and populated the board with it by using the “Run_Configuration” button. However past 78% the process stops and shows an error that states:“Error in final launch sequence:Failed pre launchFailed pre launchFirmware remoteproc load failed, please: 1. make sure that /lib/firmware on your target has space 2. make sure that /lib/firmware has write access > you can open a Console View for this..”In the STM32MP2 system a log of these messages are displayed:“[ 2321.306087] remoteproc remoteproc0: powering up m0 [ 2321.307
Hello,I was checking if it is possible to test my M33 NS code I generated using CubeMX would work in Developer Mode. However, the information found on internet suggest it being difficult as it requires the clock to be configured by M33 and also needs RIF accesses making it difficult. Without proper documentation on use case and how to use developer mode, it becomes challenging to work on a project within a stipulated time. So please, I would request for the help and Information to test and debug the code in Developer mode. Thanks for the support.With regardsAmit
I am working on secure boot and firmware encryption on a custom STM32MP257F board based on the STM32MP257F-DK.I have already provisioned the encryption key material into OTP and am testing encryption through Yocto using ENCRYPT_ENABLE = "1", with a 128-bit key for FSBL and a 256-bit key for FIP.I noticed that when I use the correct encryption keys, the board boots successfully.When I use a wrong key, flash fails with a decryption error.But when I remove the encryption settings from local.conf, the board still boots even though the keys are already provisioned in OTP.I want to understand why this happens. I thought that once the encryption keys are provisioned, the board should not boot without the correct keys.Could someone please clarify a few things?Is it normal for the board to boot with an unencrypted image even after the encryption keys are provisioned into OTP? Does provisioning the keys into OTP only store the keys, or is there a way to enforce encryption at boot? What is the re
Hello,I’m bringing up a custom board based on STM32MP135F and cannot read OTP reg. I am using scarthgap based Yocto distribution “openstlinux-6.6-yocto-scarthgap-mpu-v26.06.10”I modified DTS of TF-A, Optee, u-boot according to my board. File generated from openstlinux-6.1 version, I am able to able to do read and write operation.I am able to program EMMC but not able to do OTP read and write. Getting following error on COM port-optee optee: TA_NVMEM invoke failed TEE err: ffff0006, err:0Error: OTP read issue -5dfu_read: Failed to fill bufferError Log from ST-programmer CLI-Error: Read OTP Partition failedError: Uploading the OTP structure failedError: Initializing the OTP structure failedDo I need enable any configuration or any build modification for this openstlinux-6.6?
Hai, I am trying to read the data stored in the EEPROM via I²C during the U-Boot SPL stage.The EEPROM data can be read successfully from both U-Boot and user space, as shown below. Uboot Area:iWave-G62H>iWave-G62H> i2c dev 0Setting bus to 0iWave-G62H> i2c md 0x50 0x0000.2 10000: 99 .iWave-G62H> i2c md 0x50 0x0000.2 10000: 99 .iWave-G62H> i2c mw 0x50 0x0000.2 0x01 1iWave-G62H>iWave-G62H> i2c md 0x50 0x0000.2 1 0000: 01 .iWave-G62H> i2c md 0x50 0x0000.2 10000: 01 .iWave-G62H> User Space:root@imx91-iwg62h:~#root@imx91-iwg62h:~# dd if=/sys/bus/i2c/devices/0-0050/eeprom bs=1 count=1 2>/dev/null | hexdump -C00000000 01 |.|00000001root@imx91-iwg62h:~#root@imx91-iwg62h:~#root@imx91-iwg62h:~# printf '\x99' | dd of=/sys/bus/i2c/devices/0-0050/eeprom bs=1 count=1 1+0 records in1+0 recor
Hi!I’m using this commangst-launch-1.0 -v filesrc location=bbb.mp4 ! qtdemux ! h264parse ! v4l2slh264dec ! waylandsink fullscreen=trueTo play video in 1080p without lagging. But this comes without sound.How can I play sound with gst-launch-1.0?I can only play sound with “aplay /path/to/file.wav”.
I have heard that ST have tried QtNanoBrowser on the MP257 and according to them the web browser is working well.My question is if there are any more additional information about the user experience of QtNanoBrowser on the MP257?For example a benchmark and which pages did run smoothly and which pages took long time to load.
Hi listI am testing the STM32MP135d-odyssey for a project. It is small, still cheap, has support for POE and on board ethernet connectors and SD-card holder. The buildroot repositories are quite old so I wonder if the board is in actual use and can be recommended for new projects?The xogium repository seems very outdated but I have cherry picked a few patches from there to a fork of STMicroelectronics repository and it builds and boots with modern buildroot. I have only tested to boot from sd-card yet.Please test if interested. I have updated versions of buildroot-stm32mp135d-odyssey, u-boot and optee_os in my Github repository.https://github.com/GauiStori/buildroot-stm32mp135d-odysseyShall I make pull requests for u-boot and optee_os to STMicroelectronics or xogium? Or is there an updated version of xogium somewhere?Now I want to see if I can find a working Yocto recipe. RegardsGudjon
Error MessageDebugger Settingsi am trying to upload the firmware into the co-processor of the stm32mp157fdk-2 board and struggling with this error I shared the error details and my debug configurations In the drop down menu of the Serial Port nothing is over there but I can able to use putty and can able to view the booting messages, and I am not trying to upload the code while connected with the putty, I also tried the engineering mode tooAnd now I am on the windows, is this windows specific error or what? cause when I was trying to upload using the linux everything was running very fine. Now I create elf file everytime and scp into the board then manually start the co processor, I don’t want to do this again and again
Hi all, I’m searching a method to configure the NVRAM STPMIC25 VINOK_rise param in the 0x90 adress Register (NVM_MAIN_CTRL_ SHR1) As this is a sensitive reg I’m supposing this field and may others are Locked in the NRAM in the DK board from ST. Please I’m considering running Board with 3.3V power Buck Converters. Cheers, Habib
Subject: STM32MP257F-DK - How to get the MPI7001 800x480 HDMI panel working (EDID override gives test patterns, but no stable image/video)SETUP- Board: STM32MP257F-DK- OS: OpenSTLinux (Yocto build), Weston 13.0.1, kernel 6.6.129 (-dirty)- Panel: MPI7001, 7inch HDMI Display-B (800x480)- Display path: LTDC -> DSI host -> ADV7535 (i2c0, 0x3d, adv7511 driver) -> HDMI -> panel- stm_drm and dw_mipi_dsi_stm are built as modules (=m) and loaded via /etc/modules-load.dPROBLEMThe display never shows a stable image or video from the DK board. With the panel attached, and before loading any EDID: modetest -M stm -c 32 0 disconnected HDMI-A-1 0x0 0 31 (0 modes)dmesg shows "EDID block 0 is all zeroes", and Weston logs "connector 32 is disconnected" and exits.WHAT WE DID1. Copied the panel's EDID from a PC (cat /sys/class/drm/card1-HDMI-A-2/edid > panel.bin) to /lib/firmware/edid/panel.bin on the board.2. Loaded it on the board: mount -t debugfs none /sys/kernel/deb
I am going to build linux system on a board based on STM32MP257F and have read many kinds of related technical documents.In the process, a question bothers me. I want to modify only several components such as uboot and kernel in existing STM32MPU Distribution Package. To do that, the STM32MPU Developer Package is needed because their source cdoes and build tools are required. This is where the major problem lies. Those are as follows:To build the source files, what is used between Developer Package’s SDK and Distribution Package’s BitBake ? After the modified components are built anyway, how and where are their binary images added into the Distribution Package including their configurations ?I have read in the documents that interoperation between the Developer Package and the Distribution one is available.But, I have not found out its actual usage example.
Hi,Does anyone know if there is a list of the operating systems supported on the Cortex-A35 cores of the STM32MP257 ? Any information or pointers would be welcome.Thanks!
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.