Product forums

Cannot wake from Stop mode using LPTIM1Board: STM32N6570-DK (STM32N657X0, Cortex-M55)RTOS: Zephyr 4.4.0Goal: Enter Stop mode and wake periodically via LPTIM1 auto-reload interrupt (~200ms)What works:Sleep mode (WFI without SLEEPDEEP) — enters and wakes correctly from GPIO EXTI and LPTIMLPTIM1 initialization — confirmed running, ISR fires (verified via counter incrementing in HAL_LPTIM_AutoReloadMatchCallback)LPTIM1 EXTI line 52 enabled — EXTI->IMR2 |= EXTI_IMR2_IM52 via __HAL_LPTIM_LPTIM1_EXTI_ENABLE_IT()NVIC LPTIM1_IRQn enabled — interrupt registered and working in normal (non-Stop) operationClock restore after Stop — SystemClock_Restore() re-enables HSE, PLLs (PLL1/2/3), IC muxes back to 800 MHzWhat does NOT work:Stop mode entry → CPU never wakes. After HAL_PWR_EnterSTOPMode(PWR_MAINREGULATOR_ON, PWR_STOPENTRY_WFI), the MCU halts permanently. No interrupt wakes it.LPTIM1 configuration:__HAL_RCC_LPTIM1_CLK_ENABLE();// Clock: LSI (~32 kHz)RCC_PeriphCLKInitTypeDef pclk = {0};pclk.Per

Hi ST community,We are evaluating motor-control architecture for a 3-phase BLDC/PMSM ESC project based on STM32G431 / STSPIN32G4.Currently we understand that STM32 MCSDK supports both:- FOC control projects- 6-step / trapezoidal control projectsHowever, we would like to clarify whether MCSDK officially supports runtime switch-over from 6-step control to FOC control in the same firmware project.Our target concept is:1. Start the motor with 6-step control or open-loop 6-step startup.2. After the motor reaches a sufficient speed / stable rotor position estimation, switch to FOC control.3. Continue running with FOC current loop and SVPWM.Questions:1. Does MCSDK officially support runtime switch-over from 6-step control to FOC control in one generated project?2. If not officially supported, is there any ST reference implementation, application note, or recommended method for implementing this handover?3. Can MCSDK-generated 6-step and FOC control modules coexist in one runtime while sharing

I have been trying to download STM32CubeIDE for Windows, but the download never starts. Someone can help me with this issue?

Hi,I wanted to give Visual Studio Code a try and converted an existing STM32CubeIDE project. In the original project, the main.c (in Core/Src directory) file was compiled using g++, since it has some C++ content. However, VS Code invokes gcc, and therefore, build is not successful. How can I change this?One other thing, I noticed when converting the project, all source files are copied to the new location, but the .ioc file is not. Is this intended behaviour?

I started with the MC workbench and installed X-Cube-MCSDK Version 6.4.2. After installation the MC Workbench is opened, but the dialog is complete empty (except the caption). The behaviour is the same if i start the workbench via the desktop icon or as administrator.

Are there any Dual Core LoRaWAN Application examples for the STM32WL55CC that use the STM32Cube FW WL V1.5.0 (LBM) libraries?  If  there aren’t, will this be supported in the future? Thanks,Nick

Am using Engine Control eTPU Library (AN4907SW) in the SPC563M64L5 device.And in the source files, there is a piece of code which needs to be enabled for MPC5500 devices as it is mentioned in the comment that “an errata 2477 is present on MPC5500 devices”. Since SPC563M64L5 device is almost similar to MPC5634M device which is MPC5500 family as both jointly developed. does these errata applicable to SPC563M64L5 as well?

i've just installed all necessary requirements for the STM32 vscode extension however it doesn't seem to launch cube mx or mcu finder when i click launch from vscode. not sure if its incorrect paths or permission issues?please see the screenshot for the path settings

