STM32 MPUs

Hi,I am debugging the STM32MP257F-EV1 board via a JTAG debugger . The kernel version is 6.1.82.I have a sample application that runs on Linux and I am trying to debug it.When I set a breakpoint in the application, I get the following message on the Kernel prompt:---------------------------------------------------------------------E/TC:0   stm32_iac_itr:192 IAC exceptions [159:128]: 0x200E/TC:0   stm32_iac_itr:197 IAC exception ID: 137E/TC:0   stm32_risaf_dump_erroneous_data:256DUMPING DATA FOR risaf@420d0000E/TC:0   stm32_risaf_dump_erroneous_data:257 =====================================================E/TC:0   stm32_risaf_dump_erroneous_data:258 Status register (IAESR0): 0xb1E/TC:0   stm32_risaf_dump_erroneous_data:266 -----------------------------------------------------E/TC:0   stm32_risaf_dump_erroneous_data:268 Faulty address (IADDR0): 0x10b4dc8dcE/TC:0   stm32_risaf_dump_erroneous_data:287 ==========

Dear STMicroelectronics Support Team,I am working with the STM32MP257F-DK board and using OpenSTLinux. In my setup, I am only using the Cortex-A35 (MPU) without any firmware running on the Cortex-M33 (MCU). I am trying to enable USB OTG functionality using the USB3.0 DRD port via the USB Type-C connector (CN15).My goal is to enable dual-role OTG behavior (host/device) using only the A35 core and Linux kernel. I would like to ask:1. How can I properly enable and configure the USB OTG mode using the USB3.0 DRD port in this configuration?2. Is it possible to manually switch between host, device, and OTG modes through the Linux kernel (e.g., via sysfs or configfs interfaces)?3. Do I need to load any additional drivers, userspace daemons (such as usb-role-switch), or enable MCU firmware to support role switching?4. Is automatic role detection via the Type-C controller supported purely in A35/Linux setup, or is MCU firmware required? The device tree includes usb-role-switch and a u

Hello STMicroelectronics Community:I would like to ask how to burn the system without using STM32CubeProgrammer. My chip is stm32mp135-AAE3. Thanks,Ivy7

My board (STM32MP135D) useTIM2 to count the external clock.PE15 cannot work properly, but PA15 works normally. // ok tim2_pins_mx: tim2_mx-0 { pins { pinmux = <STM32_PINMUX('A', 15, AF1)>; /* TIM2_ETR */ }; };  // not work tim2_pins_mx: tim2_mx-0 { pins { pinmux = <STM32_PINMUX('E', 15, AF1)>; /* TIM2_ETR */ }; }; 

Hello STM32 Community,I’m currently working with the STM32MP135D-FK (Boyard) board and trying to build a Weston image using a custom machine configuration. I’m following the official guide: :link: https://wiki.stmicroelectronics.cn/stm32mpu/wiki/How_to_create_your_own_machine. After compiling with the STM32 starter package, I successfully generated the required folders and files. However, when I attempted to generate my custom image using CubeMX device tree, I encountered an issue. The generated build doesn’t contain the expected folders and files, and I received the following warning: WARNING: st-image-weston-1.0-r0 do_create_flashlayout_config: >>> Cannot generate FlashLayout_board.tsv file: the arm-trusted-firmware/tf-a-stm32mp135f-studyproject1-mx-opteemin-program/fsbl_boot.bin is missing in the deploy folderCould anyone assist in resolving this issue or provide guidance on how to properly include the necessary files for my custom image generation?Thank you in ad

It looks like this commit reverted the hashes for meta-st-stm32mp-addons and meta-st-scripts.The revert for meta-st-stm32mp-addons is particularly problematic because the commit pointed to by the v6.0.2 manifest has LAYERSERIES_COMPAT_stm-st-stm32mp-mx = "mickledore", which breaks the build for v6.0.2, which requires "scarthgap". Am I missing something?

