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
I don't have the knowledge to look at the LCD touch screen specifications to determine if it can be used on my board.I am looking for a 7-inch LCD touch screen that can be used with openstlinux on STM32MP157D-DK1.openstlinux was set up like this:repo init -u https://github.com/STMicroelectronics/oe-manifest.git -b refs/tags/openstlinux-6.1-yocto-micckledore-mp1-v23.11.15repo syncDISTRO=openstlinux-weston MACHINE=stm32mp1 source layers/meta-st/scripts/envsetup.shbitbake -k st-image-westonLinux stm32mp1 6.1.28 #1 SMP PREEMPT Thu May 11 14:04:52 UTC 2023 armv7l GNU/LinuxPlease help me.
I compiled the linux kernel with STM32CubeIDE and notice that the linux kernel vmlinux is about 242 Mb.Why so large?Or do I looking at the wrong folder? I'm standing inside the build folder.
Hello I have built the st-example-image-qt using openstlinux(Openstlinux-5.15-yocto-kirkstone-mp1-v23.07.26) to run a qt application for stm32mp157f-dk2 board.I could run the application the application successfully.It would be very helpful to move forward with my further development, if i could get the clarifications regarding the below mentioned points :1.How to enable window manager support in the example image that i am working with.2.How to implement debugging of QT Application using remote gdb server.3.How to display on application on DSI and HDMI simultaneously. Thanks in AdvanceSrikanth
Hi,I want to create a custom machine for my board. I've found the wiki page "how to create your own machine" but this assumes you create your own layer/machine inside meta-st, but I want my machine to be inside /layers/.I want this outside meta-st because I want to add the machine inside a git repo, meta-st-stm32mp-addons is already a git repo on its own.I want to setup my distribution package the following way, is this possible, and how?repo init -u https://github.com/STMicroelectronics/oe-manifest.git -b refs/tags/openstlinux-6.1-yocto-mickledore-mp1-v23.06.21repo syncgit clone <git server/repo that contains custom layer + machine> ./layers/meta-mylayer/DISTRO=openstlinux-weston MACHINE=my-custom-machine(inside meta-mylayer) source layers/meta-st/scripts/envsetup.shbitbake st-image-core
I would like to only use cgroup v2 and would like to modify the kernel cmdline boot arguments as follows:, . I searched internet and suggestion is to useadd systemd. unified_cgroup_hierarchy=1 under /etc/default/grub , followed by sudo update-grub .My current command line is:cat /proc/cmdlineroot=PARTUUID=e91c4e10-16e6-4c0e-bd0e-77becf4a3582 rootwait rw console=ttySTM0,115200root@stm32mp1:/dev# stat -fc %T /sys/fs/cgrouptmpfs**cgroup v1 and cgroup v2 enabled.I added to new file /etc/default/grouproot@stm32mp1:/dev# cat /etc/default/grubGRUB_CMDLINE_LINUX="$GRUB_CMDLINE_LINUX systemd.unified_cgroup_hierarchy=1"I tried update-grub and grub2-mkconfig, but both commands did not executeroot@stm32mp1:/dev# update-grub-bash: update-grub: command not foundroot@stm32mp1:/dev# grub2-mkconfig-bash: grub2-mkconfig: command not foundroot@stm32mp1:/dev# echo $PATH How do I update GRUB on STM32MP157F-EV1 system?
NOTICE: CPU: STM32MP157FAC Rev.ZNOTICE: Model: STMicroelectronics STM32MP157F-DK2 Discovery BoardINFO: PMIC version = 0x21INFO: Reset reason (0x14):INFO: Pad Reset from NRSTINFO: FCONF: Reading TB_FW firmware configuration file from: 0x2ffe2000INFO: FCONF: Reading firmware configuration information for: stm32mp_ioINFO: Using SDMMCINFO: Instance 1INFO: Boot used partition fsbl1NOTICE: BL2: v2.8-stm32mp1-r1.0(debug):lts-v2.8.6-dirty(ff0bd5f9)NOTICE: BL2: Built : 17:57:15, Apr 21 2023INFO: BL2: Doing platform setupINFO: RAM: DDR3-DDR3L 16bits 533000kHzINFO: Memory size = 0x20000000 (512 MB)INFO: BL2: Loading image id 1INFO: Loading image id=1 at address 0x2ffff000INFO: Image id=1 loaded: 0x2ffff000 - 0x2ffff1eaINFO: FCONF: Reading FW_CONFIG firmware configuration file from: 0x2ffff000INFO: FCONF: Reading firmware configuration information for: dyn_cfgINFO: FCONF: Reading firmware configuration information for: stm32mp1_firewallINFO: BL2: Loading image id 4INFO: Loading image id=4 at addre
I have compiled.OpteeTF-AU-bootLinuxAnd it seems to work well. I have also tried to implement a pre-made OpenSTLinux from the Source files. And it seems to work well too. I haven't got any terminal up and running. I can only see the display output of messages when I start it up.Notice that the kernel comes from STM32MP157 and before the kernel startup, it's from STM32MP151. That's why you see that the MAC address is not set, but once linux kernel is started, you can see inside the log that the MAC address is set to "56:bf:8f:58:f8:31".https://pastebin.com/QTV4qbHrI need to create bootfs, vendorfs, userfs and rootfs.ext4, so what should I do next? Should I create empty .ext4 files and then mount the .ext4 files and later fill them with...?
Hello,Would it be possible to have an updated guide on how to use a custom device tree within my own layer for latest STM32MP1 Ecosystem ?The one provided here "How to compile the device tree with the Distribution package" is clearly outdated, as the Yocto delivery mentionned in the exemple is Kirkstone (should be now Mickledore) and the step : Replace STM32MP_MX_BASE by STM32MP_MY_DEMO_BASEIs impossible to do, as the variable STM32MP_MX_BASE does not exist in latest machine configurations.In the meanwhile, any ideas of how to implement this solution for latest? I'm currently using this solution "How to create your own machine" in the wiki, but that is not the way I would like to work in the long term.
Hi ST Community, @Erwan SZYMANSKI I’ve been working on integrating a Qt example from ~/Qt/Examples/Qt-6.7.2/quickcontrols/imagine into my custom Yocto layer for an STM32 board. I created a recipe for this and updated my local.conf accordingly. After building the image and flashing it to my board, I encountered the following error when running the application. I have added my .bb recipe file and local.conf file. (I have qt5 layer installed too) nesnes@nesnes-ABRA-A5-V19-2:~/STM32MPU-Ecosystem-v5.1.0/Distribution-Package/build-openstlinuxweston-stm32mp15-disco$ bitbake automotive NOTE: Started PRServer with DBfile: /home/nesnes/STM32MPU-Ecosystem-v5.1.0/Distribution-Package/build-openstlinuxweston-stm32mp15-disco/cache/prserv.sqlite3, Address: 127.0.0.1:33289, PID: 89725 Loading cache: 100% |########################################################################################################################################################################| Time: 0:00:00 Loade
Hello,We're trying to boot our prototype which contains an STM32MP157FAA.Unfortunately, we didn't implement an oscillator/quartz on the board, so we are unable to use HSE and can only use HSI.We have access to USB1, USB2, SDMMC3, and UART4.Is there a way to load U-Boot with these options using HSI ?Best regards,François
The 'of_device_id' in my module is as follows:static const struct of_device_id gcnano_of_match[] = { { .compatible = "st,gcnano" }, { .compatible = "vivante,gc" }, { /* end node */ } };In the device tree:compatible = "vivante,gc";When using the 'modprobe' command to load the module, it was unable to match successfully and the 'probe' function of the module was not executed. The 'compatible' property of the module is the same as the 'compatible' property of the device tree, but I changed both the 'compatible' property of the module and the device tree to 'vivante_1, gc_1' to match successfully and execute the 'probe' function. I have tried many times to change it to anything, as long as I change it back to 'vivante, gc', it won't work. Has anyone encountered this problem?
Does anyone know how to view and modify the current CPU frequency of STM32MP157D? I also cannot use the following command: root@stm32mp1:/sys# cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 1 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 Hardware : STM32 (Device Tree Support) Revision : 0000 Serial : 003C00403132510831323338 root@stm32mp1:/sys# cd / root@stm32mp1:/# cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva
x linux-5.15-stm32mp-r2 for our puposes. I have also attached the pps-gpio source code in case it is useful.
Hello STM32 Community,I hope this message finds you well.I’m currently working with an STM32 Linux board and have encountered an issue where the TSV Flashing Service fails and the code is not dumping correctly. I would greatly appreciate any assistance or guidance you can provide to resolve this problem.Here are some details that might be relevant:TSV Flashing service failedFile does not exitstep 1step 2:step 3:step 4:step 5:Thank you very much for your time and support. I look forward to your advice.Best regards,EM-TECH
HiI have recently been working on the board model mentioned in the title. At the moment I have a problem with two things:1. when trying to debug the kernel drivers, the kernel is inactive for a period of time which causes the watchdog to run. This behavior makes it impossible to debug the drivers. Is there any convenient solution to disable the watchdog?At this point I have disabled support for watchdog in both the uboot and kernel, but this has caused the board to reset itself no matter what I do (there is information on the wiki about the possibility of disabling it from the build root level). Looking through the information available on the Internet, I found out that you could directly modify the memory, but this option does not suit me. Another piece of advice is in the course from bootlin: ```However, it turns out that this pre-defined configuration enables the STM32 watchdog, and since our Linux user-space does not have a watchdog daemon to tick the watchdog regularly, it wo
Hi, when trying the new ST BSP release base on linux kernel 6.1.82 on my stm32mp157f-dk2 I noticed that the legacy framebuffer support is not working anymore.this was working perfectly on the previous release with linux kernel 6.1.28.I didn't succeed in getting it working again, here is a fragment of my linux kernel configuration: CONFIG_DRM=yCONFIG_DRM_STM=yCONFIG_DRM_STM_DSI=yCONFIG_DRM_PANEL_ORISETECH_OTM8009A=yCONFIG_DRM_SII902X=yCONFIG_FB=yCONFIG_FB_SIMPLE=yCONFIG_BACKLIGHT_CLASS_DEVICE=yCONFIG_BACKLIGHT_PWM=yCONFIG_BACKLIGHT_GPIO=yCONFIG_FRAMEBUFFER_CONSOLE=yCONFIG_FRAMEBUFFER_CONSOLE_ROTATION=yCONFIG_DRM_FBDEV_EMULATION=yCONFIG_LOGO=ycan you please advice how to get it working again ? I don't plan to use DRM. Best regards
The Linux version I am using is 6.1.28, and the chip is STM32MP157D. Currently, the USB-OTG chip uses FUSB302. I tried the online driver and found some issues. When I plugged in the USB device, there was no response. However, setting the USB-OTG to host or peripheral mode separately is normal, so I suspect it may be a problem with the FUSB302 driver.
Hello to everyone!We have develop a System on Module board based on the STM32MP153AAB. Currently it have a custom Yocto Image build, that it's working. The process followed almost all the steps in the wiki for the STM32MP157F-DK2 discovery kit, however, some pins had to change due to the custom design. Now we have encountered a problem debugging the M4 firmware in the custom SOM. This firmware currently works in the MP157F-DK2 discovery kit (The debug too). Trying to fix this, we have used the STM32CubeIDE 1.14.0 to develop a blinky example on the M4, and the STLINK-V2 to start the debugging. The STLINK-V2 it's correctly recognized by the STM32CubeIDE. Besides that, we have not been able to debug. We can download and run the .elf manually on the board, following the steps in the wiki using sys and remoteproc interface: https://wiki.st.com/stm32mpu/wiki/Linux_remoteproc_framework_overview LED blinks okay. Because we are in a custom PCB, don't have ac
I want to test the memory by using U-boot.I'm reading the DDR memory from 0xC0000000 to 0xE0000000 with the pattern 0xFFFFFFF. But I don't have premision to read the memory. How can I solve this issue? STM32MP> mtest 0xC0000000 0xE0000000 0xFFFFFFFF Testing c0000000 ... e0000000: Iteration: 1 Pattern FFFFFFFF Writing... Reading...Iteration: 2 Pattern 00000001 Writing... E/TC:0 tzc_it_handler:79 TZC permission failure E/TC:0 dump_fail_filter:420 Permission violation on filter 0 E/TC:0 dump_fail_filter:425 Violation @0xf8803000, non-secure privileged read, AXI ID 4a0 E/TC:0 tzc_it_handler:79 TZC permission failure E/TC:0 dump_fail_filter:420 Permission violation on filter 0 E/TC:0 dump_fail_filter:425 Violation @0xf8804000, non-secure privileged read, AXI ID 4a0 My U-boot Device Tree for the memory. memory@c0000000 { device_type = "memory"; reg = <0xc0000000 0x20000000&
Dear All,I have been developing touch screen with XPT4096.When press touch screen, interrupt is generated.Read Y, X, Z1, Z2, power down is sent to XPT4096.During transferring message to XPT4096, transfer setup failed.Please refer to waveform.1CH : spi clock2CH : interrupt3CH : MOSI(to 4096)4CH: MISO(from 4096)
I can fix the problem by enabling interrupts for the DMA channel. But WHY should this be necessary?I'd prefer to do this with no interrupts. I allow ample time between calls so data transfers have plenty of time to complete.(G4 chip, MX set up as SPI3 transmit only master with DMA on DMA2 channel1)Thanks!
I have only one MMC, in this case it's an eMMC on SDMMC2. I have some issues when I loading over the TF-A and the FIP.bin file.Update:I have change the clock frequency to 49.5 MHz and measured the v3v3 signal to 3.3V and the vdd signal to 3.3V as well. I got still the same issue. &sdmmc2{ pinctrl-names = "default", "opendrain", "sleep"; pinctrl-0 = <&sdmmc2_pins_mx>; pinctrl-1 = <&sdmmc2_opendrain_pins_mx>; pinctrl-2 = <&sdmmc2_sleep_pins_mx>; status = "okay"; /* USER CODE BEGIN sdmmc2 */ non-removable; no-sd; no-sdio; st,neg-edge; bus-width = <8>; vmmc-supply = <&v3v3>; vqmmc-supply = <&vdd>; mmc-ddr-3_3v; /* USER CODE END sdmmc2 */ }; This is the debug output. Here we can see that I have only one eMMC. I don't know if the log says that the eMMC is mounted on 0, or if it's the first index. Second suspect is "Loading Enviroment from nowhere... OK". So that means...what? An empty system?&nb
Hello We have built OpenSTLinux(Openstlinux-6.1-yocto-mickledore-mp1-v23.06.21) for stm32mp157f-dk2 Board and I have built st-image-weston image. Iam new to this Yocto,so I request you to help with the following:How to make changes in dts & dtsi files (u-boot & Linux) and source files and build the image.And Iam working on display, I would like to write an application and run it on the display. So hoping to get help regarding how to add Qt (Qt5) packages and the respective libraries so that i could run a GUI on the display. Thanks & RegardsSrikanth.R
Why does the STM32MP157AAD3 have a higher heat or temperature? We have an STM32 board that has interfaces for PMIC, DDR3, temperature sensors, VOC, EMMC, LEDs, push buttons, WIFI+BLE modules, 8-pin connectors, wake-up switches are build in same board Sir, we have observed that the board can get as hot as 90 degrees Celsius when it is operating at full load. How can we deal with this heat problem? Could you please elaborate? I've included pictures of the board for your reference.
Hi, we have a custom design with an STM32MP13xx CPU.We currently see random issues during boot. Some of the prototypes randomly stuck on boot without any output on the serial console, sometimes they are booting well. When a board has booted it runs stable without any issues.In error case, the oscillator does not start, we don't see any i2c communication to the PMIC and also the RAM power supply is not there.After review of the layout we saw that PDR_ON is floating and not connected to VDD as required in the datasheet and AN5474 (Getting started with STM32MP13x lines hardware development).My question:- can a floating PDR_ON pin lead to this random boot issues?- what else can be checked or is required if the oscillator does randomly not start running?Thanks in advance and best regardsRuben
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.