STM32 MCUs Software development tools

I'm trying to flash an an NUCLEO-N657X0-Q board with the STM32N6 using STM32CubeProgrammer v2.20.0. I have two NUCLEO-N657X0-Q boards here: One of them flashes just fine, the other one refuses to work. Both boards are in development mode (BOOT jumpers set accordingly as described here https://github.com/STMicroelectronics/STM32N6-GettingStarted-ImageClassification?tab=readme-ov-file#boot-modes). In STM32CubeProgrammer, I have selected the appropriate External loader to be able to write to the external flash memory.As a simple experiment, I am trying to erase a sector of the external flash memory. I am using the exact same STM32CubeProgrammer settings for both boards. Erasing the flash works just fine on one of the boards, but on the other board, I get the following error:Did I accidentally enable some kind of flash memory protection? How do I disable it? Or is my board broken? The board still boots the old code in the flash memory when in flash boot mode, so I don't thin

Browsing the STM32CubeMx Docs&Resources page for information.The section "Application Notes for related Tools and Software" includes couple of links to documents targeting a specific MCU different from the currently viewed one.I.e. browsing for STM32H5, or STM32G4 there are also shown "Getting started with STM32N6 MCUs in STM32CubeIDE". And it's the same with WL, L5, MP1, ... CubeIDE ANs.  

