STM32 MCUs

After updating and restarting my PC with Windows 10, my old version of CubeProgrammer would not open at all. The version number is unknown. Other STM32 software works without any issue such as CubeMX and CubeIDE.I then tried installing the latest version, 2.21.0. The program launched (even when run as administrator), but it did not function fully. I attached a screenshot for reference. None of the four icons on the top-left responded, and I received error messages when clicking the icons on the right.I also tried installing previous versions from 2.16.0 to 2.20.0, but none of them worked. Specifically:Versions 2.16.0, 2.18.0, and 2.19.0 briefly showed the launch logo, then closed immediately.Versions 2.20.0 and 2.21.0 would open, but the program remained unusable. 

I get no message if i send some bytes about my terminal tool. Because i have no schematic i dont know waht going wrong. Do i need an external supply( target ) or do i need pullup resistor or someone else? A target board isnt still connected.

Hi everyone,I am bringing up a custom board based on the STM32H743VIT6. I am trying to connect via ST-Link (SWD), but I am getting the standard "Can not connect to target" error in STM32CubeProgrammer.The Setup:MCU: STM32H743VIT6Debugger: ST-LinkInterface: SWD (SWDIO, SWCLK, GND, 3.3V detected)Power Supply: External 3.3V. Board voltage source to provide the necessary power for the system, something that ST-Link alone cannot do.The Problem: After failing to connect, I probed the power pins and found abnormal values:VCAP Pin: I measured 2.7 V on the VCAP pin. As I understand it, VCAP corresponds to the internal LDO output for VCORE and should normally be around 1.2 V. Does a reading of 2.7 V indicate an internal short circuit to VDD or a blown LDO?VDD Drop (Pin 75): On Pin 75 (VDD input), I have a known bad solder connection (trace compromised). I measured 2.3V on this pin.Question: Since the other VDD pins are correctly supplied with 3.3V, shouldn't the internal silicon power mesh maint

My STM32H533VE works as PD Sink.We connected CC1/CC2 with DBCC1/DBCC2 (as AN5225), STM32 cannot power up with a USB PD adapter. The adapter supplies power for ~20ms then stops the supplying.If I remove the long time initialization code (LSE initialization), system can boot up and USB PD works fine (PDO can switch).Is this normal? if yes, I may move the LSE initialization later.

Hi everyone,I’m feeling a bit defeated by a task that should be "Hello World" level simple. I’m trying to get a basic printf to show up in PuTTY using a NUCLEO-G474RE, but I’m getting absolutely nothing in the terminal.I do this all the time with my NUCLEO-H723ZG using USART3 and it works like a charm. For the G4, I’ve switched over to USART2, but no luck.Here is my setup:Toolchain: CubeMX + CMake.The Logic: I've overwritten __io_putchar() with a HAL_UART_Transmit call.The Config: USART2 is enabled, baud rate matches PuTTY (115200), and the clocks seem fine.I even had a friend who uses G4 boards regularly take a look, and even he couldn't figure out why the data isn't hitting the ST-Link. It feels like I'm missing one tiny, G4-specific checkbox or jumper setting.I've put together a bare-bones repository with just the code for the printf here: https://github.com/mpek29/nucleoG4Has anyone else run into similar issues ?Thanks in advance for any pointers, I'm sure it's something silly I've

Hello, I am currently evaluating the STM32N6570-DK and am seeking clarification regarding a discrepancy I’ve encountered. I can confirm that there is a 48MHz crystal on board for the HSE. However, the default CubeMX projects generated by the board selector, as well as other example projects I have reviewed, all configure the input frequency to 24MHz. Could you please clarify what the correct input frequency for the HSE should be on this discovery kit? Thank you for your assistance.

Hello,i have project with a'n STM32H743II on a custom board. I use a J-Link Plus to debug and download the program, everthing was working fine. When i updated to version 2.0.0  downloading the program elf file failed. After initialization sequence and downloading the first block the debugger stops, because it can't load the elf file, but the file exists and the path is correct. Message window:Debugger console output: SEGGER J-Link GDB Server V8.80 Command Line Version JLinkARM.dll V8.80 (DLL compiled Oct 22 2025 11:56:02) Command line: -port 2331 -s -device STM32H743II -endian little -speed 4000 -if swd -vd-----GDB Server start settings-----GDBInit file: noneGDB Server Listening port: 2331SWO raw output listening port: 2332Terminal I/O port: 2333Accept remote connection: localhost onlyGenerate logfile: offVerify download: onInit regs on start: offSilent mode: offSingle run mode: onTarget connection timeout: 0 ms------J-Link related settings------J-Link Host int

