Solved

Hi everyone! I'm working with the NFC07A1 board associated with the Nucleo L053R8, with the intention of being able to perform ADC readings. I configured everything(ADC, pin, NFC07A1, etc.) on CubeMx, and then, opened the generated file on CubeIde. After writing the code for reading the ADC in the main file, i tried to run it, but even though there were no errors in the code, the  "startup_stm32l053r8tx.s" tab opens by pointing to line 51 (as well as Reset_Handler: ldr r0, =_estack). Consequently, the values acquired via the ADC are not printed on the screen, but the only thing printed on the sreen is "welcome to x-cube-nfc7 example". Could you help me solve the problem?

I am working on converting projects from STM32F745VET to STM32U575VGT. Part of the startup routine of the projects is checking for flash errors using the CRC peripheral. The STM32F7 projects initialize a DMA channel in the following way: void MX_DMA_Init(void) { /* DMA controller clock enable */ __HAL_RCC_DMA1_CLK_ENABLE(); __HAL_RCC_DMA2_CLK_ENABLE(); /* Configure DMA request hdma_memtomem_dma2_stream1 on DMA2_Stream1 */ hdma_memtomem_dma2_stream1.Instance = DMA2_Stream1; hdma_memtomem_dma2_stream1.Init.Channel = DMA_CHANNEL_0; hdma_memtomem_dma2_stream1.Init.Direction = DMA_MEMORY_TO_MEMORY; hdma_memtomem_dma2_stream1.Init.PeriphInc = DMA_PINC_ENABLE; hdma_memtomem_dma2_stream1.Init.MemInc = DMA_MINC_DISABLE; hdma_memtomem_dma2_stream1.Init.PeriphDataAlignment = DMA_PDATAALIGN_WORD; hdma_memtomem_dma2_stream1.Init.MemDataAlignment = DMA_MDATAALIGN_WORD; hdma_memtomem_dma2_stream1.Init.Mode = DMA_NORMAL; hdma_memtomem_dma2_stream1.Init.Priority = DMA_PRIORITY_LOW; hdma_memtomem_dma2

ST moderator: post split from this thread. Hello mƎALLEm, Thank you for your confirmation on this issue. I would like to provide some additional information. I have also encountered the same problem on the STM32F405RGT6. In STM32CubeMX, when I configure both HSE or LSE to "Bypass Clock Source" mode, the tool insists on reserving PH1 (OSC_OUT) or PC15 (OSC32_OUT) as RCC pins. It blocks me from configuring them as regular GPIOs, even though the hardware (as you've confirmed) supports it. Furthermore, I tested this on the STM32F446RE and STM32F446RC using the latest CubeMX, the problem still exists on those devices as well. Regarding the internal tickets you mentioned (220390 for documentation, 222721 for CubeMX), may I kindly ask: Has the CubeMX fix (ticket 222721) been implemented in any release yet? If not, is there an estimated timeline for when we can expect this fix? I understand if you cannot share internal details, but any update would be very helpful fo

Hi there, im using Nucleo-F446RE , ST HAL and CubeMX, and im learning to configure the clockI use HSE Bypass mode (MCO from the st-link in the nucleo), everything perfect hereIn the RM i found out that, when using HSE BYPASS mode, PH1 (OSC_OU) should be left in HI-Z state What does HI-Z means in STM32 MCUs? does it mean configuring the pin as digital input? or it means configuring the pin as analog input?Or it depends?   When selecting HSE BYPASS MODE the chip image in the .ioc file gets set like this: But if i try to  set PH1 (OSC_OUT) as GPIO a conflict is generated, so, how can i set the state of PH1 as HI-Z?   Also, why does PH1 gets reserved and configured in the chip as OSC_OUT? is this to avoid configuring it as another thing?And finally, what it seems very weird to me, why the clock por GPIOH is enabled when CubeMX generates the code if i cant use PH1 as a normal GPIO? (im not using any other PHx PIN)   Thanks in advance and sorry for the english, not a n

Here are the logs and waveforms. The slave device of IIC is unable to raise the SCL response. The data cannot be sent out either. The code is provided in the attachment.HAL_I2C_AddrCallback: 开始接收数据接收到字节[0]: 0x40接收到字节[1]: 0x03接收到字节[2]: 0x22接收到字节[3]: 0xFE接收到字节[4]: 0xBEHAL_I2C_ListenCpltCallback: 开始接收数据接收到字节[0]: 0x41HAL_I2C_ListenCpltCallback: 开始发送数据发送字节[0]: 0x05发送字节[1]: 0x62发送字节[2]: 0xFE发送字节[3]: 0xBE发送字节[4]: 0x30发送字节[5]: 0x31 

Module / setup- Module: ST87M01-1301- Host: STM32-class MCU over UART, 115200 8N1, no flow control- Carrier: 1NCE NB-IoT (auto-PDP on CID 5)- AT manual reference: v3.1, 2025-10-06Current sleep-related configuration16:34:39.720 -> === AT readbacks ===16:34:39.720 -> >>> AT+CGMR16:34:39.720 -> <<< A:2.7.0-M:2.7.0-S:2.7.016:34:39.720 -> <<< OK16:34:39.720 -> >>> AT#SLEEPMODE?16:34:39.720 -> <<< #SLEEPMODE: 1,5,016:34:39.720 -> <<< OK16:34:39.720 -> >>> AT#WAKEUPEVENT?16:34:39.720 -> <<< #WAKEUPEVENT: 15,316:34:39.720 -> <<< OK16:34:39.720 -> >>> AT#SLEEPIND?16:34:39.720 -> <<< #SLEEPIND: 0C16:34:39.720 -> <<< OK16:34:39.720 -> >>> AT#RINGPIN?16:34:39.720 -> <<< #RINGPIN:0,20,1,10016:34:39.720 -> <<< OK16:34:39.720 -> >>> AT+CPSMS?16:34:39.847 -> <<< +CPSMS: 1,,,"10010100","0000111

Dear ST,Now I'm testing my VL53L7CX sensor that is on the package P-NUCLEO-53L7A1 in Autonomous Mode with integration time = 2ms, ranging freq. = 4Hz and 4X4 Resolution, the attached screen-shot represents the output current related to my integration time and it's typically 2ms.My question is about the added peaks after the integration time peak, Why could this happen?and, How can I eliminate or reduce it?Knowing that the duration of these peaks illustrated in the other screen-shot attached.Thank you.    

With the recent split of STM32CubeIDE and STM32CubeMX, I'd like to propose a dark mode option be added to STM32CubeMX.In consideration of the competing priorities for STM's software development team, I have two suggestions for how this proposal could be implemented:The first suggestion is the typical route: STM's in-house software development team add the UI theming and inputs to switch between dark and light mode.The second suggestion is less typical: make STM32CubeMX open source and let the larger software community assist with adding dark mode. Perhaps the source could be placed alongside other repositories in STM's current GitHub account....The benefits of adding such an option would be as follows:Consistency with STM32CubeIDE, from which STM32CubeMX was split from (STM32CubeIDE already has a dark mode)Consistency with the vast majority of other software in the industryConsistency with what has become a common user experience across operating systems, browsers, and setups in g

Hi, We are planning to use STM32H743ZI for our project. Our requirement is to interface a 7-inch LCD touch display with 1024x600 resolution using a 24-bit RGB interface (RGB888) through LTDC. Can STM32H743ZI reliably support this display resolution? Also, what frame rate can realistically be achieved with this configuration? Are there any important hardware or performance considerations before selecting this MCU? Any suggestions or reference designs would be helpful. Thanks.

Hello There,I am currently trying to use the ST25R200 with the X-CUBE-NFC10 Software package.First thing am not sure about: In the "Software Packs Component Selector" I have to configure the "Board Extension NFC/NFC10A1" even when i don't plan to use this board. Otherwise i get a warning that "NFC10Boardlface" requires "NFC/NFC10A1". If I don't select the board part, I get a simmilar warning from the RFAL component.If i either don't add NFC/NFC10A1 in the component selector or don't select "Board Part NFC10Boardlface" in the Mode selection for the X-CUBE-NFC10 package, CubeMX seems to have problems generating the header "nfc_conf.h", which i have attached to this post.This is how the configuration looks, which generated nfc_conf.h:Am I using this library not correctly? Or rather which components of this library am i supposed to configure if i want to use the library with a custom board based on the ST25R200?Best Regards, Cecil

I have created a firmware for a STM32L010F4Px microcontroller.I was able to Connect and Download Firmware by using ST-LINK V2.For some reason, I can't connect to the MCU at the moment by using CubeProgrammer + ST-LINK V2.Instead, I can connect/debug my microcontroller by using a SEGGER J-Link Ultra+ + J-Flash tool.The log from CubeProgrammer doesn't give me much details:13:28:34 : UR connection mode is defined with the HWrst reset mode13:28:34 : ST-LINK SN : 37FF71064E573436D2C1144313:28:34 : ST-LINK FW : V2J47S713:28:34 : Board : --13:28:34 : Voltage : 3.28V13:28:34 : Error: Unable to get core ID13:28:34 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication

I'm working on STM32mp25f-EV1, i have downloaded FLASH-stm32mp2-openstlinux-6.6-yocto-scarthgap-mpu-v26.02.18 package but i'm facing problem while accessing SSH.

Hello, I'm trying to configure my SAI to receive TDM packets from my external ADC. For some reason, no matter what sample rate I choose, the real audio and error between selected is always 0. I've tried changing the clocks to the SAI1 module to 50 and 100 MHz, but it didn't change anything. Is this a visual bug with CubeMX or is it something with how I'm configuring the peripheral? Thanks.  

Excuse me, how can I implement this kind of loadingI'm really at a loss for ideas. Please help me out, thank you

Hi all, I'm planning to use USB (DFU mode) for production programming of the STM32C071K8U6 — including the very first firmware upload. The board has no external crystal; I intend to rely solely on the internal RC oscillator.   A few questions: 1) Is USB DFU feasible on this specific part without an external crystal? I've read that not all STM32 variants support USB boot without an external crystal (due to clock accuracy requirements for USB). Can anyone confirm whether the STM32C071K8U6's internal oscillator is sufficiently accurate for this?   2) Are there any specific hardware or configuration requirements I should be aware of for first-time USB DFU programming on this part? As the moment I just have the two USB traces connected to the USB connector but no 5V (VBUS) connected anywhere to the micro. I also have a pushbutton on the BOOT0 pin.   3) What USB speed does the built-in bootloader use, and is it possible to force a lower speed? The reason I ask is that the USB

Hi, we have purchased stm32h750vbt6 microcontroller for analog signal validation with 10k potentiometers to integrate with game controller joystick especially joy.cpl using windows 10 OS.   We have dealt with DMA Circular mode configuration pointing cortex-M7 DRAM to 0x30000000 to retrieve the analog signals associated with respective 10k potentiometers. Totally we have four analog pins such as PA0,PC0,PA3 and PC5 from ADC1 & ADC2 with proper distinguished rank allocation alongside desired maximum sampling cycles but although we have altered and tested with different values of this above configuration it ended up with ADC channel leakage which is declared 16 bit ADC.    Moreover we have tried adding external 100nf capacitors to avoid these linkage but failed.    We kindly request you to resolve the ADC channel leakage in our current stm32 Project. Our entire stm32 project attached for your reference and fault identification.  

I am using the Analog Devices EVAL-ADE9430 Evaluation board for testing one of their devices. The Evaluation board uses the NUCLEO-144 STM32F413ZH processor. I am using the Keil uVision development setup to run and debug code.  I am specifically concentrating on the SPI Bus Driver and the timing. I have no previous experience with STM Devices and how the SPI transfers happen in the processor. so I apologize a head of time.  My question is very basic I am trying to understand how the NUCLEO-144 STM32F413ZH board is transmitting the data over the SPI Bus. What setup is involved and what kicks off the actual transmission in the the HAL_SPI_Transmit() code below. The code i am using is transmitting 8 bits at a time.  The Chip Enable (SS) is set active prior to this code. I see a structure called hspi that has a bunch of parameters that are initialized at line 29 below By single stepping know when line 108 below executes I can see 8 bits of data on my scope. I

DeviceSTM32H563ZIT6, single binary (no separate bootloader), dual-bank OTASetup Bank1: Current running firmware (original)Bank2: New OTA firmware (potentially corrupted)IWDG: Started in Bank1 before swapOTABootSafetyCheck: In Reset_Handler of every binary buildBKP0R: Boot counter set before swapProblemAfter bank swap, if Bank2 firmware is corrupted and Reset_Handler never executes:  Bank swap → resetCPU reads 0x08000000 → SP (may be valid)CPU reads 0x08000004 → Reset vector (may be valid)CPU jumps to Reset_Handler addressReset_Handler code is corrupted → garbage instructions → crashOTABootSafetyCheck never runsBoot counter never incrementsIWDG fires → reset → same crash → infinite loopRollback never happensBank1 original firmware never recoversDevice is permanently stuck What We Have Tried1. OTABootSafetyCheck in Reset_Handler  asmReset_Handler: ldr r0, =_estack mov sp, r0 bl OTABootSafetyCheck ; before SystemInit and main bl SystemInit bl __libc_init_array bl

Hello,I am an engineering student working on my senior graduation project using the STEVAL-WBC2TX50 evaluation board. I need the STSW-WBC2STUDIO (or the updated WPSTUDIO) GUI to configure the board, but all official links on the ST website return a 404 error.Could you please provide a working download link or the installer files? My project exhibition is approaching soon, and this is a critical blocker.Thank you for your support.

ST moderator: updated the title to be more concise according to the below exchanges. Hello All,   I am facing a problem for debugging one of the board which uses stm32h7 controller. I am not sure why this is happening but on other board I am able to debug it, but for first one its not working. Though the code and debug config settings are same for both the board and using same system to debug both, but on one board I am able to debug while on other its is not. so could you please tell me what I can try to resolve this issue.   Thanks, SD 

Hi, I have all configured using internal loop FDCAN1 and there is not working on my STM32G474RE-Nucleo board 

Hi, We are busy making a setup with 2 nucleo-c092rc boards. Our first test was to send from board 1 to board 2 by the integrated CAN interface on these boards. We started at 1Mbits and this worked great. Also on 4Mbits the setup worked great. But we also want to test this on 8Mbits and now the transmitter is not sending correctly. We only see that the arbitration phase is send out and a couple of bits of the data part, but then the transmitters stops sending. We have tried with internal HSI(48Mhz) and external HSE crystal which is also 48Mhz on the nucleo boards.  We calculated the values for the SyncJumpWidth and timeseg1 and 2 and also tested with values slightly altered. hfdcan1.Init.DataPrescaler = 1; hfdcan1.Init.DataSyncJumpWidth = 2; hfdcan1.Init.DataTimeSeg1 = 2; hfdcan1.Init.DataTimeSeg2 = 3; But we allways have the same outcome. Sometimes it's not sending anything and sometimes only a small part of the total message of 64 bytes. What could be the issue here?  

This is some feedback for the STM32C5 OEMiRoT example provided by ST.This is based on the STM32C5-MCU-HAL2.0.0 pack download 06-05-2026.Attached you can also find the CMake Config files for the example, specifically for the NUCLEO-C542RC board.General Bug Provisioning Python ScriptThe provisioning python script has a small bug when it comes to the prebuild script which adjusts the linker files.These files are compiler specific so the correct adjustment function needs to be called.This compiler dependent code is missing in the `_update_linker_define()` function in `STM32C5-MCU-HAL/rot/rot_provisioning/helper/project/project_generic.py` starting at line 318:linker_path = self.config.get_compiler_linker(compiler) value = f"0x{self.flash_layout.get_flash_layout(define):X}" update_define_in_file(linker_path, define, value)change tolinker_path = self.config.get_compiler_linker(compiler) value = f"0x{self.flash_layout.get_flash_layout(define):X}" if (compiler == "gcc"): update_variable_

Hello, ST expert For GPIO structure, what are the differences between FT and TT mode? Are there any differences for the ESD diode and the other diode in these two modes?     BR Yang  

Hi All,I've just been watching an ST tutorial video on how to implement  bare-metal Device CDC USB  on an STM32U3.During the video, the lecturer says that the code is available within the workshop download. No link is provided to the workshop code....Does anyone know where I can find it? This is the video in question : https://youtu.be/m8ph9JIY5QE?list=PLTJzs51NlEIAHFfePhKJPsnWvT5XidJuU&t=1164Any help would be appreciated.CheersMichael