STM32 MPUs Embedded software and solutions

Hello, I have dual core STM32MP157F-EV evaluation kit. I can connect via ST-link and install an application (This is installing on M4). And when I press the reset button, the application is deleted because the M4 core is RAM. I want it to work again every time I reset it. How can I do that ? How can I create an application-specific yocto project?

Building the yocto image for honister release for STM32MP157F-DK2 board.

HiWe are using SEEED studio 102110318 module which uses STM32MP157CAC3 processor. We want to know if there is any way we can keep processor pin PD13 pin to low state in suspend state. We want the pin to maintain low state while in sleep mode. We have added pullup on this pin in Hardware which is affecting one of our peripheral operation in sleep mode. For this reason we want this pin to be set low which will solve the issue. We do not have any other option to remove pullup in hardware as our device production is completedPD13 is used as PWM to control LCD backlight, Is there any possibility to maintain PD13 as its runtime state during suspend mode, basically i dont want to control this pin during suspend modeI tried in sysfs, to control autosuspend_delay_ms but im getting IO error please find below imageis there any way to control it from suspend mode?Is there any other drivers that will support this feature?RegardsSrini

Hi,we are using a coin cell to supply the internal RTC of an STM32MP157 when our system is unpowered.This works as expected - as long as the external supply is off. As soon as the system is powered on, the battery is discharged with >20µA.Observing the register ADC_CCR shows that VBATEN is permanently set, connecting VBAT to the ADC input and a resistor devider (as stated in Fig. 248 in the reference manual).[Edit: removed misleading reference to ADC driver]In my understanding VBATEN is supposed to be set only while (and shortly before) VBAT is actually sampled. Otherwise the switch as seen in Fig. 248 does not make much sense to me.

Hi Everybody,I would like to completely boot kernel 5.10-dunfell (last year) from a 64MB dataflash (nor0). No mmc0 or nand0. Compiled the correct DTS with TF-A, U-Boot and kernel, I would like to use the following TSV for STM32CubeProgrammer:#Opt Id Name Type IP Offset Binary - 0x01 fsbl1-boot Binary none 0x0 tf-a-stm32mp151a-***-mx-usb.stm32 - 0x03 fip-boot Binary none 0x0 fip-stm32mp151a-***-mx-trusted.bin P 0x04 fsbl1 Binary nor0 0x00000000 tf-a-stm32mp151a-***-mx-nor.stm32 P 0x05 fsbl2 Binary nor0 0x00040000 tf-a-stm32mp151a-***-mx-nor.stm32 P 0x06 fip Binary nor0 0x00080000 fip-stm32mp151a-***-mx-trusted.bin PDE 0x07 u-boot-env Binary nor0 0x00480000 none P 0x10 UBI Binary nor0 0x00500000 rootfs.binwhere *** is my project code (obfuscated).Once started, U-Boot fails to proceed to load rootfs.bin, which contains the kernel, modules and filesystem as a UBI partition. This was produced by Buildroot and it is valid; I checked loop-mounting it with mtdram. The type for UBI is Binary s

Custom PCB, STM32MP157C chip. Linux 5.7.10. Buildroot build. No issues - Linux boots to console prompt without trouble, no errors. I can view device registers and all memory regions using Segger Jlink via SWD in both SPL and UBoot. Once Linux starts - I can only view memory from 0xC0000000 to 0xCFFFFFFF, i.e. the DRAM. Any attempt to read internal RAM or device registers via SWD fails with "cannot read memory". JLink connected to CPU 0 (A7). If connected to M4 all I get is 0x23000000 regardless of what address I try to read (but the M4 is still in reset so that may be the reason).I am not certain if SWD read goes through A7 virtual memory mapping or not - but anybody know what needs to change so I can access internal RAM space and device registers from SWD once Linux is running ?

Hallo in our company we use for a large Project a STM32 MP153a microprocessor. Currently I'm trying to write a Device Driver for the TDK ICM42688P Mems Gyro. We have connected the Gyro trough I2C with the Cortex M4 core within the MPU. Both devices are located on a custom PCB and the Gyro is routed to the I2C2 Interface of the MPU (I2C2_SCL = PZ6, I2C2_SDA = PZ7). The Gyro is the only Device on this Interface (I2C2). We use a I2C Voltage of 1.8V and both devices support these voltage. The I2C2 Interface is in the Polling Mode.For my driver I have to read multiple registers of the Gyro therefore I use the HAL_I2C_MEM_READ function of the STM32 HAL which is in the HAL generated from CubeMX. I noticed that I get random Communication Errors so I have written a simple testcase in which I only read the Device ID of the Gyro in a while loop. Here is the pseudo code of this testcase so you have an idea how it works:while(1){ retVal_e = icm42688pReadRegister(ICM42688P_BANK_0_WHO_AM_I, &regV

