Ask questions and find answers on STM32 microprocessors and dedicated embedded software solutions, such as Yocto SDK, Qt, and OP-TEE.
Most recent activity
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
This might be my misunderstanding of how OVERRIDES work, but I'm building with the recently-released "wrynose_v26.02.18" branch of meta-st-stm32mp and, for the purpose of debugging, I wanted to set:ST_OPTEE_CORE_DEBUG = "y"so I did that in my local.conf file, but after I set it, it still had the value of "n" for the build, so I dumped the value to see how it was (or was not) being set:bitbake-getvar -r optee-os-stm32mp ST_OPTEE_CORE_DEBUG... snip ...# $ST_OPTEE_CORE_DEBUG [3 operations]# set /home/rpjday/BOARDS/nexus/wrynose/build/conf/local.conf:13# "y"# set /home/rpjday/Layers/wrynose/st/meta-st-stm32mp/recipes-security/optee/optee-os-stm32mp-common.inc:37# [_defaultval] "y"# override[stm32mp15common]:set? /home/rpjday/Layers/wrynose/st/meta-st-stm32mp/recipes-security/optee/optee-os-stm32mp-common.inc:38# "n"# pre-expansion value:# "n"ST_OPTEE_CORE_DEBUG="n"You can see how the first line seems to show that I am explicitly setting it in my local.conf, then the processing continues th
I get this issue in the booting process of Linux. Then nothing else happens, except outputs from Optee. F/TC:? 0 pta_scmi_ocall:207 Posting MSG message on channel 0 root '/dev/disk/by-partuuid/e91c4e10-16e6-4c0e-bd0e-77becf4a3582' doesn't exist or F/TC:? 0 regulator_set_voltage:202 vddcpu 800000uV does not contain a /dev. Question:I assume that this is a common issue for the MP2 platform. Is there anyway I could fix this? Extlinux.conf perhaps? I have the same clock settings as DK.See attached file.
Hi~ My board gets stuck at the kernel stage during boot. I've referred to numerous related posts but failed to resolve the issue.The boot file versions I use are OP-TEE 4.0, U-Boot 2023.10 and Linux 6.6.116.The official device tree I referenced is stm32mp157f-ed1.I have attached the boot logs, hardware schematic and device tree files. Please help analyze the root cause of the problem.stm32f7-i2c i2c@5c002000: pinctrl_select_state_full: pinctrl_config_one: err=-19 [ 1.741795] arm-scmi firmware:scmi: SCMI Protocol v2.0 'ST:' Firmware version 0x0 [ 1.748959] DEBUG: SCMI CLOCK PROBE STARTED! sdev name: scmi_dev.2 I/TC: SCMI-CLOCK: Reporting 34 clocks to Linux I/TC: SCMI-FW: ETZPC ID 2 DENIED for Non-Secure world! I/TC: SCMI-MSG: NS Request Clock ID 15 (iwdg1), ETZPC 2, Access=FAIL I/TC: SCMI-CLK: ID 15 has no name/not found I/TC: SCMI-FW: ETZPC ID 7 DENIED for Non-Secure world! I/TC: SCMI-MSG: NS Request Clock ID 16 (rng1_k), ETZPC 7, Access=FAIL I/TC: SCMI-CLK: ID 16 has no name/not
I wonder why this is happening after U-boot has booten up?It seems that something is NULL. D/TC:? 0 tee_ta_close_session:484 Destroy session Error: eth1@482c0000 address not set. D/TC:? 0 tee_ta_init_session_with_context:562 Re-open trusted service a8cfe406-d4f5-4a2e-9f8d-a25dc754c099 F/TC:? 0 pta_scmi_invoke_command:404 SCMI command 0x3 ptypes 0x3 F/TC:? 0 pta_scmi_invoke_command:404 SCMI command 0x4 ptypes 0x651 D/TC:? 0 tee_ta_close_session:465 csess 0x821301f0 id 1 D/TC:? 0 tee_ta_close_session:484 Destroy session No ethernet found. �7�[r�[999;999H�[6n�8No EFI system partition No EFI system partition Failed to persist EFI variables D/TC:? 0 tee_ta_init_pseudo_ta_session:303 Lookup pseudo TA ab7a617c-b8e7-4d8f-8301-d09b61036b64 D/TC:? 0 tee_ta_init_pseudo_ta_session:315 Open rng.pta D/TC:? 0 tee_ta_init_pseudo_ta_session:330 rng.pta : ab7a617c-b8e7-4d8f-8301-d09b61036b64 F/TC:? 0 plat_prng_add_jitter_entropy:74 0x1C D/TC:? 0 tee_ta_close_session:465 csess 0x821301f0 id 1 D/TC
Hello,I would like to ask about the current status of Bare-Metal support for the Cortex-A35 core on the STM32MP2x platform (STM32MP257F-DK).While searching the ST Community, I came across the following discussion related to this topic:https://community.st.com/t5/stm32-mpus-embedded-software-and/stm32mp257f-dk-bare-metal/td-p/787100Since that discussion is now more than one year old, I wanted to check whether there have been any updates regarding Bare-Metal development support on the STM32MP2 platform.When creating a project in STM32CubeIDE for the STM32MP257F-DK, I could not find an option to create a Bare-Metal project targeting the Cortex-A35 core.Could you please clarify the following:Is there now an official Bare-Metal project template for Cortex-A35 in STM32CubeIDE?Are there any application notes, examples, or documentation demonstrating how to run Cortex-A35 without Linux?Is there any roadmap update regarding official Bare-Metal support for STM32MP2x?Our use case requires:Fast bo
ObjectiveSign STM32MP23 firmware using AWS KMS ECDSA P-256 keys instead of local private keys, to enable cloud-based signing workflow.Hardware: STM32MP23 seriesHeader Version: 0x00020200 (v2.2.0)Signing Algorithm: ECDSA_SHA_256 (P-256 NIST / secp256r1)Development and Issues summary as followsWe have followed following ways to sign binaries externallyUsing external HSM - SoftHSMThis method shows the exact same issue mentioned in community threadError: Invalid Header version valueHeader v2.2 accepts 8 public keysIf we skip the header version argument, the signing tool fails with CKR_OBJECT_HANDLE_INVALID error.Using PKCS#11 solution along with aws-kms-pkcs11With this method too, we face similar errors as mentioned in #1. With header version 2.2 argument, it gives Invalid header errorIf we skip the header version argument, the signing tool fails with CKR_OBJECT_HANDLE_INVALID error.Developed a custom signing script (Compatible with the STM32 Signing workflow)Firmware s
I am developing a custom board using the STM32MP255F-AK.After configuring the kernel via menuconfig, the .config file reverts to its default state for some reason.The custom board settings and device tree are located in `meta-st-stm32mp-addons`.I have already fetched the source code using `devtool modify virtual/kernel`.Run `bitbake -c menuconfig virtual/kernel`ADIN_PHY was set to yThe .config file is saved in the following location:workspace/source/linux-stm32mp/.config.new -> ~/OpenSTLinux/distpkg_ev1/build-openstlinuxweston-stm32mp25 -disco/tmp-glibc/work/stm32mp25_disco-ostl-linux/linux-stm32mp/6.6.48-stm32mp-r1/build/.configNext,I ran `bitbake virtual/kernel`The ADIN_PHY=y setting remained in .configI tried running bitbake virtual/kernel againThe ADIN_PHY=y setting remains in .configI tried modifying the kernel's DeviceTreeI ran bitbake virtual/kernelIt reverted back to “ADIN_PHY is not set.” Also, the build result showed that the ADIN_PHY driver was not included.How can I prev
Hello teachers, I am a developer of the STM32MP157F chip and would like to ask you a question about device tree configuration. Please help me. The version I am currently using is as follows: optee 4.10 uboot 2023.10 linux 6.6 At present, the system startup is stuck in the kernel stage. I have attached the device tree and system startup log. Can you help me analyze the specific reasons? Thank you very much. I've been stuck on this problem for many days。NOTICE: CPU: STM32MP157FAD Rev.ZNOTICE: Model: STMicroelectronics STM32MP157F eval OSTL daughter on eval motherINFO: PMIC version = 0x21NOTICE: Reset reason (0x15):INFO: Power-on Reset (rst_por)INFO: FCONF: Reading TB_FW firmware configuration file from: 0x2ffe1000INFO: FCONF: Reading firmware configuration information for: stm32mp_fuseINFO: FCONF: Reading firmware configuration information for: stm32mp_ioINFO: Using SDMMCINFO: Instance 1INFO: Boot used partition fsbl1NOTICE: BL2: v2.10-stm32mp1-r2.0(debug):()NOTI
When U-boot is going to startup at the entry point address = 0x84000000, then this happens.IAC ID 137 is RISAF4 - DDR-SDRAM.SERC ID 32 is USART2.I don't know why USART2 seems to write at the Optee address region (0x82000000 - 0x83FFFFFF) and it all lands on 0x83FFFF80. The optee address region is secure and USART2 seems to write on this address.I have attached my complete device tree and I wonder if the ST dev team can help me to find why USART2 is trying to access 0x83FFFF80 in DDR-SDRAM?My processor is STM32MP257FAK.Note 1: The difference between 0x84000000 and 0x83FFFF80 is 128, e.g one byte. So I guess that something is shifted wrongly here?Note 2: I'm using LDO2 as VDDIO_SDCARD and BUCK7 for 3v3 for VDD_SDCARD. Because my PMIC is the STPMIC25A and not STPMIC25D. F/TC:0 0 pmic_get_voltage:192 vddgpu_pmic: get voltage: 800000 uV D/TC:0 0 set_opp:67 set clock to 800000kHz I/TC: Primary CPU switching to normal world boot INFO: BL31: Preparing for EL3
Hi, I'm having trouble building the core-image-weston image. I'm using Ubuntu 22 and VMware Workstation.config in local.conf:MACHINE = "stm32mp1"DISTRO ?= "poky"EXTRA_IMAGE_FEATURES ?= "debug-tweaks"USER_CLASSES ?= "buildstats"PATCHRESOLVE = "noop"BB_DISKMON_DIRS ??= "\STOPTASKS,${TMPDIR},1G,100K \STOPTASKS,${DL_DIR},1G,100K \STOPTASKS,${SSTATE_DIR},1G,100K \STOPTASKS,/tmp,100M,100K \HALT,${TMPDIR},100M,1K \HALT,${DL_DIR},100M,1K \HALT,${SSTATE_DIR},100M,1K \HALT,/tmp,10M,1K"PACKAGECONFIG:append:pn-qemu-system-native = " sdl" CONF_VERSION = "2" Error :ERROR: libglu-2_9.0.3-r0 do_configure: meson failedERROR: libglu-2_9.0.3-r0 do_configure: ExecutionError('/home/dawid/Projects/yocto/build-mp1/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/libglu/9.0.3/temp/run.do_configure.2642423', 1, None, None)ERROR: Logfile of failure stored in: /home/dawid/Projects/yocto/build-mp1/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/libglu/9.0.3/temp/log.do_configure
Hi ST Team,I am currently working with the STM32MP257F-EV1 based custom carrier board and experiencing an issue during the flashing process(boot mode is eMMC).Initially, the board works fine and flashing completes successfully. Over the time, the flashing is failing.From the flash logs, I observe that the failure occurs at partition 0x03 (refer the attached flash_log.txt).At the same time, the UART console shows panic logs during boot (attached in uart_boot_logs.txt).Could you help us to know the root cause of this issue and steps to recover?Thank & regards,Kaviya
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.