Hello,I am using NUCLEO-H755ZI-Q (STM32H755) and I am observing a reproducible boot issue related to high system clock frequency.1. Hardware / EnvironmentBoard: NUCLEO-H755ZI-QMCU: STM32H755Power supply: USB (on-board)Debugger: ST-LINK (Connect under Reset)Supply configuration: LDOToolchain: STM32CubeIDE 1.19.02. Issue DescriptionWhen the system clock is configured to 480 MHz, the board fails to boot after power-on or reset.Flash programming and verification succeedImmediately after reset release, the target becomes unresponsiveST-LINK connection is lost When the same firmware is configured to 400 MHz, the board boots and runs normally.Interesting behavior:Power-on the boardFlash firmware configured for 400 MHz → boots normallyWithout removing power, rebuild and flash firmware configured for 480 MHzThe board runs normally at 480 MHzIf power is removed and re-applied, 480 MHz boot fails againThis behavior is fully reproducible.3. ObservationsThe issue only occurs after a cold power

I have a custom board with stm32wba65 processor. I also have an RFM95 LoRa module. I need to add LoRaWAN capability. I tried adding I-CUBE-LRWAN into my CubeMX but was not able to load it (not a recognised package).How can I get an ST or Semtech approved LoRaWAN stack into my project?Please do not suggest I use stm32WL processor.

Hello STM Community,I currently have a NUCLEO-U575ZI-Q board and the X-NUCLEO-IKS4A1 motion MEMS and environmental sensor expansion board. I’m looking to add BLE functionality and was considering the X-NUCLEO-WB05KN1.Before proceeding, I’d like to ask:Are the X-NUCLEO-IKS4A1 and X-NUCLEO-WB05KN1 compatible when stacked together on the NUCLEO-U575ZI-Q?If not, is there an alternative BLE expansion board that is known to work well with the IKS4A1 on this Nucleo board?Alternatively, is there an expansion or adapter board that allows both shields to be connected without pin conflicts?Any guidance or shared experience would be greatly appreciated!Thanks in advance.

Hello all,Trying to set up the custom display on the STM32H750B-DK dev board.Interestingly, the display works via LTDC functions in Keil just fine... but I do not have much luck with the TouchGFX. For example, started with setting up the TBS in the Designer to avoid the complications of memory and other configurations (thanks to the ST support) and continuing in the CubeIDE where I have opened the .*.ioc file to update the MX configuration for the LTDC and TouchGFX... it compiles ok, I can opend the TouchGFX designer and "upload" the picture, for example, I can see the picture to be in the memory. See attached build memory analyzer.However, when I run the application or debug, I cannot see the preview of the picture.One of the ideas, as it is explained in the TouchGFX manual, namely Board bring up, would be to preview a simple framebuffer, not sure how easily that would be?I am not sure how to tackle this problem, so any comments, ideas, or hints are more than welcome! Best. 

Hi, I'm working with a STM32WL5MOC with the STM32Cube FW_WL V1.4.0. In my main.c I have this initialization: MX_GPIO_Init(); MX_DMA_Init(); MX_RTC_Init(); MX_LPUART1_UART_Init(); MX_USART1_UART_Init(); MX_ADC_Init(); MX_CRC_Init(); MX_SPI1_Init(); MX_LoRaWAN_Init(); I put the MX_LoRaWAN_Init after all inizialization. However, I noticed that the code get stacked in MX_RTC_Init();, in particular on here if (HAL_RTCEx_SetSSRU_IT(&hrtc) != HAL_OK).I attach the ioc file and the main. Thanks. 

The Errata sheet for STM32G030x6/x8, ES0486 - Rev 6, states in chapter 2.2.9:After connecting the debug interface and until the device power-down, the boot source upon reset or wakeup from a low-power mode is determined by the PA14-BOOT0 pin level before connecting the debug interface (stored by the device), as opposed to the actual PA14-BOOT0 pin level. The device power-up restores the operation of the PA14-BOOT0 pin as direct boot source selector.But this also applies to the empty check: if the debug interface is connected, the empty check is only updated on device power-up (reset is not sufficient).So, if you program an empty device with the STM32CubeIDE in order to debug the software, you need to stop the first debugging session, perform a power cycle and start the next debugging session. Otherwise, the µC will keep executing the bootloader and debugging will fail with “Break at address 0x1f… with no debug information available, or outside of program code”.