Hi @Community member​ , Is there any common Linux image available for accelerating STM32MP1 based SoM, irrespective of eMMC (JEDEC Version 5.0/5.1 Complying) & DDR3 manufacturer.

..

root@stm32mp1:~# uname -a Linux stm32mp1 5.15.24 #1 SMP PREEMPT Wed Feb 16 11:56:41 UTC 2022 armv7l armv7l armv7l GNU/Linux root@stm32mp1:~# pacmd list-sinks-inputs No PulseAudio daemon running, or not running as session daemon. root@stm32mp1:~# alsamixer ALSA lib ../../alsa-plugins-1.2.6/pulse/pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: Access denied   cannot open mixer: Connection refused root@stm32mp1:~# root@stm32mp1:~# aplay /usr/local/demo/media/ST12266_269_full_technology-freaks_0160.ogg ALSA lib ../../alsa-plugins-1.2.6/pulse/pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: Access denied   aplay: main:831: audio open error: Connection refusedMy board is STM32MP157F-DK2. As expected I can't hear anything, but in SDK V3.X.X everything works fine.Please fix the bug as soon as possible.

hi, i'm stuck starting usbh_hs2 from u-booti can already start usbh_hs1 at boot, in order to load kernel and fs from an usb mass storage. i wish to do the same with usb_hs2, is that possible? is one configuration from DTS or from U-boot source code? ps. i'm starting u-boot from mmc, then detect usb mass storage and start alla the system from there thank you !!!

Hello All,forgive me if this as an obvious mistake but I'm completely new to TouchGFX. I'm using STM32 MPU, with Cube, FreeRTOS and TouchGFXI have created a page in TouchGFX using the digital clock object, I have created a TickEvent to update the clock.The Tick even is being called and if I put literal numbers into setTime24Hour, they are displayed correctly and can even be updated. The RTC is used throughout the rest of the code and is working fine, the code complies without any warnings.When I use the code (below) I only get 00:00:00 on the displayAny ideas?All the bestDren*****************************extern RTC_HandleTypeDef hrtc;void PageView::handleTickEvent(){ RTC_TimeTypeDef sTime; if ( HAL_RTC_GetTime(&hrtc, &sTime, RTC_FORMAT_BCD) != HAL_OK ) Fatal_Error(); digitalClock1.setTime24Hour(sTime.Hours, sTime.Minutes, sTime.Seconds);}

I have LCD COG with ST7586 Controller but my device must by drive this LCD by FMC ( backward compatibility ) How can I Drive this LCD from Linux ? I found driver stm32mp1-fmc2-nfc for using FMC by Micrel ETH but i'm not have any idea for use it for LCD.

Hello,I created a new project in STM32CubeIDE for my STM32MP157A by using STM32CubeMX. In it I enabled UART and FreeRTOS on CMSIS-RTOSv2 and that's all. I use the auto generated code.Then I wanted to use TraceAlyzer on top of FreeRTOS however, upon including#include "trcRecorder.h"In the FreeRTOSConfig.h I got a strange error:/Middlewares/Third_Party/FreeRTOS/Source/CMSIS_RTOS_V2/cmsis_os2.c:154: multiple definition of `SysTick_Handler'; ./Core/Src/stm32mp1xx_it.o:   ./CM4/Core/Src/stm32mp1xx_it.c:160: first defined hereThe SysTick_Handler is defined in both files, here are the implementations if it may help:in cmsis_os2.c :/* SysTick handler implementation that also clears overflow flag. */ void SysTick_Handler (void) { /* Clear overflow flag */ SysTick->CTRL;   if (xTaskGetSchedulerState() != taskSCHEDULER_NOT_STARTED) { /* Call tick handler */ xPortSysTickHandler(); } } #endif /* SysTick */In stm32mp1xx_it.c :/** * @brief This function handles System tick timer

I'm testing the Developer Package for STM32MP157c-dk2 demo board. Starter Pack is installed. When I compile the kernel as described in the Dev. Package's "README_HOW_TO.txt" file and update the kernel, The "Cube" example ceases running. It only says "No GCNANO GPU STACK capabilities to run 3D GPU demo. What I'm missing here ?The boot log says something about galcore time out.

