STM32 MPUs Software development tools

Custom MP157AAA3 board.  SD card formatted with ECO 5.0.0 using the SD tools using the files from the starter package. (including rootfs etc..) .  Build the TF-A, OP-TEE (in SYSRAM), U-boot and kernel from the ECO 5.0.0 sources.Kernel generates the messages as below and then feezes. The DT's were generated using CubeMX and customized for the board. It looks like drivers are all waiting on resources to become available, perhaps one single one they all need. Hence the deferred probe.Any hints/steps how to debug this ?[12.832984] Run /init as init process[ 13.390242] platform 50000000.rcc: deferred probe pending[ 13.395778] platform 5000d000.interrupt-controller: deferred probe pending[ 13.402749] platform 48002000.dma-router: deferred probe pending[ 13.408792] platform soc:pinctrl@50002000: deferred probe pending[ 13.414956] platform soc:pinctrl@54004000: deferred probe pending[ 13.421084] platform 48000000.dma-controller: deferred probe pending[ 13.427498] platform 58000000.dm

Hello, I'm trying to install EGit in STM32CubeIDE, but I'm getting an error.Cannot complete the install because one or more required items could not be found. Software being installed: Git integration for Eclipse 7.5.0.202512021534-r (org.eclipse.egit.feature.group 7.5.0.202512021534-r) Missing requirement: Git integration for Eclipse - Core 7.5.0.202512021534-r (org.eclipse.egit.core 7.5.0.202512021534-r) requires 'osgi.bundle; org.eclipse.core.runtime [3.33.100,4.0.0)' but it could not be found Cannot satisfy dependency: From: Git integration for Eclipse 7.5.0.202512021534-r (org.eclipse.egit.feature.group 7.5.0.202512021534-r) To: org.eclipse.equinox.p2.iu; org.eclipse.egit.core [7.5.0.202512021534-r,7.5.0.202512021534-r]Does anyone else have the same problem?

