Get ready for the STM32 Summit 2026 | Online, November 3
Join conversations with your peers and ST experts. Explore the full potential of STM32 microprocessors for your embedded design.
Most recent activity
Hello We have custom board with STM32MP257DAI3 Processor.We would like to test it using Buildroot. Could you please advise whether it is feasible to use the STM32MP257F-EV1 Buildroot configuration for testing our STM32MP257DAI3-based custom board? Additionally, we would appreciate any recommendations or necessary modifications required to ensure compatibility. Thanks & RegardsAkshitha Pattem
I'm running a small STM32-board with the original STLinux. This board comes with some kind of USB OTG port. Now I want to configure this port to let it act as serial device, means when I connect it to an other PC via that USB-port, I like to appear it as COM or /dev/ttY* there.What I have so far is a script which should do the trick:mkdir -p /sys/kernel/config/usb_gadget/g1 cd /sys/kernel/config/usb_gadget/g1 echo 0x1111 > idVendor echo 0x2222 > idProduct mkdir strings/0x409 echo "0DEADBEEF" > strings/0x409/serialnumber echo "Me, myself and I" > strings/0x409/manufacturer echo "MyDevice" > strings/0x409/product mkdir configs/c.1 echo 120 > configs/c.1/MaxPower modprobe usb_f_acm mkdir functions/acm.0 ln -s functions/acm.0 configs/c.1 echo 0000:01:00.0 > UDCThe mkdir command works only when I execute this as root and with sudo. But my problem is the last line: It always fails with ansh: write error: Device or resource busyHere neither root nor sudo nor both do help.
I am working through the MPU Wiki guide Develop on the Cortex-M33 for STM32MP257FI am running the FlashLayout_sdcard_stm32mp257f-dk-ca35tdcid-ostl-m33-examples-optee.tsv image.I can successfully load and debug binaries for the M33 and the virtual UART behaves as expected. However, after adding the __LOG_TRACE_IO_ macro, any attempt to read from /sys/kernel/debug/remoteproc/remoteproc0/trace0 returns: Trace not availableFrom minicom, I can see that the log messages are correctly sent to /dev/ttyACM1I've observed the same behaviour for both the DK and EV kits.Having the log output to the remoteproc trace would be very useful during development. Any advice on getting this working would be great!Thanks in advance.
HelloI am working on the multi-system in STM32MP257-EV board, I had modified the tsv file to prepare a double system A and B. If using the default metadata.bin file, the A system will be run always. Now I want the B system to be run, I need to modify the metadata.bin file, for example change the "accepted" of B bank to false:If the status of img_0_bank_1 is trial, the B bank system will be run when ev board power up, isn't it?how to modify the metadata.bin?If the status of img_0_bank_1 has been modified to trial, and the B bank system run up normally, is the status of img_0_bank_1 modified automatically by linux? how does the linux system modify the metadata.bin file?
Hello,I want to use a virtual keyboard on STM32MP257 now. Due to the possibility of porting some non Qt applications in the future, it is advisable to avoid using Qt's built-in virtual keyboard as much as possible. Do you have any ideas.My main application requires the use of Wayland2. We plan to port non Qt applications in the future3. What virtual keyboard scheme is used in the facerecognition example?https://wiki.stmicroelectronics.cn/stm32mpu/nsfr_img_auth.php/0/06/Cpp_ovx_face_recognition_application_enrollment.png
Hello, I need some advice.I would like to know if the STM32MP135 processor is capable of reading a USB UVC camera through its USB host port. I currently have a USB camera based on the OV9734 sensor.I know the documentation states that the processor supports an 8- to 16-bit camera interface, but in my case, I need to use a USB camera.Can someone clarify if this is possible?
Hello We are currently working on reading NOR Flash(MT25QL128) device ID through OSPI interface on our custom board with STM32MP257D processor. During our testing, we observed an issue where no data appears to be written into the OCTOSPI Data Register (OCTOSPI_DR), even though we can see signals on the data lines of the NOR Flash chip. Thanks & RegardsAkshitha Pattem
i am using stm32mp135-dk board . i have installed the STM32MP1-Ecosystem-v5.0.0 Starter Package now i want to install python how i can install ?
Hi all,Following the guide at https://wiki.st.com/stm32mpu/index.php/How_to_create_your_own_machine, I generated Device Tree .dts files using STM32CubeMX (version 6.14.1) for the STM32MP257F-EV1 board (selected via Board Selector) in a project named demo, aiming to use a custom device tree setup.In CubeMX, I set the project location to:/Distribution-Package/layers/meta-st/meta-st-stm32mp-addons/mx(I manually created the mx folder beforehand.)This resulted in the expected output files being generated under:Distribution-Package/layers/meta-st/meta-st-stm32mp-addons/mx/demo ├── CA35 │ ├── DeviceTree │ │ └── demo │ │ ├── kernel │ │ │ ├── Makefile │ │ │ ├── stm32mp257f-demo-mx.dts │ │ │ └── stm32mp257f-demo-mx-resmem.dtsi │ │ ├── optee-os │ │ │ ├── conf.mk │ │ │ ├── stm32mp257f-demo-mx.dts │ │ │ ├── stm32mp257f-demo-mx-rcc.dtsi │ │ │ ├── stm32mp257f-demo-mx-resmem.dtsi │ │ │ └── stm32mp257f-demo-mx-rif.dtsi │ │ ├── tf-a │ │ │ ├── stm32mp257f-demo-mx.dts │ │ │ ├── stm32mp257f-demo-mx-fw-conf
Hi I am currently working with an STM32MP135F-DK development board. My goal is to compile and execute a simple C program on this board.While I have successfully booted the board and updated the operating system using my laptop, I am finding it difficult to locate a clear, step-by-step guide that explains how to compile and run a C program (for example, a basic "Hello, World!" program) on the STM32MP135F-DK from the very beginning.Could you please point me towards any helpful articles, tutorials, or resources that detail this process? Any assistance you can provide would be greatly appreciated.Thank you for your time and consideration.RegardsGirish
how to configure the device tree(gpios,timers and other peripheras) of STM32MP257F-EV1 for yacto build custom linux ,core-image-full-cmdline
I am about to integrate Ezurio sna module If 513 with the STM32MP257F-EV another to provide wireless capabilities to my board. does any one try this before for any assistance. I am using mini PCIE TO M.2 adapter to connect. so if there is any to assist me with a complete guide , I will appreciate, Thank you.
Moved from MCUs forum: STM32MP13 is an MPU - not an MCU.Hello Everyone,I hope you’re doing well. I’m encountering a problem when trying to boot Linux directly instead of U-Boot on our STM32MP135F-DK board. Below is a summary of what I’ve done and the error I see:1. Procedure followedBuilt a new FIP binary and tf-a with the recommended changes and flags:-> fiptool update --fw-config stm32mp135f-dk-fw-config.dtb --hw-config stm32mp135f-dk.dtb --nt-fw Image fip-stm32mp135f-dk-optee-sdcard.binModified the TSV in the starter package to replace u-boot.bin with my Linux image and updated the FIP entries as follows:2. Observed output:NOTICE: CPU: STM32MP135F Rev.YNOTICE: Model: STMicroelectronics STM32MP135F-DK Discovery BoardNOTICE: Board: MB1635 Var1.0 Rev.E-02INFO: PMIC version = 0x21INFO: Reset reason (0x134):INFO: IWDG1 Reset (rst_iwdg1)INFO: FCONF: Reading TB_FW firmware configuration file from: 0x2ffe0000INFO: FCONF: Reading firmware configuration information for: stm
We are following the steps mentioned in this link How to measure the DDR throughput - stm32mpu.However we are facing the below error while trying to use stm32_ddr_pmu We inserted the lkm module stm32_ddr_pmu.ko using modprobe. The lsmod lists the stm32_ddr_pmu The zcat shows that CONFIG_STM32_DDR_PMU is enabledperf list does not show the stm32_ddr_pmu Can you please help us to find what are we missing here?
Had a working yocto build of st-image-weston for a custom machine based on 157-DK2, then I followed the simple instructions for update from openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06 to 6.0.3 (v25.04.30) -- just a new repo manifest tag...https://wiki.st.com/stm32mpu/wiki/STM32_MPU_OpenSTLinux_release_note#v6-0-3repo sync ran without errorsbut now `bitbake st-image-weston` fails: ERROR: Nothing RPROVIDES 'linux-firmware-bluetooth-bcm43xx' (but /home/aescape/Documents/projects/pensa/evon/code/dist-package/layers/openembedded-core/meta/recipes-core/packagegroups/packagegroup-base.bb RDEPENDS on or otherwise requires it) NOTE: Runtime target 'linux-firmware-bluetooth-bcm43xx' is unbuildable, removing... Missing or unbuildable dependency chain was: ['linux-firmware-bluetooth-bcm43xx'] NOTE: Runtime target 'packagegroup-base-extended' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-base-extended', 'linux-firmware-bluetooth-bcm43xx'
I have created basic image with DISTRO=openstlinux-weston MACHINE=stm32mp25-disco, and tried to add device tree files and I have tried to switch to new device tree variant via configuration, and I am planning to emmc to flash the image, I have done integration for all the files in the new device tree folder. Once I try to build with new configuration, I am facing issues during the build process.
Hi all,i'm developing firmware for STM32MP135F-DK board to communicate with some external chips in I2C1.No problems if I communicate with other I2C chips (clockgen, eeprom, io expander).Communicating with the RTC PCF85063 chip happens that no problems if I send write command.If I send a read registry command the I2C bus stucks with the SCL and SCK lines at low level. And the bus stays locked until MP135 reset. If i only power down, than power up, the PCF chip, the SDA line goes up but the SCL line stays low so again i2c locked.I attached the scope screeshot: in particular I see the initial write/set current register acknoledged; when I send the read command I see the read packet with the chip address (0x51+1 bit high for read) but it is never acknoledged cause the lines levels..The problem is always present even I change the register to read.For each kind of communication I'0m using the HAL_I2C_* functions.Any idea?Thanks
Dear ST Team,I am currently working with the STM32MP257x-EV1 evaluation board to validate the BSP, following the official setup procedure provided on your Wiki.At this stage, I am verifying OpenAMP communication between the Cortex-A35 and Cortex-M33 cores. However, I have encountered an issue where the VIRT_UART0_RxCpltCallback function in the M33 firmware does not produce any output, and it appears that the callback might not be triggered.I would appreciate your assistance in clarifying the following:Are there any specific operational steps I might have missed?Could there be any misconfigurations in my current setup?How can I verify whether VIRT_UART0_RxCpltCallback is actually being executed?Thank you for your support. void VIRT_UART0_RxCpltCallback(VIRT_UART_HandleTypeDef *huart){LOG_INFO("UART0 RX Callback, %d bytes received", huart->RxXferSize);VirtUart0ChannelRxSize = huart->RxXferSize < MAX_BUFFER_SIZE? huart->RxXferSize : MAX_BUFFER_SIZE-1;memcpy(Vi
I am working on a STM32MP157D-DK1 board, and I am trying to follow the guide from the wiki to start the coprocessor from u-boot:https://wiki.st.com/stm32mpu/wiki/How_to_start_the_coprocessor_from_the_bootloader#Start_from_the_bootcmd I have pulled the u-boot source code:devtool modify u-boot-stm32mp And modified include/configs/stm32mp15_st_common.h to contain: #define CONFIG_EXTRA_ENV_SETTINGS \STM32MP_MEM_LAYOUT \STM32MP_BOOTCMD \STM32MP_PARTS_DEFAULT \BOOTENV \"m4fw_name=my-m4-fw.elf\0" \ "m4fw_addr=${kernel_addr_r}\0" \"boot_m4fw=rproc init; rproc load 0 ${m4fw_addr} ${filesize}; rproc start 0\0" \ "boot_m4_mmc0=if load mmc 0#bootfs ${m4fw_addr} ${m4fw_name} ; then run boot_m4fw; fi;\0"\ "bootcmd=echo \"Loading the firmware!\"; echo \"ELF files is: ${m4fw_name}\"; run boot_m4_mmc0; run bootcmd_mmc0\0" I have rebuild the distribution as:bitbake st-image-weston (No issues or erros) and uploaded all image files via CubeProgrammer u
Hi,I have STM32MP257F-DK and Yocto linux installed to it.I have tried to get spidev working on SPI6, but no luck so far./dev/spidev6.0 won't appear to filesystem.Has anyone tried this combo and got it working?Any working SPI configuration would be highly appreciated.
Dear ST Developer Support,I am currently developing in a bare-metal environment on the STM32MP257F-EV1. I’ve encountered an issue where I am unable to write to RAM or flash memory."Despite using STM32CubeIDE (with ST-Link), memory access to RAM and flash fails, and the binary does not run as expected, even on the Cortex-M33 core."Could you please advise whether it is possible to write and execute a binary directly on the Cortex-M33 core, either using STM32CubeIDE or through other methods? Are there specific initialization steps or boot configurations required for bare-metal development on this platform?Alternatively, is development on this board only supported through OpenSTLinux? Thank you for your support.Best regards,Dahun
Hi everyone, Hi everyone,I’m currently designing a custom board based on the STM32MP157FAC1 evaluation board, and as part of the process, I’m working to estimate the power budget for the design.However, I’m finding it difficult to locate clear information on load current requirements in the STM32MP1 datasheet, likely due to the MPU’s complex architecture.Does ST provide any power estimation tools or official guidelines to help calculate power consumption when transitioning from the evaluation board to a custom design?Any advice or references would be greatly appreciated. Thanks in advance!
Hello~ I am using the Mickledore version of Yocto. I want to directly apply the following:meta-st-x-linux-rt-openstlinux-6.1-yocto-mickledore-mpu-v24.06.26 to DISTRO = openstlinux-weston. DISTRO=openstlinux-weston MACHINE=mymachine source layers/meta-st/scripts/envsetup.shInstead of using the new DISTRO = openstlinux-rt,I directly run bitbake, but the RTpatch did not take effect. I only succeeded after changing SRC_URI:append:stm32mprtcommon to SRC_URI:append:stm32mp2common. May I ask if there are any other issues with this approach?Or is there any better way to handle this problem?
Hello,I am trying to use the DDR test suite from Cube IDE with a custom board based on the STM32MP257FAI3 with 32Gb of LPDDR4 (MT53E1G32D2FW-046 WT:B). The board doesn't have engineering boot available, but it does have USB/UART boot, so I have been attempting to use SYSRAM Loading in the DDR Test Suite. However I have been getting "This Port Com Is Not Responding" errors when trying to connect. The steps I have taken are as follows: 1. Clone DDRFW-UTIL and edit `DDR_Tool/STM32MP257F-EV1/Inc/stm32mp_util_conf.h` to change the UART and PMIC settings:/* UART related configuration */ #define UTIL_UART_INSTANCE UTIL_UART9 #define UTIL_UART_TX_PIN UTIL_PIN13 #define UTIL_UART_TX_GPIO_PORT UTIL_GPIOD #define UTIL_UART_TX_AF GPIO_AF6_UART9 #define UTIL_UART_RX_PIN UTIL_PIN14 #define UTIL_UART_RX_GPIO_PORT UTIL_GPIOB #define UTIL_UART_RX_AF GPIO_AF6_UART9 #define UTIL_UART_BAUDRATE 115200 #define UTIL_UART_WORDLENGTH UART_WORDLENGTH_8B #define UTIL_UART_STOPBITS UART_STOPBITS_1 #def
I am using the STM32MP257F-DK with a WiFi-BT module. WiFi is connected via SDIO pins and Bluetooth is connected using UART6 pins through the 40-pin header.I am testing the HFP profile on the BT module. When I run the dial-number script from the ofono test script, the call is placed successfully, but there is no audio during the call.PipeWire, WirePlumber, and oFono are all running successfully, but when dialing a number, I get the following log: root@stm32mp2-e3-d2-9e:/usr/lib/ofono/test# ./dial-number xxxxxxxxxxofonod[1675]: src/modem.c:get_modem_property() modem 0xd3664a0 property SystemPathUsing modem /hfp/org/bluez/hci1/dev_5C_ED_F4_5A_72_AEofonod[1675]: src/voicecall.c:synthesize_outgoing_call() Registering new call: 1/hfp/org/bluez/hci1/dev_5C_ED_F4_5A_72_AE/voicecall01ofonod[1675]: src/voicecall.c:ofono_voicecall_notify() Got a voicecall event, status: dialing (2), id: 1, number: 9651273221 called_number: , called_nameofonod[1675]: src/voicecall.c:ofono_voicecall_notify() F
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.