Dear STMicroelectronics Support Team,I am currently working with the STM32MP257F-EV1 evaluation board and have encountered a discrepancy in the user manual (UM3359, Rev 2, October 2024) concerning the GPIO mapping of the USER2 button.In Table 8 of the manual, the USER2 button (B4) is listed as connected to PA13. However, Table 32 correctly indicates that the USER2 button is connected to PG8, which aligns with the board's schematic and my practical observations. Pressing the USER2 button triggers the expected behavior associated with PG8, while PA13 does not respond as described.This inconsistency could potentially lead to confusion for developers referencing the manual. I kindly request that this discrepancy be reviewed and corrected in future revisions of the documentation.Thank you for your attention to this matter.Best regards,Adnanps: I could not find anyway to send a correction request to any emails, so here it is for everyone to know in advance.

Hi,I've lost the power brick for my STM32MP15X-EVAL board. It's a 5v-3a barrel connector, but I don't know the polarity and it's not written on the board or anywhere.Does anyone know where I can find a replacement, or the exact spec of the power brick so that I can find another one ?

Platform Details:Board: STM32MP257-dk and STM32MP257-ev1 seriesOS: Linux (Debian-based, provided by STM)Architecture: ARM64.NET Version: .NET SDK 8.0.407 (linux-arm64)SCADA System: Rapid SCADA (runs as a systemd service)Description:I'm trying to run a .NET 8-based SCADA application (ScadaAgentWkr.dll) on my STM32MP2 embedded Linux system. However, the application crashes when launched via systemd. Here’s what I’ve done and the issues I’m facing:What I Tried:Installed .NET SDK 8.0.407 for linux-arm64 from Microsoft.Installed libicu packages:libicudata74 libicuuc74 Configured systemd service at /etc/systemd/system/scadaagent6.service.Added environment variables to support ICU: Environment=DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=1 Environment=LD_LIBRARY_PATH=/usr/lib/aarch64-linux-gnu Also tried using a wrapper script to export these before calling dotnet.Error Logs:From systemctl status scadaagent6.service: Main PID: XXXX (code=dumped, signal=ABRT) Failed to start Rapid SCADA Age

We are following the steps mentioned in this link How to measure the DDR throughput - stm32mpu.However , stm32_ddr_pmu.py is not found anywhere Please point us to stm32_ddr_pmu.py.

Could you please clarify the pinctrl_z assignment in the device tree?The thing is, OP-TEE panics in shared_resources.c:142 <get_gpioz_nbpin> when I don't define in the device tree something like this:&pinctrl_z { st,package = <STM32MP_PKG_AC>; gpioz: gpio@54004000 { status = "okay"; ngpios = <8>; gpio-ranges = <&pinctrl_z 0 400 8>; };};Even though this is an assignment for AC package, and not the AB I have.

I am working with openSTLinux as below:- oe-manifest: TAG openstlinux-6.6-yocto-scarthgap-mpu-v25.03.19- Hardware: STM32MP257F-DK- Image: st-image-weston- Secure boot is enable and device is closed (BSEC_STATE_SEC_CLOSED)- Remove Debug Support in Linux Device tree as KYAO suggested in this topic I ran command xtest. The command is provides by a recipe optee-test_4.0.bb in meta-st-openstlinux. I found that many test cases are failed. They are related to pcks11. I attached the log file while running xtest.28179 subtests of which 33 failed 134 test cases of which 29 failed 0 test cases were skipped TEE test application done!Is there any problem with OPTEE OS? Please help me solve the problem or give suggestions to solve this problem.  

Moved from the MCUs section - STM32MP157F is an MPU (as the title says!)Hello!I'm building battery powered device and considering STM32MP157F.Looking at the mainline upstream linux kernel(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)I don't see device tree for this board, only for stm32mp157c (stm32mp157c-dk2.dts)Can you please tell what's the status of upstreaming support for STM32MP157F, maybe there is some process already. If yes, can you send me links to LKML patches?I've also checked device trees difference between C and F in your repo and it looks pretty much the same, will it work if I just copy paste the device tree from https://github.com/STMicroelectronics/linux/blob/v6.6-stm32mp/arch/arm/boot/dts/st/stm32mp157f-dk2.dts to mainline kernel and run it on STM32MP157F. Or some additional patches are required?Best regards!

Hi,in schematic of the STM32MP257-DK-board, I found the following resistors at the Ethernet interface being marked with "DNF":When looking at the board, these resistors are missing (which should be "DNP" in this case?).From my understanding of the wiring of the Ethernet interface, they should be there, but as one can see, the ETH-port on that DK-board is working properly also without them.So my question: what is the story behind these resistors which should be there and are missing while everything is working properly? Is there some other hack which makes these resistors obsolete/which replaces these resistors?Thanks! 