Hello,A question on STM32CubeMX v6.16.1, when  I select OpenAMP in Middleware and Software Packs, I can see configuration options, like COMMUNICATION_MODE, SHM_START_ADDRESS, SHM_SIZE etc, but they are all greyed out and not allowing me to change anything.Is there a way to change these options in STM32CubeMX GUI? (I'm aware that the code generated by CubeMX is cutrrently broken so CubeIDE cannot build this code, and I hope for the fix in the next CubeMX version). Another question - the code in CM33/ folder that is generated by CubeMX, can it be built by the Yocto bitbake, like it does for CA35/ folder?Thanks! Regards,Sergei

Hello everyone !device: STM32MP257F-DKWe build the X-LINUX-QT starter package following in steps1.X-LINUX-QT starter packagerepo init -u https://github.com/STMicroelectronics/oe-manifest.git -b refs/tags/openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11 repo sync2.Install X-LINUX-QT distribution package v2.2.0 git clone -b v2.2.0 https://github.com/STMicroelectronics/meta-st-x-linux-qt.git layers/meta-st/meta-st-x-linux-qt git clone -b 6.8.3 https://code.qt.io/yocto/meta-qt6.git layers/meta-qt63.Setup the build environmentDISTRO=openstlinux-weston MACHINE=stm32mp2 BSP_DEPENDENCY="layers/meta-qt6 layers/meta-st/meta-st-x-linux-qt" source layers/meta-st/scripts/envsetup.sh4.building bitbake st-image-qt package-indexthen, we have an error message as follows: Spoiler (Highlight to read)ERROR: qtbase-6.8.3-r0 do_package_qa: QA Issue: /usr/share/examples/corelib/serialization/cbordump/cbortag.py contained in package qtbase-examples requires /usr/usr/bin/env, but no providers found in RDE

Hi ST, How i can I use M33 co-processor of stm32mp257 series , and how can i connected debug with Cubeide,how can i use Ethernet port  through the Co-processor,Note: I am using Opnestlinux distribution package.

Hi,I am trying to enable secure boot in STM32mp157f-ev1 board. I am using the Developer Package source code provided by ST. I am using this command to generate the tf-a.stm32:make E=0 -f ../Makefile.sdk.stm32mp1 TF_A_DEVICETREE=stm32mp157f-ev1 TF_A_CONFIG="optee-sdcard optee-programmer-usb" TRUSTED_BOARD_BOOT=1 GENERATE_COT=1 ROT_KEY=<path>/privatekey.pem ROT_KEY_PWD=<password> KEY_ALG=ecdsa MBEDTLS_DIR=<path>/mbedtls-3.4.1 DYN_DISABLE_AUTH=0 DEPLOYDIR=$FIP_DEPLOYDIR_ROOT/arm-trusted-firmware stm32But I am getting an error:LD SOURCES-stm32mp-openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11/stm32mp-openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11/sources/ostl-linux/tf-a-stm32mp-v2.10.13-stm32mp-r2-r0/tf-a-stm32mp-v2.10.13-stm32mp-r2/../build/optee-sdcard-stm32mp157f-ev1/bl2/bl2.elfarm-ostl-linux-gnueabi-ld.bfd: SOURCES-stm32mp-openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11/stm32mp-openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11/sources/ostl-linux/tf-a-stm32mp-v2.10.13-stm32mp-r

 Hello ST team,I am facing a reproducible issue with USART6 on the STM32MP257F-DK board when working with the OpenSTLinux 6.6.78-stm32mp-r2 distribution.1. Summary of the ProblemWhen I enable USART6 in the Linux Device Tree and deploy the DTB on the target:SSH access breaks completely after reboot(ssh root@192.168.7.1 no longer works)When running a simple A35 UART6 echo application via minicom,the entire board resets.The reset is triggered by RIFSC / SERC firewall exceptions.The very same DTS configuration works perfectly on OpenSTLinux 6.6.48 —no SSH issue, no kernel panic, and UART6 user application runs fine.This strongly suggests a firewall / RIF / OP-TEE integration regression between OSTL 6.0.0 and 6.6.78.2. DTS Snippet That Triggers the Problem  &usart6 { pinctrl-names = "default", "idle", "sleep"; pinctrl-0 = <&usart6_pins_a>; pinctrl-1 = <&usart6_idle_pins_a>; pinctrl-2 = <&usart6_sleep_pins_a>; status = "okay"; /* e

1. STM32 Cmake project2. Select executable option. 3. Chose the MPU4. Build  ERROR==========   

Hi Community Members,We are using a MYB-LD25X development board and are able to boot Linux successfully on the A-core. However, we are facing issues when debugging Cortex-M33 code generated by STM32CubeMX. Although we assign the required peripherals exclusively to the M33 core, the initialization code generated by CubeMX does not work as expected. When the M33 firmware starts, it consistently enters a HardFault. Has anyone experienced a similar issue with the MYB-LD25X / STM32MP2 platform? Any guidance on correct peripheral assignment, resource management (RIF/ResMgr), or CubeMX configuration for M33 debugging would be greatly appreciated.Thank you in advance.

Hello,Is the STM32CubeProg + STlink (v3) supposed to work with STM32MP257 ?I can't get any connection.Thank you 

Hello,I can’t download the file en.SOURCES-stm32mp-openstlinux-6.6-yocto-scarthgap-mpu-v25.08.27.tar.gz from https://www.st.com/en/embedded-software/stm32mp1dev.html#get-software. Only this file gets downloaded: SDK-x86_64-stm32mp1-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06.tar.gz.Could you please advise how I can download the correct en.SOURCES?

Hello,I am trying to generate a STM32CubeIDE project using CubeMX (version 6.16.1) for MP157D-DK1 board. It generates some device trees (linux, u-boot, tp-a) but it fails to generate the CubeIDE project.I also tried older versions of CubeMX (as late as 6.12) and none work.The error it displays is attached. Any idea what might be going wrong with the code/project generation? I have STM32CubeIDE v2.0.0 installed.Thanks.

This post provides a workaround for a specific issue in STM32CubeIDE v2.0.0. The issue will be resolved in the next version. If STM32CubeIDE v2.0.0 is installed from scratch and if the imported project in STM32CubeIDE v2.0.0 is a project generated with STM32CubeMX v6.16, it is not possible to install the OpenSTLinux plugin. Consequently, it is not possible to import OSTL projects such as Linux, Optee, TF-A, or U-Boot. In order to work around this, the following steps are recommended: Install STM32CubeIDE 1.19.0 Install OpenSTLinux plugin v6.1.0 in STM32CubeIDE 1.19.0 Import the projects concerned (Linux, Optee, TF-A, U-Boot) Help > Check for updates > select STM32CubeIDE 2.0.0 > Next > Finish Then restart the STM32CubeIDE.

How can I activate CSI i STM32CubeIDE for STM32MP257?As you can see, I'm missing something.Any special clock I need to activate?I have activated CSI from DCMIPP. But still the CSI cannot get its pinns green.   

Hello,I'm trying to modify STM32MP157x-DK2 kernel so that it would use ST ethernet drivers (dwmac-stm32.ko, stmmac.ko et al.) as modules (like on stm32mp257f board we have) and not be included into the kernel uImage. I'm using latest v.25.08.27 package and instructions for building and modifying  kernel, and uImage and its default modules are built fine. But when I try to use make menuconfig  to modify build configuration, I receive the following errors:make menuconfigGEN MakefileHOSTLD scripts/kconfig/mconf/home/###/workspace/DeveloperPackage/SDK_MP1/sysroots/x86_64-ostl_sdk-linux/usr/lib/gcc/x86_64-ostl_sdk-linux/13.3.0/../../../../x86_64-ostl_sdk-linux/bin/ld: scripts/kconfig/mconf.o: in function `show_help':mconf.c:(.text+0x87a): undefined reference to `stdscr'/home/###/workspace/DeveloperPackage/SDK_MP1/sysroots/x86_64-ostl_sdk-linux/usr/lib/gcc/x86_64-ostl_sdk-linux/13.3.0/../../../../x86_64-ostl_sdk-linux/bin/ld: scripts/kconfig/lxdialog/checklist.o: in function `print

Dear Sir/Madam, We are currently using CubeMX version 6.1.4 alongside CubeIDE version 1.18.1 to generate code for the M33 microcontroller. However, we have encountered an issue where the clock configuration functions are not being generated as part of the code.We kindly request your guidance on resolving this matter. Please let us know if further details are required.Thank you for your assistance.Best regards

I'm working on an STM32 project using STM32CubeIDE with CMake as the build system. I need to add custom include paths for my own header files.I tried to include my_folder from C/C++ General -> Paths and Symbols -> Includes, but it doesn't work.Note that under C/C++ Build -> Settings there is no settings to include anything, which are available only when working with STM32CubeMX/STM32CubeIDE Project   

We are pleased to announce that STM32CubeIDE 2.0.0 release is available. STM32CubeIDE is now independent from STM32CubeMX. With this release, device configuration, previously handled within STM32CubeIDE via STM32CubeMX, is now exclusively available through the stand-alone STM32CubeMX tool. Users will configure microcontroller peripherals and generate initialization code separately in STM32CubeMX, then import the generated projects into STM32CubeIDE for coding and debugging.   STM32CubeIDE, is now a stand-alone tool, offers the possibility to create empty project through its own MCU/Board selectors now present inside. What does this change mean for developers?  Separate download and installation: STM32CubeMX is no more integrated in STM32CubeIDE, requiring separate download alongside STM32CubeIDE 2.0.0 for configuration and code generation.  Tool update flexibility: Developers can update and freeze&n

We are pleased to announce that STM32CubeMX 6.16.0 release is available. What is new in 6.16.0: Added support for new microcontrollers across the STM32WBA, STM32N6 and STM32H5 series and the STM32WL3x product line. The related new boards include the NUCLEO-WL3RKB1 and NUCLEO-WL3RKB2. Implemented the "Start from Board" feature for NUCLEO-WL3RKB1 and NUCLEO-WL3RKB2: Preconfigured board setup through the Start From Board feature simplifies project creation and significantly reduces development time. Released a new installer that natively supports Apple® Silicon : Native support of ARM64 for mac computers.  Implemented the memory management tool for STM32N6: This feature is designed to assist developers in configuring and optimizing the memory layout of their STM32N6 projects efficiently. Enhanced the build process using CMake: Default configuration: ST ARM CLANG with its own linker instead of GCC linker. Picolib is selected as default library for the b

We are pleased to announce that STM32CubeProgrammer 2.21 is available What is new in 2.21: • Support for the STM32WL3Rxx microcontrollers:         – Internal memory programming        – Option byte and OTP programming        – PKCS#11        – Firmware authentication • STM32MP21x microprocessors: SSP support on Linux®• STM32WBA6xxG microcontrollers: Support for 1-Mbyte flash memory size• Support for new devices in the STM32C0 series: STM32C011xx, STM32C031xx, STM32C051xx, STM32C071xx, STM32C091xx, and STM32C092xx microcontrollers• Support for the factory reset of option bytes:        – STM32WBA5xxx and STM32WBA6xxx microcontrollers         – STM32U375/385 microcontrollers• Dynamic upgrade of components• Support for SWD multi-drop• Fast read new CLI command Main fixed issues in 2.21: Refer to the STM32CubeProgrammer wiki at: STM32CubeProgrammer errata 2.

 Hello,I am working on an STM32MP257F platform using the STM32MPU OpenSTLinux Distribution (V25), together with the latest STM32CubeMX code-generation flow for the STM32MP257F-DK board.I am using the STM32MPU-OSTL-DEV-helper to build the full BSP (Kernel + U-Boot + OP-TEE).The Linux DTS and U-Boot DTS build correctly.However, the OP-TEE Device Tree compilation fails with the following error:Error: stm32mp257f-mydts-mx-rif.dtsi:63.116-117 syntax errorFATAL ERROR: Unable to parse input tree To investigate, I inspected the CubeMX-generated OP-TEE RIF file:STM32MPU-OSTL-DEV-helper/DEVICETREE/myDTS/optee/stm32mp257f-mydts-mx-rif.dtsiUsing:nl -ba stm32mp257f-mydts-mx-rif.dtsi | sed -n '60,130p'The file appears syntactically correct. For example:60 RIFPROT(STM32MP25_RIFSC_I2C5_ID, EMPTY_SEMWL, RIF_LOCK, RIF_NSEC, RIF_NPRIV, RIF_UNUSED, RIF_SEM_EN, RIF_CFEN) 61 RIFPROT(STM32MP25_RIFSC_I2C6_ID, EMPTY_SEMWL, RIF_LOCK, RIF_NSEC, RIF_NPRIV, RIF_UNUSED, RIF_SEM_EN, RIF_CFEN) 62 RI

 Description:When configuring DDR parameters for STM32MP257 in STM32CubeMX, I changed the DDR speed bin:Speed_Bin: DDR4-3200AA 22-22-22 → DDR4-2933Y 21-21-21After generating the code:The device tree were updated correctly according to the new timing values.However, the generated Device Tree files (.dts/.dtsi) did not change at all.This is confusing. The DTS still reflects the previous configuration even though the DDRCTRL/DDRPHY timings have been modified. Questions to ST:Is this a known limitation of STM32CubeMX (i.e., CubeMX does not update DTS when DDR timing changes)?Should the Device Tree be updated automatically when the DDR Speed_Bin is changed?The current behavior looks like a potential bug or an unimplemented feature in CubeMX, as it may lead users to believe DDR configuration did not take effect.Thank you.

Using CubeMX v6.15 on Windows 11I tried generating a project for MP257-EV1 selecting the M33-Master option"Initialize all peripherals with their default Mode = YES"Without making any changes, the Pinout tool shows an error (red encircled X) for TAMP and warnings for RCC and when trying to generate code, it issues this WARNING:- Main Config: These peripherals still have some not configured or wrong parameter values: [RCC, TAMP]How does one go about fixing these issues?

I’m working on a custom STM32MP257DAK3 board.In STM32CubeMX, I need both SDMMC1 (SD card) and SDMMC2 (eMMC) to be supported as possible boot devices.When I check both:SDMMC1 → Memory Boot DeviceSDMMC2 → Memory Boot DeviceThe following error appears in IPs assignment rules: Faulty state detected for SDMMC1, SDMMC2 : Only one Memory Boot Device can be assigned to TF-A simultaneously. I understand that TF-A allows only one memory boot device at a time.However, our hardware design supports dual boot options (either from eMMC or SD card). How can I fix this error? 

 Description of the IssueI am experiencing a configuration validation warning related to RCC when generating code in STM32CubeMX version 6.15.0 for the STM32MP257DAK3 MPU. Although the code can be generated, CubeMX reports the following RCC warning during validation:  Main Config: These peripherals still have some not configured or wrong parameter values: [RCC]This warning appears even when the RCC configuration seems complete and valid.Steps to ReproduceOpen STM32CubeMX v6.15.0Create a new project for STM32MP257DAK3Navigate to System Core → RCCSet HSE to Crystal/Ceramic ResonatorClick GENERATE CODECubeMX displays the above warning during pre-generation configuration checkI've selected Pin Context Assignment from the dropdown menu, but it's empty.