I want to enable input capture functionality on our stm32mp157c based system. I am using Timer 1 channel 4 for the same and have made the necessary additions in the device tree as follows: &dma1{ status = "okay"; /* USER CODE BEGIN dma1 */ sram = <&dma_pool>; /* USER CODE END dma1 */ }; &dma2{ status = "okay"; /* USER CODE BEGIN dma2 */ sram = <&dma_pool>; /* USER CODE END dma2 */ }; &dmamux1{ dma-masters = <&dma1 &dma2>; dma-channels = <16>; status = "okay"; /* USER CODE BEGIN dmamux1 */ /* USER CODE END dmamux1 */ }; &timers1{ /* USER CODE BEGIN timers3 */ /* Enable DMA "ch1" for PWM input on TIM1_CH1 */ dmas = <&dmamux1 13 0x400 0x80000001>; dma-names = "ch3"; status = "okay"; /* USER CODE END timers3 */ pwm { pinctrl-names = "default", "sleep"; pinctrl-0 = <&tim1_pins_mx>; pinctrl-1 = <&tim1_sleep_pins_mx>; status = "okay"; /* USER CODE BEGIN timers1_pwm */ /* U

Hi everyone,I'm working on a custom STM32MP157 based board running custom Linux with Kernel v5.10.116. A LCD panel is connected using the LTDC display controller.I want to implement a splash-screen as soon as the power supply is on.I managed to add my panel interface in U-Boot and display my splash-screen but when the kernel is initialized the GPIOs connected to the LCD panel (reset-pin and power supplies commands) are reset and re-initialized so the LCD display is switched off and on.The final sequence is : U-Boot displays the splash screenthe kernel is launchedthe LCD display is re-initializedthe splash-screen is re-displayedSo there's a black screen for 2 seconds and I would like the splash-screen to remain displayed until the main application is launched.Is it possible in the kernel DTS files to add an option so the GPIO (maybe PMIC) drivers won't re-initializes the pins tied to the display ?I know it is possible with the TI drivers by adding "ti,no-reset-on-init" in the GPIO descr

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/ethernet/stmicro/stmmacCan anyone tell is this driver for some specific ST(?) IP, or for a runaway collection of various Synopsys based IPs? Does the ethernet controller of STM32MP1 work with this driver?

We are trying to read an analog value from a sensor (PF14 pin - A0 on Arduino connectors) and send it over UART (UART7 - PE7 for RX, PE8 for TX) for reading in the terminal of computer. We use M4 for this aim. Our final goal is to read the analog value over OPENAMP to be used on A7 side. But we want to be sure about the data integrity, and correctness of analog output as a first step. That's why we use UART7 through FTDI. We can read only "enclosed question marks" in the terminal. We are able to correctly read and graph analog readings with NUCLEO-STM32L432KC, using the same sampling rate and using USART1 and FTDI (although data resolution seems to be decreased significantly, compared to reading data over ST-LINK). Since ST-LINK is dedicated to A7 in STM32MP157F-DK2, it seems that it can not be used on M4 side (in Engineering Mode) for our aim.The pin configuration in A7 dts file is as follows.m4_uart7_pins_mx: m4_uart7_mx-0 {   pins {      

Next problem with my board is the RS485. I can send bytes, but can't receive because after sending once the DE stays always high. Without sending receive of course works.&uart5 { status = "okay"; pinctrl-names = "default", "sleep","idle"; pinctrl-0 = <&uart5_pins_a>; pinctrl-1 = <&uart5_sleep_pins_a>; pinctrl-2 = <&uart5_idle_pins_a>;   rts-gpios = <&gpioc 6 GPIO_ACTIVE_HIGH>; rs485-rts-delay = <0 0>; linux,rs485-enabled-at-boot-time; };uart5_pins_a: uart5-0 { pins1 { pinmux = <STM32_PINMUX('B', 6, AF12)>; /* UART5_TX */ bias-disable; drive-push-pull; slew-rate = <0>; }; pins2 { pinmux = <STM32_PINMUX('B', 5, AF12)>; /* UART5_RX */ bias-pull-up; }; };   uart5_idle_pins_a: uart5-idle-0 { pins1 { pinmux = <STM32_PINMUX('B', 6, ANALOG)>; /* UART5_TX */ }; pins2 { pinmux = <STM32_PINMUX('B', 5, AF8)>; /* UART5_RX */ bias-pull-up; }; };   uart5_sleep_pins_a: uart5-slee