STM32CubeMX generates inconsistent indentation in MX_Recieve_Q_Build:/** * @brief CLIP application Data scenario Receive queue build * @param None * @retval None */static void MX_Receive_Q_Build(void){ /* LPBAM build variable */ LPBAM_DMAListInfo_t pDMAListInfo_LPGPIO = {0}; LPBAM_GPIO_PinSeqFullAdvConf_t pReadPinSeqFull_LPGPIO = {0}; LPBAM_COMMON_TrigAdvConf_t pTrigConfig_LPGPIO = {0}; LPBAM_COMMON_DataAdvConf_t pDataConfig_LPGPIO = {0}; /** * Receive queue CLPReceiveBits build */ pDMAListInfo_LPGPIO.QueueType= LPBAM_LINEAR_ADDRESSING_Q; pDMAListInfo_LPGPIO.pInstance= LPDMA1; pReadPinSeqFull_LPGPIO.Pin = LPBAM_GPIO_PIN_0; pReadPinSeqFull_LPGPIO.Size = 13; pReadPinSeqFull_LPGPIO.pData = (uint32_t*)&receivedBits[0]; if (ADV_LPBAM_GPIO_ReadPinSequence_SetFullQ (LPGPIO1, &pDMAListInfo_LPGPIO, &pReadPinSeqFull_LPGPIO, &Receive_Q_CLPReceiveBits_Desc, &Receive_Q) != LPBAM_OK) { Error_Handler(); } pTrigConfig_LPGPIO.TriggerConfig.TriggerM

I’ve started from the LWIP TCP echo server with FreeRTOS example from ST and have made a *.ioc2 file to support that example. The issue is that I’m starting from the NUCLEO-C5A3ZG (which I’ve configured the *.ioc2 project), but intend to use a STM32C593 in my final product. My understanding was that STM32CubeMX would allow switching microcontrollers, but keeping the similar configuration settings (e.g. LWIP, FreeRTOS, etc.). I’d like to have the project required configuration settings managed in a tool like CubeMX2, but this will not be possible/feasible if I can’t make changes without having to start completely from scratch every time we make a change. Is there a setting somewhere that I’ve missed to allow switching processors? Is this a planned feature that may not yet be released? Thanks in advance.

Hi,We are using the ST25R3920B NFC reader IC along with the NXP S32K312 MCU running an AUTOSAR OS for NFC card detection.We have observed that, after the NFC wake-up event, the NFC initialization and polling sequence takes approximately 300 ms before a card is detected. This startup time is longer than expected and is impacting our application requirements.Could you please suggest any configuration changes, RFAL optimizations, or best practices to reduce the NFC initialization and polling time? If there are any recommended settings for use with an AUTOSAR-based system or the ST25R3920B that can help improve startup performance, we would greatly appreciate your guidance.Thanks,Anitha

I have made a bootloader for STM32F4 with dual bank and single bank structure. I have done so rudimentary testing with it and written test logs in a md file. Here is the link:-https://github.com/Tank4676/stm32-dualslot_bootloader

Yocto 5.0To build Yocto I follow simple instruction from bootlin bootlin.com/doc/training/yocto/yocto-stm32mp1-labs.pdfBut I get a corrupted Poky distro: 8th partition ("/mnt/part08") is empty (see screenshot below). Why?File "$HOME/stm32mp1_scarthgap/build/tmp/work/stm32mp1-poky-linux-gnueabi/core-image-minimal/1.0/temp/log.do_image_stsplitpartitions.2582911" looks suspicious```NOTE: image_link_name -> "core-image-minimal-stm32mp1.splitted-rootfs"NOTE: image_name -> "core-image-minimal-stm32mp1.splitted-rootfs-20260602150830"du: cannot access '/home/q/stm32mp1_scarthgap/build/tmp/work/stm32mp1-poky-linux-gnueabi/core-image-minimal/1.0/splitted_rootfs/usr/bin/dumpleases'du: cannot access '/home/q/stm32mp1_scarthgap/build/tmp/work/stm32mp1-poky-linux-gnueabi/core-image-minimal/1.0/splitted_rootfs/usr/bin/printf'```My repo to reproduce stm32mp1_scarthgap.Yocto 4.0The same steps I can do with end-of-life Yocto 4.0. And it will works (because 8th partition is not empty, I can see man

Hi, I use STM32H7 with STCUBE 11.1.I use RNDIS module  usbd_cdc_rndis.h to communicate with a PC.Sometimes when the PC sends a frame the STM32 replies with NAK, here is the sequence that repeats:SYNCPID OUTAddressCRCEOPSYNCPID DATA0data 30 bytesCRCEOPSYNCPID NAKEOPWhat might be the issue? Can I change the USB interval (CDC_RNDIS_FS_BINTERVAL)?BRJonas

what maximum current the DAC_output / ADC_input pin can hold if shorted to the ground. with internal buffer Off/On? STM32H753zi.

I am doing g3-PLC test by connecting two board of EVLKST8500GH-2  according to ST G3-Hybrid PLC&RF GUI Quick start guide, but i am not clear test envirionment 1) COM port of PC is connected with ST8500GH-MB or  NUCLEO-G070RB, when i connect with  NUCLEO-G070RB port is recognized but when i connect with ST8500GH-MB, port is not recognized in the PC.   2) I am using 30V(AC) power for Power line because " ST8500 Hybrid PLC&RF Connectivity Development Kit UserManual"  Safety precautions guide of " The kit is intended for use on extra low voltage (ELV): <50 V AC, <75 V DC." but i am not clear this 30V(AC) is enough for PLC. i want to know the level of Power   3) I want to know power line connection between two board EVLKST8500GH-2. serial or pallel ?