Hello,I use STM32MP1 SoC. According to wiki I can interrupt uploading images with STM32 Cube Programmer via USB-DFU: For USB boot, you can easily interrupt this command stm32prog usb 0by pressing Ctr + C in the console without U-Boot modification. U-boot also prints in its console "Ctrl+C to exit", but in fact I cannot send "Ctrl+C".  It looks like U-boot console is read-only while uploading via USB-DFU.  What is wrong ?At normal boot (from eMMC), I can interrupt U-boot loading and use console perfectly.  I use minicom for U-boot console

Hi,I'm trying to download SDK version 5.10 to build the version of Linux kernel used in our product after some years, i understand the file we need is en.SDK-x86_64-stm32mp1-openstlinux-5.10-dunfell-mp1-21-11-17.tar.xzunfortunately I get V6.x regardless of what I select on the download page. Would someone have a link to this file? (it's almost a gig)Thanks Simon Fisher

I have a custom yocto project based on stm32mp157c. I have developed the bootloader and linux kernel.I have display functionalty and display is working perfectly. But now I am changing the display, because the display will be discontinued. The device tree setup for the display is:&dsi { #address-cells = <1>; #size-cells = <0>; status = "okay"; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; dsi_in: endpoint { remote-endpoint = <&ltdc_out_dsi>; }; }; port@1 { reg = <1>; dsi_out: endpoint { remote-endpoint = <&dsi_panel_in>; }; }; }; panel-dsi@0 { compatible = "orisetech,otm8009a"; reg = <0>; rotation = <0>; address_mode = <0>; power-supply = <&v3v3>; status = "okay"; port { dsi_panel_in: endpoint { remote-endpoint = <&dsi_out>; }; }; }; };This configuration is working perfectly fine. As this display will be discontinued, we decided f

This info i have got through chatgpt is this true?                                                                                                           The STM32MP1 Distribution Package (OpenSTLinux) traditionally supports Qt 5.15.x, with Qt 5.15.13 being the latest version officially integrated into the ecosystem. This version is commonly used in development environments for STM32MP1 devices.​For newer versions of Qt, such as Qt 6.x, STMicroelectronics has introduced the X-LINUX-QT Expansion Package. However, as of the latest updates, this expansion package is primarily designed for the STM32MP2 series and is not yet fully functional with the STM32MP1 series. Therefore, if you're working with STM32MP1 devices, the

I have created a button in qt when I click on the button it has to create a pdf and also display the pdf.i am developing an application where i have to store the user data in pdf called report and later view it please give me the steps on how to perform this and any examples related to it 

Hello,I was writing an application interacting with the default firmware on the STEVAL-STLKT01V1 in python using the Blue-ST-SDK and it was working fine (https://github.com/STMicroelectronics/BlueSTSDK_Python/tree/master).    My teammate then flashed the FP-SNS-ALLMEMS1 firmware on the tile and now the script I wrote using the Blue-ST-SDK-Python cannot discover it (the example_1.py now simply times out) even though the device MAC address can be found with bluepy.  It gives this error when trying to add the node by the MAC address:AM1V420: "Manufacturer specific data" must be of length "7" or "13", not "15".  The board is discoverable and usable by the ST BLE Sensor app.  Maybe the FP-SNS-ALLMEMS1 is only compatible with IOS/Android versions of the SDK?    Which firmware is compatible with the Blue-St-Protocol-Python?  And which firmware is default flashed onto the Sensortile?  I simply need to read accelerometer and gyroscope

I am working with openSTLinux as below:- oe-manifest: TAG openstlinux-6.6-yocto-scarthgap-mpu-v25.03.19- Hardware: STM32MP257F-DK- Image: st-image-westonWhen the system starts up I see some error messages like this:Starting kernel ... I/TC: Secondary CPU 1 initializing I/TC: Secondary CPU 1 switching to normal world boot I/TC: Reserved shared memory is disabled I/TC: Dynamic shared memory is enabled I/TC: Normal World virtualization support is disabled I/TC: Asynchronous notifications are enabled [ 0.000000] [SCMI] channel: Cmd [740 (0x14:0x7)] returned error (-8) [ 0.000000] [SCMI] channel: Cmd [741 (0x14:0x7)] returned error (-8) [ 0.000000] [SCMI] channel: Cmd [742 (0x14:0x7)] returned error (-8) [ 0.000000] [SCMI] channel: Cmd [743 (0x14:0x7)] returned error (-8) [ 0.000000] [SCMI] channel: Cmd [744 (0x14:0x7)] returned error (-8) [ 0.000000] [SCMI] channel: Cmd [745 (0x14:0x7)] returned error (-8) [ 0.000000] [SCMI] channel: Cmd [746 (0x14:0x7)] returned error (-8) [ 0.000000] [S

We are pleased to announce that the minor version 6.14.1 of STM32CubeMX is available. What is new in 6.14.1: SAI settings not displayed in the configuration tab of STM32H7Bxxx devices: After upgrading to STM32CubeMX 6.14.0, the SAI tab configuration is lost. DCMI building problems in STM32N6 projects: DCMI initialization instructions are not generated for both secure and nonsecure domains. Failure in generating the initialization instructions for projects using the DCMIPP feature in CSI mode. ULPI_Clock initialization issues for STM32F7 projects using the USB_OTG_HS feature: STM32CubeMX generated code omits the ULPI_Clock initialization or adds it when it is not needed. STM32WBA63xx project generation issues: STM32_WPAN advertising menu elements not updated correctly. Inaccurate warnings about non configured peripherals. IOC files failing to reopen, reverting to the home screen. stdio.h inclusion error for STM32U5 projects: A preprocessor error occurs in the compilation

Hi ST Community,I’m working with the STM32MP135D-FK (Boyard) board and trying to build a Weston image using a custom machine configuration, following this official guide::link:https://wiki.stmicroelectronics.cn/stm32mpu/wiki/How_to_create_your_own_machineI’m using OpenSTLinux (scarthgap) and everything builds fine, but I get this warning during the final step:WARNING: st-image-weston-1.0-r0 do_create_flashlayout_config: >>> Cannot generate FlashLayout_board.tsv file: the arm-trusted-firmware/tf-a-stm32mp135f-studyproject1-mx-opteemin-program/fsbl_boot.bin is missing in deploy folderIt says fsbl_boot.bin is missing and so the FlashLayout_board.tsv file can’t be created. The build itself completes successfully otherwise.     My questions:How can I fix this issue and generate the missing fsbl_boot.bin?Do I need to enable or configure something extra in trusted-firmware-a or optee-os?Is there anything

 Hello,I’m trying to enable UART6 on the STM32MP257F-EV1 board using the A-35 processor. UART6 is connected to PF13 (TX) and PF14 (RX) on the extended GPIO. I’m using the OpenST Linux distribution and STM32CubeMX.What I’ve Tried:Configured UART6 in CubeMX:Set runtime context to A35/Linux with PF13 and PF14 assigned.Generated the device tree, but UART6 doesn’t show up in /dev/ttySTM*.Device Tree Configurations:Updated as follows:    &usart6 { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&usart6_pins_a>; };Pinmux for USART6_TX and USART6_RX is set to AF7.Checked Linux:Ran ls -l /dev/ttySTM* and dmesg | grep ttySTM but found no output for UART6.CubeMX Pin Conflicts:PF13 and PF14 conflict with other peripherals like ETH3_PHY_INTN. Disabled conflicting peripherals but still no success.Questions:How can I make UART6 appear as /dev/ttySTM6 in Linux?Are there additional steps needed in the device tree or Linux configuration?Has anyone successf

Hi all.I am confused about how I am supposed to provide power to the STM32MP257F-DK as it seems I am not providing enough power to the board when connecting the board to my PC via the STLINK/Power connector as the red Power LED is on and the Green LED that is meant to be on when the board is powered up is off.I am using a USB 3.0 port from my PC, I was able to successfully power the board to use the DFU function with an PD USB prower brick pluged into STLINK/Power while I had a USB cable connected from my PC to the USB DRD port.How am i ment to power this board when using STLINK for serial use when I cant plug in a PD power brick at the same time as use STLINK ?