Ask questions and find answers on STM32 microprocessors and dedicated embedded software solutions, such as Yocto SDK, Qt, and OP-TEE.
Most recent activity
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; }; };
dimensions are the most important thing and the ability to be chassis mountable. the resolution isn't as important but better resolutions wont hurt
How do I change the pin for the u-boot-stm32mp programmer mode at boot up?
The startup file is generated only once if I generate for the very first time.Where is information stored that file has to be generated?I am using STM32CubeMX version 6.6.1.
..
I want to create my own distro for OpenSTLinux but it seems like the envsetup.sh file is dependent on the distro.conf file being located in the meta-st directory. This is a little hard because I am trying to not modify the meta-st layer but am trying to build on it. What would be the best way to create my own distro.conf file that is usable by the envsetup.sh but storable in another layer. I am using a hardlink pointing to the other layer for now.https://wiki.st.com/stm32mpu/wiki/How_to_create_your_own_distribution
When I run bitbake openocd-stm32mp-native I get an issue baking the application but when I run bitbake openocd-stm32mp it works fine. Any thoughts why this might be?Edit: I was porting my layer from dunfel to kirkstone and I wasn't importing the open-st-linux.inc file. It had since changed to require the uninative support. Adding that to my machine config got it to work correctly.
I have the following DTS file and I have not been able to get the GPIO external interrupt working correctly. I have read this document on interrupt overviews, and tried to enable the EXTI to have control of the GPIOB pin 12. /dts-v1/; #include "stm32mp157.dtsi" #include "stm32mp15xa.dtsi" #include "stm32mp15-pinctrl.dtsi" #include "stm32mp15xxac-pinctrl.dtsi" #include "stm32mp15xx-dkx.dtsi" / { model = "STMicroelectronics STM32MP157A-DK1 Discovery Board"; compatible = "st,stm32mp157a-dk1", "st,stm32mp157"; chosen { stdout-path = "serial0:115200n8"; }; button { compatible = "test,button"; input-gpios = <&gpiob 12 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>; //Works with pull-up once the driver is loaded. interrupts-extended = <&gpiob 12 IRQ_TYPE_EDGE_FALLING>; interrupt-names = "qwerty"; status = "okay"; }; led { extern-led { compatible = "test,led"; gpios = <&gpiob 10 GPIO_ACTIVE_HIGH>; linux
On ecosystem 4.1 and git version 2.39.1 there is an error when you do devtool modify tf-a-stm32mp and bitbake tf-a-stm32mp. The error is Command '['git', 'submodule--helper', 'list']' returned non-zero exit status 128. After a bit of searching there is a patch that needs to get applied in order for it to work since that git version no longer supports that command. Patch is located at https://git.yoctoproject.org/poky/commit/?id=0533edac277080e1bd130c14df0cbac61ba01a0c . Maybe that can get patched in?
I would like to set the low-power timer as wake up source to wake up the Linux from sleep mode with some periodic time, let's see every 5 minutes. All I have found is pwm and counter examples here: https://wiki.st.com/stm32mpu/wiki/LPTIM_device_tree_configuration
I've tried following the examples given here and here, but it will not work. I just want to enable a pull up resistor in the DTS file. Here is my DTS file. If anyone can please tell me why it's not working I would appreciate it. /dts-v1/; #include "stm32mp157.dtsi" #include "stm32mp15xa.dtsi" #include "stm32mp15-pinctrl.dtsi" #include "stm32mp15xxac-pinctrl.dtsi" #include "stm32mp15xx-dkx.dtsi" &pinctrl { button_pins_a: button-0 { pins { pinmux = <STM32_PINMUX('B', 12, GPIO)>; bias-pull-up; }; }; }; / { model = "STMicroelectronics STM32MP157A-DK1 Discovery Board"; compatible = "st,stm32mp157a-dk1", "st,stm32mp157"; chosen { stdout-path = "serial0:115200n8"; }; button { compatible = "test,button"; pinctrl-names="default"; pinctrl-0 = <&button_pins_a>; status = "okay"; }; led { extern-led { compatible = "test,led"; gpios = <&gpiob 10 GPIO_ACTIVE_HIGH>; linux,default-trigger = "cpu";
I want to generete interrupt for specific value of TIM->CNT TIM1->DIER |= TIM_IT_CC1; TIM1->CCR1 = myVal;I use only above. if(TIM_GetITStatus(TIM1,TIM_IT_CC1) != RESET){ //when interrupt generete here ,CCR1 is not equal my value } I'm so confused why am I doing wrong?
Can some one help me to know what would be the default factory OTP settings on the processor - STM32MP157FAA1 - or should it be set by the User? Does the Default Comes with SDMMC1 set for the Boot?If I need to change from SDMMC1 to SDMMC2 as the Primary boot what is the procedure and which tool has to be used for it?I need the secondary boot as USB how to set this.
Hi,We want to boot cortex M4 from cortex A7 in baremetal in RETRAM. We have followed below steps 1.we are setting BOOT MCU bit in RCC global control register(Offset :0x10C). 2.I am restting MCURST bit in RCC global reset control set register(offset:0x404).3.setting MCU Boot enable bit in RCC boot control register.am i doing in correct way or not? if not can you tell the procedure of waking up the cortex M4 from cortex A7 in RETRAM.
Hi,I encounter an extraordinary problem with STPMIC1APQR. When powering on the board without loading any images voltages on each section are as described in the PMIC documentation. When I start fsbl the voltages change, and increase not as described in the dts.My dts configuration is as follows&i2c4{ pinctrl-names = "default", "sleep"; pinctrl-0 = <&i2c4_pins_mx &i2c4_pins_z_mx>; pinctrl-1 = <&i2c4_sleep_pins_mx &i2c4_sleep_pins_z_mx>; status = "okay"; /* USER CODE BEGIN i2c4 */ i2c-scl-rising-time-ns = <185>; i2c-scl-falling-time-ns = <20>; clock-frequency = <400000>; /delete-property/ dmas; /delete-property/ dma-names; pmic:stpmic@33{ compatible = "st,stpmic1"; reg = <0x33>; interrupts-extended = <&exti_pwr 55 IRQ_TYPE_EDGE_FALLING>; interrupt-controller; #interrupt-cells = <2>; status = "okay"; regulators{ compatible = "st,stpmic1-regulators"; buck1-supply = &l
I have a custom board with a STM32MP157AAB3 and I am trying to boot it with the SD card. I have tested the SD card on a STM32MP157C-DK2 and it boots to Linux fine. When I probe the SD card lines, I can see the clock is toggling for a long time and the CMD pins is also toggling however nothing happens on the D0 pin, it is held high (3V3)
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.