Dear ST Support Team,I am using the STM32MP157F-DK2 evaluation board with OpenSTLinux (Linux kernel 5.15).I am interfacing a Telit LE910C1-IN LTE modem through the USB Host interface. The modem is successfully detected by lsusb (VID:PID 1bc7:1201), and dmesg confirms successful USB enumeration. However, no /dev/ttyUSB* devices are created, preventing AT command communication.I also verified that the kernel configuration shows:# CONFIG_USB_SERIAL is not setCould you please provide the recommended procedure to enable USB modem support for the Telit LE910 on STM32MP157F-DK2? Specifically, I would like to know the required kernel configuration, drivers, packages, or any additional Device Tree or software changes needed to create the /dev/ttyUSB* interfaces.Below is relevant screenshot for reference.Thank you.

 Dear STMicroelectronics Support,In our application, the STM32H7B3I-DK board is used in a "shield" configuration: it is mounted on a carrier/daughter board(PHOTO 2) (via the Arduino connectors CN19/CN20/CN10/CN11) which supplies its power. The daughter board therefore injects a 5V voltage directly onto CN19, pin 1 (5V_VIN), without going through a USB supply or through the standard VIN input of the kit.Power configuration5 V is applied to CN19, pin 1 (5V_VIN). JP1 is configured in the 5V_VIN position. VIN (CN19, pin 8) is left unconnected.MeasurementsVoltage before R114 (1 kΩ): 5.0 V Voltage after R114: 1.6 VThis corresponds to a voltage drop of approximately 3.4 V across R114, which indicates a current of about 3.4 mA flowing through the resistor.I would like to better understand whether this behavior is expected and the purpose of R114 in this circuit.Could you please clarify the following points?Is this voltage drop across R114 normal when powering the board through 5V_VIN? What is

Hi, I am planning to use IMU ASM330LHB for my project and test the sensor functionality using board STEVAL-MKI236A.I want to know whether I can plug STEVAL-MKI236A into the DIL24 connector of the SensorTile.Box PRO and test the functionality using SensortTile.box smartphone app ST BLE Sensorhttps://community.st.com/mems-and-sensors-62/getting-started-with-sensortile-box-192I want display the below values as mentioned on the link.Is it possible? Thanks,Sucheta