Currently, STM32Cube for Visual Studio Code introduces a new bundled package manager which replaces STM32CubeCLT.However, when developing STM32 projects with other IDEs (e.g. CLion), STM32CubeCLT is still required to provide the build environment.This leads to several problems when using multiple IDEs (VS Code + CLion):Separate installations of toolchains (STM32Cube for VS Code and STM32CubeCLT) consume extra disk space.STM32CubeCLT cannot be updated incrementally; users must download the whole package.STM32Cube for VS Code currently cannot manage STM32CubeCLT packages, leading to duplicated toolchain management.By default, tools are installed on C:\ drive, which is inconvenient for users with limited system disk space.Feature request:Allow STM32Cube for VS Code’s package manager to use and manage STM32CubeCLT packages.Benefits:Reduce disk usage by avoiding duplicated toolchains.Simplify updates and package management.Improve developer experience when using multiple IDEs (VS Code + CLi

We are pleased to announce that STM32CubeIDE 2.0.0 release is available. STM32CubeIDE is now independent from STM32CubeMX. With this release, device configuration, previously handled within STM32CubeIDE via STM32CubeMX, is now exclusively available through the stand-alone STM32CubeMX tool. Users will configure microcontroller peripherals and generate initialization code separately in STM32CubeMX, then import the generated projects into STM32CubeIDE for coding and debugging.   STM32CubeIDE, is now a stand-alone tool, offers the possibility to create empty project through its own MCU/Board selectors now present inside. What does this change mean for developers?  Separate download and installation: STM32CubeMX is no more integrated in STM32CubeIDE, requiring separate download alongside STM32CubeIDE 2.0.0 for configuration and code generation.  Tool update flexibility: Developers can update and freeze&n

Split from this thread. Hi mƎALLEm, Thanks for this reply and confirming that the OSC_OUT can be used as GPIO when HSE in bypass mode. Can  you please advise I do I set this as a GPIO? CubeMX does not allow me to configure this pin. Should this be hand coded to make this possible? Thanks. Regards Billy

It would be great if the STM32CubeProgrammer would do proper error handling for J-Link debug probes instead of crashing.Issue:Every times I try to the connect to a STM32 target that is not powered, or not properly connected the GUI pops up three error messages that need to be close separately and on the next connect it pops up another error message and gets stuck. So that the program needs to be completely restarted. Preferred behavior:STM32Cubeprogrammer show only a single pop up or only log a warning message and recovers from this situation in a way that that allows it to connect to a STM32 target again. This is no regression and has been observed since j-link probes are supported.The last time it has been observed is on a Windows 11 PC with intel CPU, targeting a STM32G4 MCU with STM32Cubeprogrammer v2.21.0, J-Link HW version V11.00(latest FW Apr 1 2025) 

Dear all!i'm try to set up STM32H562RIT6 project, i use STM32cubeMX6.4, but it seem didn't support, i try to instal H5 package but still can't find MCU. some one know how to fix it, pls help me

As shown in the figure, the title of the window bar seems to have become garbled, even though its content was originally in English. I thought it was due to the software defaulting to a font that only supports Western characters, but changing all the available fonts did not solve the garbled text issue. Please help me; this is very important to me. Thank you so much!If there are similar problem cases, please send me the solutions along with them

Hi All,I have been working with the STM32H7R7 MCU for a while.  I used the getting started manual of the application notes for Eclipse, but I could not set up the right debug environment for the STM32H7R7 deviceI used the cubemx to generate the boot, appli and ext memory. I used exactly the same ioc file (except the setting of the cmake vs cubeide), however I could not flash and debug the device without the right json file.I tried to build by myself, but I was not lucky enough to be succesfull. Also I have not found any examples on the web.Could somebody help me with a json file, environment for debug and flashing? Thank you very much in advance

Dear members of the community, how many of us developers are comfortable with this ***: 

If on a STM32H747 the Cortex-M4 (BCM4 or BOOT_M4 Bit) is disabled by software, it is impossible to reactivate it with the STM32CubeProg v2.18.0 because the checkbox disappears in the user interface. But this happens only if you do a power cycle and reconnect to the target.

Hi,I've recently been trying to get an LRUN application up and running on the NUCLEO-N657X0-Q board. Similar to the posts in https://community.st.com/t5/stm32cubeprogrammer-mcus/stm32n6570-dk-unable-to-erase-external-flash/td-p/757897, I cannot access the flash for erasure, with errors indicating to verify flash memory protection. I currently have the BOOT0 jumper on 1-2 (for 0) and BOOT1 on 2-3 (for a logical 1), which should be putting me into the Development boot mode. For external loaders, I have MX25UM51245G_STM32N6570-NUCLEO selected. I've tried both full chip erase and sector erase, both giving me errors that tell me to verify flash memory protection.Please advise, I'm not sure what I'm doing wrong. This is my first time attempting to flash the memory.EDIT: I should've mentioned, I'm using STM32CubeProgrammer 2.20.0. I've tried this on both Windows 11 and Ubuntu 24.04EDIT #2: I have also attached the verbose log file after I hit "full chip erase" and a single

The first case concerns the DAC, by setting "Output Buffer" = Disable in CubeMX, it is enabled in code generation instead, i had to add "DAC1->MCR = 0x03" in the initializations. /** * @brief DAC1 Initialization Function * @PAram None * @retval None */ static void MX_DAC1_Init(void) { /* USER CODE BEGIN DAC1_Init 0 */ /* USER CODE END DAC1_Init 0 */ LL_DAC_InitTypeDef DAC_InitStruct = {0}; /* Peripheral clock enable */ LL_APB1_GRP1_EnableClock(LL_APB1_GRP1_PERIPH_DAC1); /* USER CODE BEGIN DAC1_Init 1 */ /* USER CODE END DAC1_Init 1 */ /** DAC channel OUT1 config */ DAC_InitStruct.TriggerSource = LL_DAC_TRIG_SOFTWARE; DAC_InitStruct.WaveAutoGeneration = LL_DAC_WAVE_AUTO_GENERATION_NONE; DAC_InitStruct.OutputConnection = LL_DAC_OUTPUT_CONNECT_INTERNAL; DAC_InitStruct.OutputMode = LL_DAC_OUTPUT_MODE_NORMAL; LL_DAC_Init(DAC1, LL_DAC_CHANNEL_1, &DAC_InitStruct); LL_DAC_DisableTrigger(DAC1, LL_DAC_CHANNEL_1); /* USER CODE BEGIN DAC1_Init 2 */ /*

Hi, I started a new project with STM32U031C6. When I enabled Independent watchdog (IWDG), STM32CubeIDE generated the following line in the MX_IWDG_Init function:     __HAL_RCC_IWDG_CLK_ENABLE();When compiling the project, an error is generated:     undefined reference to '__HAL_RCC_IWDG_CLK_ENABLE'I could not find such a function either in the drivers included by STM32CubeIDE in the project or in the repository in the STM32CubeIDE installation directory.This function should enable the APB peripheral clock to the Independent Watchdog (IWDG), but I couldn't find anything for this purpose anywhere in the Reset and Clock Control (RCC) registers.Does this mean that the APB peripheral clock is always active for the Independent Watchdog (IWDG) and should not be enabled? In other words, is this function unnecessary and can I comment it out?I would be grateful for any help

We are pleased to announce that STM32CubeProgrammer 2.21 is available What is new in 2.21: • Support for the STM32WL3Rxx microcontrollers:         – Internal memory programming        – Option byte and OTP programming         – PKCS#11        – Firmware authentication • STM32MP21x microprocessors: SSP support on Linux®• STM32WBA6xxG microcontrollers: Support for 1-Mbyte flash memory size • Support for new devices in the STM32C0 series: STM32C011xx, STM32C031xx, STM32C051xx, STM32C071xx, STM32C091xx, and STM32C092xx microcontrollers• Support for the factory reset of option bytes:         – STM32WBA5xxx and STM32WBA6xxx microcontrollers         – STM32U375/385 microcontrollers • Dynamic upgrade of components • Support for SWD multi-drop • Fast read new CLI command Main fixed issues in 2.21: Refer to the STM32CubeProgrammer wiki at: STM32CubeProgrammer err

Hi,I'm trying to test and deploy this application on stm32N6-DKhttps://github.com/STMicroelectronics/STM32N6-GettingStarted-ObjectDetectionAlso follow this MOOChttps://www.youtube.com/watch?v=VV9f5e3nqM4&list=PLTJzs51NlEICI7ARAHOyUqMhTgJE0UFv0&index=8Loaded the project to stm32CubeIDE 1.19.0Can buid the project but impossible to configure or debug the application !!or this error on debug viewIf someone can help ...  

I saw some older threads regarding this issue, but no way to fix this?

Hi,I would like to get printf() debug messages from both M7 and M4 core using SWO pin. It seems to work as expected on M7 core, but I cannot get it work on M4. Ideally, I would like to have messages from both cores in parallel, but it would be great to get both cores working separately. I have been using UART so far, but SWO sounds much better. Is it possible to get SWO printf() debug messages directly from M4 core?Is it possible to use SWO on both cores in parallel?

Hello everyone,I'd like to report some issues I encountered while using NetXDuo to create a UDP server with a Nucleo-N657X0-Q board:There's no option to select a network interface other than the custom one — I had to manually add all the libraries related to the Ethernet interface and the LAN8742 driver.The folder ../../Drivers/CMSIS/Device/ST/STM32N6xx/Include/Templates needs to be added manually.Enabling NX_ENABLE_VLAN has no effect in the nx_user.h file.The linker script STM32N657X0HXQ_AXISRAM2_fsbl.ld is missing the tcp_sec and nx_data sections.After addressing all the issues above, I was finally able to get the UDP server working correctly! 

Using an STM32H7Rx or Sx, with both I2C2 and I2C3 in use, and clocked by PLL3R:Cube correctly configures I2C2. However, it doesn't seem to be aware that I2C2 and I2C3 share a clock, so it:incorrectly computes the timing for I2C3, as if it were using PCLK1 (the default), in MX_I2C3_Init();fails to insert the line "PeriphClkInit.I2c23ClockSelection = RCC_I2C23CLKSOURCE_PLL3R;" in the init code for I2C3, in HAL_I2C_MspInit(). This sets both I2C channels back to PCLK1, thereby breaking I2C2 as well.(I didn't try the other clock sources - HSI and CSI - but it's possible that they too don't work for I2C3.)Fortunately, it is possible to manually add the correct code in the user areas immediately after the two sections of affected code, so there is a workaround for now. 

 I'm experiencing an issue when attempting to debug a project in STM32CubeIDE v1.19.0 using a NUCLEO-H753ZI board and ST-LINK V3 (FW: V3J16M9). The debugger appears to hang during the early initialization phase and fails to proceed with device enumeration commands.BehaviorWhen I launch a debug session, the IDE displays:Launching: Performing pre-launch check... It remains stuck at this message indefinitely. The only way to cancel is to terminate the stlinkserver.exe process manually using Task Manager. Once the server is killed, the IDE regains control and exits the debug attempt.To investigate further, I manually started stlinkserver.exe using: stlinkserver.exe -a -p 7184 -d 5The server successfully detects the ST-LINK device: STLK: Add to stlink USB list: VID 0x0483, PID 0x3754, serial [REDACTED_SN] ... TCPCMD REFRESH_DEVICE_LIST : return 1However, no subsequent commands are issued — GET_NB_DEV, GET_DEV_INFO, and OPEN_DEV are all missing. The server enters an idle

I don't use the code-generation features of the STM32CubeMX, but rather use it just for pin-planning purposes when designing hardware. I've noticed that when enabling the Ethernet MAC, that the SMI / MIIM peripheral is automatically enabled and allocated pins. There are many cases where this is inappropriate (e.g., some other device is managing the interface, no management is possible, or another bus type is used) and it would be lovely for STM32CubeMX to treat these two things as the fully-unrelated peripherals that they really are.The workaround is to manually assign each Ethernet pin individually, but this is brutally unpleasant. Could ST please divorce these two peripherals within the STM32CubeMX software?

I noticed that the V 2.20 STM32CubeProgrammer erase function doesn't work under Pop_OS!, a Linux distribution.  It does however work on Windows 10.  I don't think this is a logic failure within the STM32CubeProgrammer but some weird interaction with the USB Driver.  Just to be clear I am using STLink on a STM32N6 evaluation board.  Interesting that this function does work on a STM32h747i_disco board.  Another difference is I am using an USB A to USB C cable, but all the other functions work, after erase on the Windows machine.  I have the erase under Windows workaround but it is a little inconvenient. 

I encountered a significant problem with the live expressions during debugging, as the variables displayed erratic values and symbols when they were set as unsigned. I spent several days trying to verify this, as I previously had doubts about my code's execution.At times, the values may be exchanged or moved unexpectedly (the output of the first variable appears in the second variable's output, and consequently, all other values are displaced).Please prioritize this matter. In our organization, many individuals are encountering this problem and are considering transitioning to VS Code.

After setting the heap size to 16 GB in the stm32cubeide.ini before finally not getting "out if memory" errors, opening the "Pinout Compatible" Dialog from an existing project consumes a little over 10 GB !I found another thread where this was apparently fixed in CubeMX in 2022 (CubeIDE 1.9.0 has a heart attack on "loading compa... - STMicroelectronics Community), it seems to be back.