STM32 MPUs Products and hardware related

Hi,I'm working on enabling USB 3.0 support for the STM32MP257 in U-Boot and need a suitable driver. I’ve attempted to modify the U-Boot kernel driver to support USB 3.0, but I’m running into issues with the PLL configuration.The problem seems to stem from setting up the correct clocking for the USB3 PHY. Despite adjusting the PLL parameters, I’m not getting stable operation, and the PHY doesn't initialize correctly. If you have any insights on configuring the PLLs for USB3 in U-Boot on STM32MP257, or if there's an existing implementation I could reference, I’d really appreciate your guidance.Thanks in advance!Here is my function.static int stm32_combophy_pll_init(struct stm32_combophy *combophy) { int ret = 0; u32 refclksel = 0, pllmult = 0, propcntrl = 0, sr = 0; unsigned long clk_rate = 0; int retry; const int max_retries = 5; /* get reference clock rate */ if (combophy->pad_clk) { clk_rate = clk_get_rate(combophy->pad_clk); printf("PADCLK rate: %lu\n", clk_rate); } else { clk

I am connecting my STM32MP257F-EV1 board to rpi Hailo 8 board via Mini Pcie to M.2 key M adapter. The board is not getting detected even though clock and reset signals are coming properly.I am using the stm32mp257f-ev1.dts (default device tree) and also sharing my device tree pci node below&pcie_rc {pinctrl-names = "default", "sleep";pinctrl-0 = <&pcie_init_pins_a>;pinctrl-1 = <&pcie_sleep_pins_a>;reset-gpios = <&gpioj 8 GPIO_ACTIVE_LOW>;wakeup-source;wake-gpios = <&gpioh 5 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>;status = "okay";};I am getting this error as given below:-root@stm32mp2:~# lspci00:00.0 PCI bridge: Synopsys, Inc. Device 0550 (rev 01)root@stm32mp2:~# dmesg | grep pci[ 1.561630] stm32-pcie 48400000.pcie: host bridge /soc@0/rifsc@42080000/pcie@48400000 ranges:[ 1.570082] stm32-pcie 48400000.pcie: IO 0x0010010000..0x001001ffff -> 0x0010010000[ 1.586511] stm32-pcie 48400000.pcie: MEM 0x0010020000..0x0017ffffff -> 0x0010020000[ 1.60301

Hello all, I am following the following guide: https://wiki.stmicroelectronics.cn/stm32mpu/wiki/STM32MP25_Discovery_kits_-_Starter_Package In order to bring up a STM32MP257F-DK board and am running into a problem when I try to use the Programmer to flash the board. It gets to Partition 0x3 and at 31% fails saying it failed to download sector[0]. Specifically this is the output in the terminal:-------------------------------------------------------------------STM32CubeProgrammer v2.20.0------------------------------------------------------------------- USB speed : High Speed (480MBit/s)Manuf. ID : STMicroelectronicsProduct ID : DFU in HS Mode @Device ID /0x505, @Revision ID /0x2000SN : 003700494236501700363847DFU protocol: 1.1Board : --Device ID : 0x0505Device name : STM32MP23xx/25xxDevice type : MPURevision ID : --Device CPU : Cortex-A35Start Embedded Flashing service Opening and parsing file: tf-a-stm32mp257f-dk-optee-programmer-usb.stm32Memory Programming ...File : tf-

Hello everyone,I’m currently developing a custom board based on STM32MP151A, and I’ve successfully built my Open ST Linux  (Yocto Scarthgap / v6.6) image using my own Device Tree generated from STM32CubeMX and further customized for our hardware.The build process completes successfully — both U-Boot and Linux kernel compile without errors, and the final image is correctly produced.However, when I try to flash the image to the target using STM32CubeProgrammer, the upload fails and I get the error log attached below.12:56:16:446 : USB speed : High Speed (480MBit/s)12:56:16:446 : Manuf. ID : STMicroelectronics12:56:16:446 : Product ID : DFU in HS Mode @Device ID /0x500, @Revision ID /0x000012:56:16:446 : SN : 003E00273030510D3434343712:56:16:446 : DFU protocol: 1.112:56:16:446 : Board : --12:56:16:446 : Device ID : 0x050012:56:17:452 : Start Embedded Flashing service12:56:17:452 : sending a set alternate setting request with index: 512:56:17:453 : receiving packet12:56:17:454 : DFU s

Hi ST Community,I’m using the STM32MP257F-DK board and successfully followed this guide: Modify, rebuild and reload the firmware Everything worked fine during the initial setup and firmware modification. Now I’m trying to flash a new image to the SD card and connect to the board again, but I’m unable to establish a connection via ST-LINK. Here’s the error I get:ST-LINK SN : 003E004A3234510636303532 ST-LINK FW : V3J16M8B5S1 Board : STM32MP257F-DK Voltage : 3.29V Error: Unable to get core ID Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug AuthenticationI’ve set the boot switches to the OFF position (boot from UART/USB), and I suspect that during the previous steps, Secure Boot may have been enabled or modified without me realizing it. Could this be preventing me from accessing the board now?I’ve already tried:Updating ST-LINK firmware“Connect under reset” modeChecking physical connections and voltageIs there

