Ask questions and find answers on STM32 microprocessors and dedicated embedded software solutions, such as Yocto SDK, Qt, and OP-TEE.
Most recent activity
First, build the package installed from STMicro's official website with the MACHINE name as "qemux86-64".And is it possible to display about 6 applications such as camera and video playback using demo launcher when started with "$ runqemu"?I look forward to your reply. Thank you.
Hi,I have a problem with the DMA seemingly being shut down due to ADC overrun.What I want to achieve: Three ADC channels should be read indefinitely and the values should be written to memory by DMA as soon as they are ready.What's currently happening:ADC and DMA work in the beginning, so my buffer fills up with values, but shortly after the start, the values in the buffer are not updated anymore and the DMA2_Stream0_IRQHandler is not called anymore either. I suspect the problem is an overrun, as the OVR bit is set in the ADC_ISR register (value is 0x101F) and ErrorCode is set to 2.The ADC_DR registers value still changes, so the ADC itself seems to be operational, and only the DMA stopped working.When the DMA does not work anymore, the DMA_CR register value alternates between 0x440 and 0x457. NDTR is some value over 140, and the addresses in M0AR and M1AR keep changing.My code for the ADC/DMA is as follows:DMA Initialization:static void MX_DMA_Init(void) { /* DMA controller clock ena
What are the benefits of using OpenStLinux on STM32MP15 and how does it differ from other operating systems?Thank you in advance for your response :)
I am an embedded Android developer working on eval board STM32MP157f-EV1 ,we started to design a custom hardware based on it .So I downloaded the st-android-11.0.0-2021-01-29 android soft , and flashed the board as mentionned on the wiki hwo to android , the switches are configured to boot from emmc , the startup of android system is ok but without screen , the dispaly is white , the tactil working fine i can see by the logcat all the services are fine even the ST laucher com.stmicroelectronics.stlauncher.Any help please ? , i tried to build locally a soft , flashed to sdcard but i faced the same problem on the dispaly .I attached the full log here
Hi,I can currently only find support for STM32MP157A-DK1 and STM32MP157C-DK2 boards in u-boot.Is there a plan to support the STM32MP157F-DK2 board in the near future?Kind regards,Steinar
I'm using the STM32MP157F-DK2-ND evaluation board and getting an error when I try to enable SPI5.I have researched previous posts with this errorhttps://community.st.com/s/question/0D53W000006FjAUSA0/error-activating-spi-module-in-yocto-linux-projecthttps://community.st.com/s/question/0D53W00000GZlRVSA1/enabling-devspidevxx-on-openstlinuxhttps://community.st.com/s/question/0D53W00000RS3ynSAD/how-can-i-enable-spi5-on-stm32mp157dk1And reviewed relevant documentationhttps://wiki.st.com/stm32mpu/wiki/How_to_use_SPI_from_Linux_userland_with_spidevhttps://wiki.st.com/stm32mpu/wiki/SPI_overviewhttps://wiki.st.com/stm32mpu/wiki/SPI_device_tree_configurationI've also ensured these options are checked in make linux-menuconfighttps://wiki.st.com/stm32mpu/wiki/SPI_overview#Kernel_configurationStill, I cannot figure out why the clock isn't running.[ 1.533147] spi_stm32 44009000.spi: clk rate = 0 [ 1.536942] spi
Hello all,I am facing a strange issue where the kernel sometimes fails to reboot the system. Here is what I am seeing.I use busybox reboot -f from the command line so that the reboot request goes directly to the kernel, i.e. no init/systemd involved. This simplifies things.I am tracing the reboot syscall up to the psci_sys_reset function of the PSCI device driver (drivers/firmware/psci/psci.c). I am toggling a GPIO just before invoking invoke_psci_fn:static int psci_sys_reset(struct notifier_block *nb, unsigned long action, void *data) { pr_info("reset!\n"); if ((reboot_mode == REBOOT_WARM || reboot_mode == REBOOT_SOFT) && psci_system_reset2_supported) { /* * reset_type[31] = 0 (architectural) * reset_type[30:0] = 0 (SYSTEM_WARM_RESET) * cookie = 0 (ignored by the implementation) */ invoke_psci_fn(PSCI_FN_NATIVE(1_1, SYSTEM_RESET2), 0, 0, 0); } else { // TOGGLE GPIO HERE invoke_psci_fn(PSCI_0_2_FN_SYSTEM_RESET, 0, 0, 0); } return NOTIFY_DONE; }The gpio i
Hi All.I have a stm32mp157C-DK2, I have used the lastest demo from ST(openstlinux-5.15-yocto-kirkstone-mp1-v22.06.15).I have done audio tests and I have found a problem/bug when I play a wav file and next I record a audio. I can see a kernel trace (always happens), indicating that an overrun occurs and the audio record has a cut.I add the traces:root@stm32mp1:~# aplay -D playback_codec /usr/share/sounds/alsa/Front_Left.wav Playing WAVE '/usr/share/sounds/alsa/Front_Left.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono root@stm32mp1:~# arecord -D record_codec -r 48000 -f S16_LE -c 1 -d 5 /tmp/rec.wav Recording WAVE '/tmp/rec.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono [ 3356.405866] st,stm32-sai-sub 4400b024.audio-controller: IRQ Anticipated frame synchro overrun!!! (at least 0.175 ms long)Is this a known issue?Would there be a solution?
Hi all.I am using a stm32mp157c-dk2 with lastest OpenSTLinux Distribution (4.1.0) trusted.In log I saw messages about SCMI driver and a series of protocols not actives.[ 0.150587] arm-scmi firmware:scmi: SCMI Notifications - Core Enabled. [ 0.150709] arm-scmi firmware:scmi: SCMI Protocol v2.0 'ST:' Firmware version 0x0 [ 0.289178] arm-scmi firmware:scmi: Failed. SCMI protocol 23 not active. [ 0.412876] arm-scmi firmware:scmi: Failed. SCMI protocol 21 not active. [ 0.424756] arm-scmi firmware:scmi: Failed. SCMI protocol 19 not active. [ 0.428615] arm-scmi firmware:scmi: Failed. SCMI protocol 17 not active.I should care about this messages?Why are these protocols not active?What are these protocols?Thanks!
My rgb lcd screen does not display。My board is based on the STM32MP153AAA3 design, using a separate power supply.This is my schematic diagramThis is the timing of the LCD This is the LCD device tree This is some panel-simple driver codeHere are some boot logs Looking forward to your response!
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
WATCH ON-DEMAND | STM32 Summit 2026
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.