STM32CubeMX 6.18.0MCU: STM32H563RIT6To my understanding, this uses STM32CubeH5 1.7.0 Start a new project and enable ThreadX and NetX Duo.In “NETXDUO Mode and Configuration”, enable “NX Core”, “Crypto” and “TLS”In configuration, parameter column “NetXDuo” there are check-boxes for:TLS CORENX_SECURE_TLS_ENABLE_TLS_1_1NX_SECURE_TLS_ENABLE_TLS_1_3NX_SECURE_TLS_TLS_1_2_ENABLEDNX_SECURE_TLS_TLS_1_3_ENABLED This is a bug.According to https://github.com/eclipse-threadx/rtos-docs/blob/1e36a62618de3771c973196e7648cba50d19cf1f/rtos-docs/netx-duo/netx-duo-secure-tls/chapter2.md#configuration-options the proper configuration options areNX_SECURE_TLS_ENABLE_TLS_1_3 Defined, this option enables TLSv1.3 mode. TLS 1.3 is the newest version of TLS and is disabled by default. NX_SECURE_TLS_ENABLE_TLS_1_0 Defined, this option enables the legacy TLSv1.0 mode. TLSv1.0 is considered obsolete so it should only be enabled for backward-compatibility with older applications. NX_SECURE_TLS_ENABLE_TLS_1_1

Good day,We are using a composite USBX device class combining CDC and MSC over USB Full Speed, built on X_CUBE_AZRTOS-H7 version 3.3.0 (USBX 6.4). During testing we discovered that a certain Windows PC sends a MODE SELECT(10) command (opcode 0x55) and causes an endpoint stall.After a rather long debugging session, it was found that the USBX source _ux_device_class_storage_mode_select() is explicitly not implemented — it stalls the OUT endpoint, UX_FUNCTION_NOT_SUPPORTED (which is not checked in the thread) and never recovers:The MODE SELECT(6) SCSI command is not even implemented and the storage thread falls through to the default case, also triggering a endpoint stall. So:- Are there any plans to implement these MODE SELECT(6/10) commands properly in a future USBX release?- Does anyone already have a workaround for this?- Wouldn't it be cleaner to reply with an ILLEGAL REQUEST instead of stalling the endpoint?System details:- MCU: STM32H7- USBX version: 6.4 (X_CUBE_AZRTOS-H7 3.3.

When using the FDCAN peripheral on a STM32H743 or a STM32H753 and the message filters are setup to only accept certain messages, does the FDCAN hardware ACK a valid message that is rejected by the message filter?

Hi everyone,I wanted to share a frustrating issue I encountered in STM32CubeMonitor while working on a complex project (vienna_stm32g474), hoping to save some headaches for fellow developers.The Problem:When updating or switching to a new version of the .elf file in the Edit variables node / Edit exe-config node, the entire selected variable list (which contained around 30 complex nested structures) gets completely wiped out/deselected. Interestingly, this behavior occurred only in one specific node, while other lists on different flows updated perfectly fine, even though the variables still existed in the new file.The Root Cause:After a lot of debugging, we found out that STM32CubeMonitor handles the .elf file path/name as a strict unique hash key inside the flows.json architecture.If you rename the file (e.g., creating a backup like project-Copy.elf) or switch paths manually in the UI dropdown, the internal parser treats it as an entirely new project schema. Instead of safely migrati

I am working with an STM32 microcontroller and a VL53L0X sensor. The sensor readings are transmitted over UART1 at 115200 baud, 8N1.I have verified: UART initialized at 115200 baud, 8N1, no parity XCTU terminal set to ASCII mode (Hide Hex enabled) Line endings set to \r\n Any suggestions for reliable output?Numeric values are printed correctly, but the text parts like "Distance" and "mm" are missing or appear as dots in XCTU’s terminal. For example, instead of:CodeDistance: 25 mmI see:CodeD..ta..e: 25 mm

I am working with an STM32C542 processor using STM32CubeMX2 and the new HAL2 library framework. CubeMX2 generated the code and I imported the CMake project into STM32CubeIDE v 2.1.1.I am trying to configure Timer 2 for a basic 1-second interrupt to toggle an LED, but the callback function is never reached. Here is the initialization generated by CubeMX2 in mx_tim2.c:/* Includes ------------------------------------------------------------------*/#include "mx_tim2.h"/* Private typedef -----------------------------------------------------------*//* Private define ------------------------------------------------------------*//* Private macro -------------------------------------------------------------*//* Private variables ---------------------------------------------------------*//* Private functions prototype------------------------------------------------*//* Exported variables by reference--------------------------------------------*/static hal_tim_handle_t hTIM2;//HAL_TIM_RegisterUpd