Hello,we have product based on a STM32MP157 running Linux. The distribution is based on Yocto kirkstone and we are using a 6.1.82 Kernel. For the MP1s' GPU we use the open source entaviv driver that ships with this kernel. The device has a graphical user interface that is displayed on 4" display. The device can be operated remotely via a webbrowser as well.The visualization of our application is handled by a web gui so that we can provide a uniform user interface to users independet whether they log in via a browser on a host PC to the device or operate the device with the display. For this reason the GUI on the local device is in fact our web gui running in a browser in kiosk mode. For this local browser in kiosk mode we use the  Cog browser from the webkit project (version 0.18.2 with wpewebkit 2.42.5).Long story short: With this setup we are struggeling with performance issuses when operating the device locally with the cog browser. From my understanding webkit currently suppor

Honey, I purchased an STM32MP257-DK development board. I inserted a 16GB SD card, powered it with a 5V power supply, and connected the USB interface to the computer's USB port. After powering on, the COM indicator flashes red and yellow, and it cannot function properly. What could be the reason? My power supply current is sufficient.

 Hello ST Community,I am currently working on a custom board based on STM32MP257FAI3, derived from the STM32MP257F-EV1 evaluation board.We initially built our own custom image and successfully enabled several peripherals (SPI, USART, Timers, ADCs, and Interrupts) and tested on evaluation board as well.Now, while adapting the configuration for our custom hardware, I have modified all pin assignments according to the alternate functions listed in the datasheet and reference manual.Most of the pins are configured correctly and appear as expected in the system.However, I’ve noticed that certain pins (for example, PZ7 and PZ8, which were used for LPUART1 on the EV1) and some other pins in list are still shown as “consumer = kernel” in the output of:  gpioinfo -c /dev/gpiochip11even though I have:Removed their references from TF-A, U-Boot, and Linux kernel device treesDeleted their entries from the corresponding pinctrl and pinmux configurationsDespite these removals, the

Hi,I'm seeking information on where to purchase alternative LCD touchscreen sizes that compatible with the STM32MP257F-EV1 evaluation board, beside the standard 7-inch touchscreen LCD (P/N: B-LVDS7-WSVGA). It appears that ST’s touchscreen uses a different LVDS touchscreen interface implementation compared to other display vendors, where video signals over LVDS are provided through one connector and the touch interface through a separate connector.Thank you in advance for your assistance.

As we are developing the camera streaming board for one of our client, I have the following queries:Both part numbers, STM32MP135DAG7 and STM32MP135FAG7 come in the TFBGA289 (9×9) package. Are the pinouts identical for both devices? can we interchange the part in PCB assembly?I believe only security features are add in FPlease share the OrCAD schematic library files for both MPUs — STM32MP135DAG7 and STM32MP135FAG7.

