STM32 MPUs Embedded software and solutions

The Linux Kernel maintainers have just updated the longterm release kernels: https://www.kernel.org/category/releases.htmlCould someone from ST please give an information about which kernel version for STM32MP1 will be supported in the future until 2026? Will ST stay on v5.15 or go to v6.1?

Hello,Here's the context of my issue.I'm using buildroot 2022.11 to build a rootfs for a custom stm32mp157 board using a LCD display;the Linux kernel is 5.10.116 (https://github.com/STMicroelectronics/linux/tree/v5.10-stm32mp);the GUI app is built using the Qt5.15 QML framework.After the buildroot team upgraded the gcnano binaries package to v6.4.7 I'm facing flickering issues with the display. To figure out if the gcnano binaries are the root cause, I manually downgraded the gcnano to v6.4.3 in which the flickering issue is not present.I can confirm that the same rootfs/kernel with the gcnano binaries 6.4.3 has no flickering issue.Find attached to this post two videos :one showing that everything works fine with gcnano 6.4.3;one showing the flickering issue with gcnano 6.4.7.The display is mandatory for our product and we can not accept flickering issues like this one.How can we fix this issue ?Let me know if you need more traces or tests.Best RegardsAlexandre Gambier

Hi,I am experiencing a loss of about 2 seconds on the hwclock every time I reboot. Regardless of how long the system has been powered off, it is consistently the same amount of time lost. I have come across the following posts which seem to point to the issue being in the initialization of the LSE oscillator during startup. STM32 RTC loses one second after each resetStm32L452 RTC Clock Drift with use---related to entering/exiting shutdown mode?My question is, since the RCC initialization is handled by the A7 core, where do I prevent the LSE from re-initializing on each boot? Below is a snippet from my device tree//tfa device tree   clk_lse: clk-lse { st,drive = < LSEDRV_MEDIUM_HIGH >;   /* USER CODE BEGIN clk_lse */ #clock-cells = <0>; compatible = "fixed-clock"; clock-frequency = <32768>; /* USER CODE END clk_lse */ };Any suggestions would be appreciated.

After download TFA, USB DFU device is marked as "UNKNOWN":#dfu-util -a 1 -D tfa_v4.stm32 && dfu-util -a 0 -e && sleep 2 #dfu-util -l   dfu-util 0.9   Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2016 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to sourceforge.net/p/dfu-util/tickets/   Found DFU: [0483:df11] ver=0200, devnum=58, cfg=1, intf=0, path="1-1.5", alt=5, name="UNKNOWN", serial="UNKNOWN" Found DFU: [0483:df11] ver=0200, devnum=58, cfg=1, intf=0, path="1-1.5", alt=4, name="UNKNOWN", serial="UNKNOWN" Found DFU: [0483:df11] ver=0200, devnum=58, cfg=1, intf=0, path="1-1.5", alt=3, name="UNKNOWN", serial="UNKNOWN" Found DFU: [0483:df11] ver=0200, devnum=58, cfg=1, intf=0, path="1-1.5", alt=2, name="UNKNOWN", serial="UNKNOWN" Found DFU: [0483:df11] ver=0200, devnum=58, cfg=1, intf=0, path="1-1.5", alt=1, name="UNKNOWN", serial="UNKNOWN" Found DFU: [

Hi!STM32MP1 provides a real-time core, and we use it for the hard-real time. But additionally, we would need the application running on the two fast cores to also be real-time. (with softer constraints but still better than standard scheduling on Linux).For this, I added to the yocto project, at (not the best place, but just trying to make it to work for now):Layers/meta-st/meta-st-openstlinux/conf/distro/openstlinux-weston.confPREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt" COMPATIBLE_MACHINE = "(stm32mp1)"But then, I get the following errors:ERROR: Nothing PROVIDES 'quilt-native'quilt-native was skipped: incompatible with machine stm32mp1 (not in COMPATIBLE_MACHINE)ERROR: Required build target 'st-image-weston' has no buildable providers.Missing or unbuildable dependency chain was: ['st-image-weston', 'quilt-native']

 stm32mp157a-dk1 board

Hello,I'm currently using the following setting for the ethernet0 in Linux 5.7.6:&ethernet0 {   status = "okay";   interrupts-extended = <&intc GIC_SPI 61 IRQ_TYPE_LEVEL_HIGH>,   <&intc GIC_SPI 62 IRQ_TYPE_LEVEL_HIGH>,   <&exti 70 1>;   interrupt-names = "macirq",   "eth_wake_irq",   "stm32_pwr_wakeup";     pinctrl-0 = <&ethernet0_rmii_pins_a>;   pinctrl-1 = <&ethernet0_rmii_pins_sleep_a>;   pinctrl-names = "default", "sleep";   phy-mode = "rmii";   max-speed = <100>;   phy-handle = <&phy0>;     mdio0 {   #address-cells = <1>;   #size-cells = <0>;   compatible = "snps,dwmac-mdio";   reset-gpios = <&gpioh 6 GPIO_ACTIVE_LOW>;   reset-delay-us = <1000>;     phy0: ethernet-phy@1 {   reg = <1>;   };   };   };It works correctly, while

I build the OpenStLinux from the ST Yocto project and added the Preempt_RT patch to make the kernel "real-time". ( uname -a correctly report PREEMP_RT kernel).After this, I am checking real-time capabilities with the rt-tests utilities.When calling root@stm32mp1-rt:/boot# cyclictest --mlockall -t -a --priority=99 --interval=200 --distance=0 -l 0 WARN: stat /dev/cpu_dma_latency failed: No such file or directory policy: fifo: loadavg: 4.69 2.97 2.01 3/243 7436   T: 0 ( 7207) P:99 I:200 C: 511845 Min: 15 Act: 30 Avg: 27 Max: 909 T: 1 ( 7208) P:99 I:200 C: 511534 Min: 15 Act: 39 Avg: 31 Max: 462I get too high jitter.I am wondering if tuning a bit the kernel could help:skew_tick=1 idle=poll ...But OpenStLinux has no grub bootloader.

There seems to be an option to change assignment in STM32CubeIDE (in .ioc file), but DMA1 is assigned to A7 and DMA2 is assigned to M4 and the another core is always greyed out. Is it possible to unlock those settings?

What possible displays mentioned below are suggested to integrate with stm32mpu boards for production purpose with doing less configurations?The touchscreen will show linux gui app.1. LVds with capacitive touch2. Rgb paralell dispaly with resisitive touch3. HMI display with capacitive touchPlease note this is industrial application.Are there any tutorials or procedures available on st homepage to easily follow and complete them?

Hello,I am using the STM32MP157F-DK2 and recently went through a textbook rebuild of the Linux kernel, the modules and the gcnano driver (for GL support). All is well and yet, I see only one of the two CPUS. dmesg tells me the following:[   0.000000] ------------[ cut here ]------------[   0.000000] WARNING: CPU: 0 PID: 0 at arch/arm/kernel/devtree.c:148 arm_dt_init_cpu_maps+0x168/0x250[   0.000000] DT /cpu 2 nodes greater than max cores 1, capping them[   0.000000] Modules linked in:[   0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 5.15.67 #1[   0.000000] Hardware name: STM32 (Device Tree Support)[   0.000000] [<c010e8ec>] (unwind_backtrace) from [<c010c158>] (show_stack+0x10/0x14)[   0.000000] [<c010c158>] (show_stack) from [<c0122404>] (__warn+0xec/0x148)[   0.000000] [<c0122404>] (__warn) from [<c0c33034>] (wa

Hi,I'm looking for a processor for a camera application that have the following features:MIPI CSI2 interfaceץBT5 connectivity abilities. Small as possible.Application processor like the Cortex A53. Thanks,Avishay.

Trying to compile wpe-browser from meta-wpewebkit and during building cog I'm getting error:https://github.com/Igalia/meta-webkit/issues/446It seems that gcnano-userland-multi-binary-stm32mp provides gbm.h which clash with one from cog. I've resolved it by:`GPU_USERLAND_LIBRARIES_WAYLAND = "mesa"` adding to local.confand also by adding append for gcnano-userland-multi-binary-stm32mp.bbappendwith content:`GCNANO_PACKAGECONFIG:remove = "gbm"` but when I start wpe browser it display just white background and nothing more.Thanks.

Hello!I've got a problem configuring USB OTG on a board based on the STM32MP157C. This is actually the Odyssey board by Seeed Studio, which is not directly supported by STLinux as far as I know. Actually we have custom hardware with the STM32MP157C SOM, but since the problem is reproducible on their development board, that is easier to follow for everybody else. I have already posted this question in their support forum but would like to hear your opinion as well.The Yocto firmware I am testing on is based on meta-st-stm32mp (openstlinux-5.10-dunfell-mp1-21-03-31). I got the same behavior with the hardknott branch which is not surprising since the kernel did not change.This is from the device tree:&usbh_ehci { phys = <&usbphyc_port0>; status = "okay"; };   &usbh_ohci{ status = "okay"; phys = <&usbphyc_port0>; };   &usbotg_hs { compatible = "st,stm32mp15-fsotg", "snps,dwc2"; pinctrl-names = "default"; /* configure OTG ID and full-speed da

Hi,I started getting above errors recently, when trying to connect to an Android device.Can you elaborate on these errors on BLE?0x08 Connection timeout0x3E Connection failed to be establishedHow can I overcome them?Thanks

I have three UARTs on the board, all passed the loopback test (wire the tx and rx pin together on the same UART)Then I connect UART 1 to UART2 while UART 1 is transmitter and UART2 is receiver.UART 1 is using HAL_UART_Transmit() to send data to UART2.On the UART2 side, after initialization, I did__HAL_UART_ENABLE_IT(uart_interrupt_config.huart, UART_IT_RXNE); // read data register not empty interruptionIRQ_SetPriority(UART2_IRQn, 0);IRQ_Enable(UART2_IRQn);I put a break point inside UART2_IRQhandler but never reaches there.What am I missing here?Thanks in advance

Hi,I have custom board running 5.15.24 OpenSTLinux on STM32MP157F based board.Problem is, when I try to select CONFIG_GCC_PLUGINS. It depends on depends on $(success,test -e $(shell,$(CC) -print-file-name=plugin)/include/plugin-version.h)in file scripts\gcc-plugins\KconfigI just can't select it, because evaluation of the conditions is always negative.I have traced the CC binary and when I run -print-file-name manually on it, plugin-version.h exist on the path.Problem seems to be with $(shellcall, which on ST port of Linux always crops output to 256 characters (which results in non existent path, because it points deeply into Yocto build folders)! I have tried it with $(shell,echoand it results in same cropping.When I try the same thing on my i.MX repository from NXP, output is correct and I can select CONFIG_GCC_PLUGINS correctly.Any ideas for what is going on?Thanks in advance,Michal Spanik

There seems to be an issue with CubeProgrammer and parsing hex strings that are longer than 8 characters. For example, an offset of 0x05984400 will parse correctly but 0x105984400 will not. It will incorrectly parse as 0x05984400. I am trying to reference an offset that is past the 4GB mark so CubeProgrammer is truncating my offset value. Is it supposed to do that? What is the best way to reference partitions past the 2^32 bits mark? Are other people able to get it to work or am I just doing something weird? Edit: Also the images in Kirkstone are defaut to a rootfs size of 4GiB.

Hello!I upgraded Linux kernel from 5.4 to 5.15 (ST linux-5.15-stm32mp-r2). Simply added new options to kernel config and kept mostly the same DT. I get the error below in the boot log which renders the whole system unusable.Based on the boot log below what would you think I am missing? If it is impossible to know without a .config and/or DT I will try to add those.[   3.254882] platform 50000000.rcc: Linked as a consumer to firmware:scmi[   3.261800] rcc@50000000 Dropping the fwnode link to scmi[   3.267423] bus: 'platform': __driver_probe_device: matched device 50000000.rcc with driver stm32mp1_rcc[   3.277231] platform 50000000.rcc: error -EPROBE_DEFER: supplier firmware:scmi not ready[   3.285613] platform 50000000.rcc: Added to deferred list[   3.291297] device: '50001000.pwr': device_addThanks in advance!

In trying to provide X11 support to a Weston distribution, I modified the weston distro conf (meta-st-openstlinux/conf/distro/openstlinux-weston.conf) to read:#DISTRO_FEATURES:remove = " x11 " # with X11 PREFERRED_PROVIDER_virtual/xserver = "${@bb.utils.contains('DISTRO_FEATURES', 'x11 wayland', 'xwayland', 'xserver-xorg', d)}"This appropriately builds the X11 libraries needed, but I get a configuration error for the mesa-gl package:| ../mesa-22.0.0/meson.build:555:6: ERROR: Problem encountered: xlib based GLX requires at least one gallium driverIt looks like the invocation of meson does not pass the right value for gallium-drivers even though the environment does imply it should be set appropriately. The do_configure log file contains "-Dgallium-drivers=":NOTE: Executing meson -Dshared-glapi=enabled -Dglx-read-only-text=true -Dplatforms=x11 -Ddri3=disabled -Degl=disabled -Delf-tls=false -Dgallium-drivers= -Dllvm=disabled -Dgbm=disabled -Dgles1=disabled -Dgles2=disabled -Dlmsensors=dis

I am trying to compile a recipe for STM32MP157c for yocto kirkstone kernel version 5.15 on Soc provided by karo-electronics i.e. QSMP1570 module on qsbase2.I have written a recipe and kernel module for gpio interrupt which is unable to be compile, the log file is attached.There are modpost errors being encountered.

Suppose I would implement a sysfs interface that enables me to set the dr_mode of the dwc2 driver. Is it possible without huge changes in the code, to change the dr_mode on the fly via userspace? We might use the usb-role-switch functionality of the dwc2 drd driver, but can it be dynamically set just like that?

Hello,I'm using a ST32MP157C-DK2 board to develop an application running on CM4 that basically handles a CAN Standard communication.I routed the FDCAN1 signals on PA11 and PA12 and I am trying to send out some random data with no result...Here is my code:static void MX_FDCAN1_Init(void) {   /* USER CODE BEGIN FDCAN1_Init 0 */   /* USER CODE END FDCAN1_Init 0 */   /* USER CODE BEGIN FDCAN1_Init 1 */   /* USER CODE END FDCAN1_Init 1 */ hfdcan1.Instance = FDCAN1; hfdcan1.Init.FrameFormat = FDCAN_FRAME_CLASSIC; hfdcan1.Init.Mode = FDCAN_MODE_NORMAL; hfdcan1.Init.AutoRetransmission = DISABLE; hfdcan1.Init.TransmitPause = DISABLE; hfdcan1.Init.ProtocolException = DISABLE; hfdcan1.Init.NominalPrescaler = 1; hfdcan1.Init.NominalSyncJumpWidth = 1; hfdcan1.Init.NominalTimeSeg1 = 2; hfdcan1.Init.NominalTimeSeg2 = 2; hfdcan1.Init.DataPrescaler = 1; hfdcan1.Init.DataSyncJumpWidth = 1; hfdcan1.Init.DataTimeSeg1 = 1; hfdcan1.Init.DataTimeSeg2 = 1; hfdcan1.Init.M

I want to be able to have the Ethernet port on my board be configured as a link local address and be able to receive DHCP. How can I accomplish this?

I modified the device tree by a patch to disable HW flow control. It seems the port is still working as expected. Why are the pins grouped by 'pins1' ... 'pinsN'? Is this just to apply the same settings to these pins?Why can I remove some pins and RX is still RX and TX is still TX and not shifted because I removed an entry? How is this detected by the driver?Here is my patch:usart2_pins_c: usart2-2 { pins1 { - pinmux = <STM32_PINMUX('D', 5, AF7)>, /* USART2_TX */ - <STM32_PINMUX('D', 4, AF7)>; /* USART2_RTS */ + pinmux = <STM32_PINMUX('D', 5, AF7)>; /* USART2_TX */ bias-disable; drive-push-pull; slew-rate = <3>; }; pins2 { - pinmux = <STM32_PINMUX('D', 6, AF7)>, /* USART2_RX */ - <STM32_PINMUX('D', 3, AF7)>; /* USART2_CTS_NSS */ + pinmux = <STM32_PINMUX('D', 6, AF7)>; /* USART2_RX */ bias-disable; }; };