Hi i want to access remotely my stm32mp157c-dk2 with graphical interface. I am running openstlinux-20-02-19 from starter package. I installed tigervnc (apt-get install tigervnc and apt-get install xauth) and start it by typing "vncserver". But when i connect to it (from vncviewer) only terminal shows up, nothing else. I tried to start some desktop session from this terminal by typing (weston / weston-start / dbus-launch weston-start / weston-launch) but nothing works. I also tried to modify ~/.vnc/xstartup and changed to :#!/bin/shunset SESSION_MANAGERunset DBUS_SESSION_BUS_ADDRESSexec dbus-launch weston-startBut after this change, only black screen shows up : /I am new to wayland/weston and vnc configuration. I hope somebody with more experience can help me with this.

Hi, i am trying to build linux image along with cortex-m4 firmware which developed using STM32CubeIDE,so for that i have copied a Stm32CubeIDE project under folder DistributionPackage/openstlinux-5.10-dunfell-mp1-21-03-31/layers/sources/m4projects-stm32mp1/Projects/STM32MP157C-DK2/Examples/TIM/project/project1/STM32CubeIDE/Added the project path in /DistributionPackage/openstlinux-5.10-dunfell-mp1-21-03-31/layers/meta-st/meta-st-stm32mp/recipes-extended/m4projects/ m4projects-stm32mp1.bbiam getting error as  arm-none-eabi-gcc: error: /home/akshay/project/stm32/DistributionPackage/openstlinux-5.10-dunfell-mp1-21-03-31/build-openstlinuxweston-stm32mp1/tmp-glibc/work/stm32mp1-ostl-linux-gnueabi/m4projects-stm32mp1/1.4.0-r0/build/STM32MP157C-DK2/Examples/TIM/Project/JCIProject1/out/Debug//home/akshay/project/stm32/DistributionPackage/openstlinux-5.10-dunfell-mp1-21-03-31/layers/sources/m4projects-stm32mp1/Projects/STM32MP157C-DK2/Examples/TIM/Project/Project1/STM32CubeIDE/Common.

I have problem to get USB to work. I'm using custom board but I know that USB works because if I boot the board with the delivered image (MyIR) the USB works. I'm using buildroot with the 5.10 kernel and the linux kernel configuration from bootlin git. In TF-A I have enabled CLK_USBPHY_HSE and CLK_USBO_USBPHY.Kernel device tree:&usbh_ehci { phys = <&usbphyc_port0>; phy-names = "usb"; status = "okay"; };   &usbh_ohci { phys = <&usbphyc_port0>; phy-names = "usb"; status = "okay"; };   &usbotg_hs { compatible = "st,stm32mp15-hsotg", "snps,dwc2"; phys = <&usbphyc_port1 0>; phy-names = "usb2-phy"; dr_mode = "host"; status = "okay"; };   &usbphyc { status = "okay"; };   &usbphyc_port0 { phy-supply = <&vdd_usb>; st,phy-tuning = <&usb_phy_tuning>; };   &usbphyc_port1 { phy-supply = <&vdd_usb>; st,phy-tuning = <&usb_phy_tuning>; };Kernel bootlog (I enabl

Hi I am working on a drivers for the various peripherals on the STM32. Let me take the GPIO as an example. GPIO BSRR is a write only register that I want to read and I need to read back always 0x00000000. Why?I made a bit-field struct on the whole GPIO block. That struct is accessed based on Register name and specific bit field. The processor can not operate on individual bits so the compiler translates the Bit field instruction in to a register read followed by mask and shift operations ending with a Register write. It's the compiler that manipulates individual bits in a register in this way.So the value of the write only register like a BSRR when it is read is important and needs to be 0x00000000 for a bit set operation.Here is my question, is the read back of a write only register like the BSRR well-defined in the design of the STM32 chip or is that value undefined.Question:Can someone tell me if the read back of Write only registers is well-defined as 0x0000000 for the STM32 family

I'm now trying to blink a LED on my STM32MP157-DK2 board.I have managed to run and even modify the GPIO_EXTI example, but I'd like to do this from scratch.1) I first created a project using CubeMX and wrote my code in the IDE.It seems that I can't use the BSP_LED_*** instructions as the build gives compilation errors : why can't I build my code when using these instructions ? Do I miss an include​ ?2) Then I tried to use the HAL_GPIO_*** instructions. This time, the build is successful, but the debug does not blink the LED.I have seen in the manual UM2367 that the blue LED is connected to PD11, so I try this:HAL_GPIO_TogglePin (GPIOD, GPIO_PIN_11); HAL_Delay (100); /* Insert delay 100 ms */but it doesn't blink. What did I miss?Thanks for your help.