Hello everyone,I’m having trouble creating a custom image for OSD32MP157C-512-IAA and OSD32MP157F-512-BAA.When I try building the image for the 157C version using the Octavo tutorial [https://octavosystems.com/app_notes/stm32mp1-cubemx-tutorial-for-osd32mp15x/], the build fails..I’ve tried several combinations:-Base images for BRK and RED boards (tested with versions 3.0.0 and 3.1.0)-Different DTS/DTSI configurations for 153C, 157C, and 157F from the minimal setup-Compared SD card partition flags between the working stock image and mine - they match.I’ve attached my logs and short build notes for both the C and F versions.At this point, I’m out of ideas on what else to check or how to fix the build.If anyone could share a complete, working guide for building and flashing a custom image for these modules, that would be extremely helpful.Thanks in advance for your help!Best regards,Nenad

Hello ST Community,I'm using the STM32MP257F-DK MPU board and wanted to enable the USART6 interface. We can access it from the 40-Pin GPIO expansion header of the board.For this, I have enabled the 'status' node settings of the usart6 from the device tree (dts) file as mentioned below.serial@40220000 {compatible = "st,stm32h7-uart";reg = <0x40220000 0x400>;interrupts-extended = <0x1e 0x1d 0x04>;clocks = <0x16 0x116>;dmas = <0x1c 0x13 0x20 0x10012 0x1c 0x14 0x20 0x3021>;dma-names = "rx\0tx";access-controllers = <0x1b 0x24>;power-domains = <0x0c>;wakeup-source;status = "okay";pinctrl-names = "default\0idle\0sleep";pinctrl-0 = <0x34>;pinctrl-1 = <0x35>;pinctrl-2 = <0x36>;uart-has-rtscts;phandle = <0xe5>;};After setting 'status = okay' in the dts, I'm able to see the '/dev/ttySTM1' device entry on my board on bootup. Now, just to check the uart is enabled or not, I have looped back Tx-Rx pins of the GPIO expansion header and

Hi I am willing to build a camera with STM32MP2 & B-CAMS-IMX. I can not locate the CAD model in any of the design resources shared for MB1854 card. I need the CAD model (step file) for mechanical integration. Please help.

Hi, I have a custom board based on STM32MP257FAK3, based on STM32MP257EV1 evaluation board. My board has a rtl8367s ethernet switch connected on eth2 port though rgmii. I can communicate though mdio to the rtl8367s and configure it. We are using OpenWrt kernel and rtl8365mb driver though smi that seems to be the right one.But I can not make works eth2 is failing DMA every time. I will share you my logs and dts. Every idea is welcoming. Thank you! 

HI ST Community,I need to compare the DDR4 configuration data before and after DDR training. could you please guide me on how to retrieve the DDR configuration data after a successful boot of the STM32MP257F-EV1 Board.Thank you. 

Hello,We are currently working with STM32MP257F-EV1 evaluation board and attempting to enable I3C4 interface to communicate with LSM6DSV device. However, we are encountering the following error messages during boot:[ 3.474187] stm32-i3c 46080000.i3c: (i3c-0) address not acknowledged [ 3.478101] stm32-i3c 46080000.i3c: (i3c-0) address not acknowledged [ 3.484119] stm32-i3c 46080000.i3c: (i3c-0) address not acknowledged [ 3.490487] stm32-i3c 46080000.i3c: 1 target(s) assigned but 0 counted [ 3.497837] stm32-i3c 46080000.i3c: Failed to register I3C master: -22 [ 3.503626] stm32-i3c: probe of 46080000.i3c failed with error -22 [ 23.205576] stm32mp_pm_domain power-domain-d1: sync_state() pending due tocThis is an excerpt from dts. The following has been added.  &i2c8 { status = "disabled"; }; &i3c4 { pinctrl-names = "default", "init", "sleep"; pinctrl-0 = <&i3c4_pins_a>; pinctrl-1 = <&i3c4_init_pins_a>; pinctrl-2 = <&i3c4_sleep_pins_

Hello,I have developed a custom board using the STM32MP157DAC1. The pin layout is nearly identical to the STM32MP157-DK2 for all pins with the same name.I am trying to flash an SD card image using STM32CubeProgrammer, but I'm facing two critical issues.1. USB Device Not RecognizedMy primary issue is that the USB connection is not recognized by my PC at all when I try to connect in DFU mode. I cannot get any response from the device over USB.I have attached a schematic of my USB circuit. Please note that I initially had an error where the DP and DM lines were crossed, but this has since been corrected on the board. Despite the fix, the USB port remains unresponsive.2. UART Flashing Fails with Timeout ErrorAs a workaround, I attempted to flash the image via UART. The process starts, and the first stage bootloader (tf-a- ... .stm32) appears to download successfully. However, the process then fails with multiple timeout errors when trying to get the next phase.Here is the log from STM32Cub

Hello,I am working on evaluation board in that boot logs I am gettingNOTICE: Model:  STMicroelectronics STM32MP257F-ev1 Evaluation BoardNOTICE: Board : MB1936 Var1.0 Rev.D-01What should I do to remove this "NOTICE: Board : MB1936 Var1.0 Rev.D-01" line from my boot logs and Change the model to a custom name how can I do it I have made changes in stm32mp257f-ev1.dts files in tf-a-source, u-boot source and kernel source.

Hi, I'm pretty new to embedded development. I'm trying to set up a really basic 'Hello world' image for my M33 core on STM32MP257F-DK. My Linux A image has remoteproc set up, and rpmesgDmesg on linux host: [43834.220252] remoteproc remoteproc1: powering up m33 [43834.258170] remoteproc remoteproc1: Booting fw image zephyr_20251017_095646_e99be8ad.elf, size 1438504 [43834.262810] rproc-virtio rproc-virtio.2.auto: assigned reserved memory node vdev0buffer@812fa000 [43834.271543] virtio_rpmsg_bus virtio0: rpmsg host is online [43834.276502] rproc-virtio rproc-virtio.2.auto: registered virtio0 (type 7) [43834.286260] remoteproc remoteproc1: remote processor m33 is now up  However, Linux won't pick up the remoteproc msg endpoint and present it as I expect it to in /dev/ttyrpmsgI'm building into my zephyr image an overlay, a resource table, a main.c and a ipcc_shim to patch over what I think is a missing getChannelConfig.To be honest, I've made a lot of assumptions.

STM32MP151 VDDCORE voltage if device above 600Mhz (800Mhz)1 VDDCORE voltage if device above 600Mhz (800Mhz). Custom Boardsee attachedThe data sheet states 2 VDDCORE voltages depending on the clock speed of part and i think yoiu can also set the clock speed in software.Can I just use STM32MP151DAD1 ARM® Cortex®-A7 Microprocessor IC STM32MP1 1 Core, 32-Bit 209MHz, 800MHz 257-TFBGA (10x10) and VDDCORE at fixed 1.35VOR do I need a 1.2V VDDCORE and then switch it to 1.35V when I want to go faster.Will a STM32MP151DAD1 run on VDDCORE 1.2V if clock set slower?ThanksDOM   

Hi,we are developing a custom board based on the STM32MP157C. We would want to use several GPIOs for buttons. We have most of them working, but a couple GPIO pins do not yield input events to the Linux kernel.The problematic pins are PC1, PC2, and PH7.In U-Boot, I can read all these pins and they reflect the state of the button. Below is what happens reading the pin before pressing the corresponding button, while pressing it, and after releasing the button. So the button is connected to the CPU pins and is active high:QSMP U-Boot > gpio input gpioc1gpio: pin gpioc1 (gpio 33) value is 0QSMP U-Boot > gpio input gpioc1gpio: pin gpioc1 (gpio 33) value is 1QSMP U-Boot > gpio input gpioc1gpio: pin gpioc1 (gpio 33) value is 0QSMP U-Boot > gpio input gpioc2gpio: pin gpioc2 (gpio 34) value is 0QSMP U-Boot > gpio input gpioc2gpio: pin gpioc2 (gpio 34) value is 1QSMP U-Boot > gpio input gpioc2gpio: pin gpioc2 (gpio 34) value is 0QSMP U-Boot > gpio input gpioh7gpio: pin gpioh7

Can I install pyenv on my STM32MP257F-EV1 DK to manage python versions?I am currently running the starter package and have access to py 3.12.9I would like to run scripts with py v3.11.9At this stage I am not interested in updating the image - so please let me know what I can do as a work around. Thanks!

I know, it's probably a design flaw, but hear me out.I'm designing a board with an STM32MP135 (in the form of a Myir Tech SoM). I have both USB1, and USB2 configured as USB-A / host mode. There is also an FTDI chip attached to UART4 for a console.The problem that I'm having is that when I try to enter USB DFU mode (bootn = 0, 0, 0) it will only work if I connect through an OTG-style adapter to another USB-A port. The only way that I can get it to enumerate is if I connect USB2 (type A plug on the target) to a USB-C to A converter, and then to a USB-A port on the laptop. If I connect USB-A on the target to USB-C on the laptop it does not enumerate at all and if I connect via a powered HUB it gets stuck in some sort of enumeration loop.This is the first board revision and I did not expect to need USB-OTG so those pins are floating, which I'm guessing is what I've missed, but I can't find where it mentions how they are used in the documentation. I don't have any use for USB-OTG otherwise.

Hi,When transmitting data to the ttySTM0 port, the data goes to the UART4_TX pin connected to the JTAG virtual serial input. However, I need an available TTL serial port to communicate with a microcontroller. How do I enable the USART1 port connected to the PC0/PB0 pins?To which pins is the ttySTM3 port linked? How do I enable it? root@stm32mp1:~# dmesg | grep tty[ 0.000000] Kernel command line: root=PARTUUID=e91c4e10-16e6-4c0e-bd0e-77becf4a3582 rootwait rw console=ttySTM0,115200[ 0.598790] 40010000.serial: ttySTM0 at MMIO 0x40010000 (irq = 61, base_baud = 4000000) is a stm32-usart[ 3.619483] printk: console [ttySTM0] enabled[ 4.294977] 4c001000.serial: ttySTM3 at MMIO 0x4c001000 (irq = 62, base_baud = 4000000) is a stm32-usart[ 4.304256] serial serial0: tty port ttySTM3 registered[ 11.426540] systemd[1]: Created slice Slice /system/getty.[ 11.502583] systemd[1]: Created slice Slice /system/serial-getty.

 Hello,I’m currently rebuilding the device tree (DTS) for our custom board. I’ve modified the pin configurations according to our schematic. Could you please confirm if updating only the following files is sufficient for our customization?stm32mp257f-ev1.dtsstm32mp25-pinctrl.dtsiMy understanding is that these two files should cover the required pin configuration changes for our board, and the rest of the device tree files can remain unchanged.Also, I would like to avoid the consumer=kernel messages that appear when running the command:  cat /sys/kernel/debug/pinmux-pins/*/pinsCould you please confirm if my approach is correct, or if there are any additional changes needed elsewhere in the device tree?Best regards,Preetham.Please suggest points that help to my work.