When using the memory management tool (MMT) on the STM32H573 to set the backup RAM as secure it generates an invalid secure attribution unit (SAU) config:#define SAU_INIT_REGION5 1 #define SAU_INIT_START5 0x40000000 /* start address of SAU region 5 */ #define SAU_INIT_END5 0x400373FF /* end address of SAU region 5 */ #define SAU_INIT_NSC5 0The above code is the last region the MMT defines for the SAU.Typically the tool would define the region 0x40000000 to 0x4fffffff (the non-secure peripheral address space) as non-secure. However 0x40036400 is the start of the backup RAM address space which shouldn't be made non-secure.Since this is the last SAU region, there is nothing configuring the region 0x40037400 to 0x4fffffff as non-secure, and so hard faults occur when e.g. trying to access the non-secure RCC address space.I believe correctly generated code should look like the below:#define SAU_INIT_REGION5 1 #define SAU_INIT_START5 0x40000000 /* start address of SAU region 5 */ #d

I have installed the stm32 cube ide , after creating the project i am get .ioc file for the configuration , i have done reinstall process but i am unable to clear the issue , the ide is opened as the image attached . 

Hello. I'm using B-G431B-ESC1 to operate drone motorThe operation was successful using FOC, but from 28,000 RPM and above,it changes to - speed as seen on the Pilot screen. (When the rpm becomes negative, speed control becomes impossible.)In fact, using betaflight, I have seen it go up to 45,000 rpm.Any idea how I can change the minus speed or what I need to change?? 

TL;DR: The receiver ESP32-LoRa node is showing garbage values instead of accelerometer values. The STM32 - LoRa sender node does read correct values from the MPU6050 sensor, as we confirmed that through PuTTY. .ioc configuration Context: So I am trying to program an STM32F411CEU6 module to read accelerometer values from MPU6050 (a 6-axis motion sensor). Then what I am trying to do is send those values to an ESP32 module. I am using Ra-02 SX1278 LoRa boards as the transceiver for the communication. We verified that the values were read properly by printing the MPU6050 sensor readings to the serial port. At the receiver end, we used Sandeep Mistry's LoRa.h library for programming the ESP32 in Arduino IDE. Clock Configuration for ref.Issue: The receiver end was receiving garbage values when we tried to monitor the sent values. Even the code in void setup() was taking a while to execute. I believe the issue is with configuring the LoRa parameters between the sender and recei

Can anyone help me understand how these two arrays have been made#define M1_ANGC                            {-116,-363,-611,-843,-1091,-1338,-1571,-1833}#define OFST {0,17,51,99,167,252,348,474}these arrays are used in MTPA calculation with y=mx+c equation.These are the motor parameters for which the array has been calculated. Your assistance will be appreciated.

CubeMX version 6.16.1 I found STM32WBA55CG project with ThreadX,  the  parameter of "TX_LOW_POWER_USER_ENTER" and "TX_LOW_POWER_USER_EXIT" will be reset to default after the ioc re-open.This bug can be 100% reproduce. 

Hello community members, I am using a STM32H5 with acitvated MPU region. I want to check and test dection of nullpointer access.Because of safety reasons. I have configured and activated the mpu so far. When doing a write access to the declared null pointer, the MemManageFault Handler is called as expected. uint32_t *m_pTest = nullptr;*m_pTest = m_value; // -> MemManageHandler is called (as expected)when doing a read access, the BusFaulthandler is calledm_value = *m_pTest; // ->BusFaultHandler is called (not my expectation)//here my mpu configuration and settingsSCB->SHCSR |= SCB_SHCSR_MEMFAULTENA_Msk |SCB_SHCSR_BUSFAULTENA_Msk |SCB_SHCSR_USGFAULTENA_Msk;/* Configure the MPU to prevent NULL-pointer dereferencing ... *///check nullpointer access Region1MPU_InitStruct.Enable = MPU_REGION_ENABLE;MPU_InitStruct.Number = MPU_REGION_NUMBER1;MPU_InitStruct.BaseAddress = 0x00U;MPU_InitStruct.LimitAddress = 0x200U;//512Byte for exampleMPU_InitStruct.AttributesIndex = MPU_ATTR

Hello,I am below Hardware and Software setup:Hardware:MCU Board: NUCLEO F401REPower Board: X-NUCLEO IHM08M1BLDC Motor: Portescap 22ECP45-8B-154.01 (specifications_22ecp45.pdf attached)Software:MC Workbenach v6.4.1I am using sensorless FOC (STO-PLL) in WorkBench tool. I am trying to increase the speed of the motor to its MAX 47000 RPM. But, I am getting only 7200 RPM with Parameters from Motor Datasheet in MC Workbench tool. I have changed the HW to short 3-SHUNT and removed mentioned capacitors.Below are my parameter configurations: Max speed I am getting on Motor Pilot:I queried Motor for the Max speed of the motor. They replied it is achievable by using 14 mNm Torque.    I have few questions:1. In the Motor profiler tool, reaches upto 12000 RPM then giving Speed Feedback error. What configurations can set to run profiler tool successfully?2. Does ST HW (F401RE + IHM08M1) support 47K RPM @24V for the Motor?3. With ST workbench tool having Sensor

I designed a board that uses a STM32H750 with a USB3300-EZK that has stopped communicating over USB. It's been having intermittent issues for the last day or so (sometimes I'd need to power cycle the board before it would show up, but then it would work flawlessly). Earlier today, I plugged it into a Raspberry Pi, and then it died fully. I've plugged it into that Pi before without issue.Despite probably hundreds of cycles at this point, I haven't gotten the USB to work again. The PHY is generating a stable 60MHz clock, and DIR is low. I haven't observed any communication on the D0..8 lines. That leads me to believe the problem is with the STM32.I am using pc2_c and pc3_c, which are supposed to work with USB, although I've heard they're more susceptible to (static?) damage.I do have a second board that I can switch to, although I don't have a third prototype, and it really would be good to figure out what happened here so I can prevent it from happening again.

I found in my tests that for the same sequence of operations (Radio.SetChannel -> Radio.RadioSetTxGenericConfig -> Radio.Send), the time required differs significantly between waking up from STOP2 sleep mode and waking up from Sleep mode. Here is Radio workflow：Startup -> Sleep -> Calibration -> Standby Here is the test code, with two additional modifications.void app_fsk_send(void) { if (!s_radio_init_flag) { Radio.Init(&s_radio_events); s_radio_init_flag = true; } TxConfigGeneric_t tx_config; uint8_t syncword[] = {0xC1, 0x94, 0xC1, 0x00, 0x00, 0x00, 0x00, 0x00}; if (!s_radio_init_flag) { Radio.Init(&s_radio_events); s_radio_init_flag = true; } priv_prbs9_generator(s_payload, 16); tx_config.fsk.ModulationShaping = RADIO_FSK_MOD_SHAPING_G_BT_1; tx_config.fsk.FrequencyDeviation = 40000; tx_config.fsk.BitRate = 100000; /* BitRate */ tx_config.fsk.PreambleLen = 4; /* in Byte */ tx_config.fsk.SyncWordLength = 3; /* in Byt

CubeIDE: v2.0.0CubeMX: v6.16.1Debugger: ST-LINK/V2 V2J46S7Hello,I'm attempting to setup a dual core project using STM32H757XIH MCU on CubeMX. I've generated and imported the project for CubeIDE. I've configured the Trace and Debug -> DEBUG for "Serial Wire" with M7 and M4 selected with Cortex-M7 as the initializer. I've configured one pin (PJ10) to be an output for a user LED.I've attempted to follow AN5361 "Getting started with projects based on dual-core STM32H7 microcontrollers in STM32CubeIDE" when configuring the debug profiles for the M7 project and M4 project while leaving the rest set to default.I've attached the logs to this post. Am I missing something when configuring the processor? Let me know if I need to add anymore information on my configuration.

Hello,I have a question about vscode with STM32 extension. I have setup a project with vscode and stm32 extension, and after compiler, it can do debug, and I can see the Global Variables on the VARIABLES window. as belowbut when I use vscode to do another design not with stm32 extension. I do the debug, but I cannot see the Global Variables on the VARIABLES window. as below, only Locals and Registers.Why no Global Variables? what is the difference among the 2 vscode?Thanks.