STM32 MCUs Software development tools

Hello,recently I started a project based on a STM32L433RCT3 and the STM32CubeIDE build tooling defaults to C++14. I myself am cautious about bleeding-edge standards but C++14 seems a bit conservative in 2026. I tried both the GCC 13.3 and GCC 14.3 toolchains and C++14 was the default in both, while C++17 is the default of GCC since GCC 11 (C++ Standards Support in GCC).With another project and toolchain I once got nasty to track down bugs when bumping the C++ standard beyond the manufacturer's default so I'm wary to do this. What are the community's experiences using C++ standards beyond C++14?What is the general policy of ST regarding bumps of the default C++ standard version?Best,MarkusPS: I tried the CMake-based toolchain too, which in my case did not set a C++ standard explicitly, so going with my local compiler's (GCC15 C++17) default. As much as I prefer CMake - and appretiate the ongoing move to it - in general I would prefer to stay with the tried-and-tested STM32CubeIDE.

On Version 1.11.0I'm aware that the chart can be resized with the 'Size' parameter.However, attempting to expand it beyond size 15 horizontally just shuts the window down:(Furthest I can go horizontally)While it is possible to expand it out vertically to an arbitrary size.Jut wondering if this is a bug or horizontal size 15 is the max limit for the chart.on 4k Monitor the chart size of 15x9 is way too small.

CubeMX 6.16.0's "Memory Management" Tool assumes Rx_PoolSection size to coincide with the Eth "Rx Buffers Length" - is that correct? I used CubeMX 6.16.0 to create a project for an STM32 H755ZI-Q.Then I opted to use the Tools -> "Memory Management" tool and afterwards enabled the ETH [ethernet] component. This automatically generated the required sections in the "Memory Management" tool. Great.Then I enabled LwIP [with RTOS and CMSIS v2] and generated code.Compiling this code worked - linking however did not. It told me the contents of Rx_PoolSection were too big, i.e. the section too small: EBoxNG3_CM7.elf section `.Rx_PoolSection' will not fit in region `Rx_PoolSection'region `Rx_PoolSection' overflowed by 225668  The buffer for the RX_POOL is declared in CM7\LWIP\Target\ethernetif.c:98:#define ETH_RX_BUFFER_CNT 12U LWIP_MEMPOOL_DECLARE(RX_POOL, ETH_RX_BUFFER_CNT, sizeof(RxBuff_t), "Zero-copy RX PBUF pool");with__attribute__((section(".Rx_PoolSection"))) extern

The STM32L0xx series contains EEPROM located at 0x08080000. This is extremely handy for storing factory calibration data, serial numbers, license keys, etc.The STM32CubeProgrammer GUI can read this memory in the Memory & File editing view Device memory tab by entering the Address and amount of data to be read. You can enter and read any address and range within EEPROM.However the Memory & File editing view cannot be used to download data from a binary file into an arbitrary location in EEPROM such as 0x08080100. If you open a binary file in a new tab and try to set the address to 0x08080100, it will display an Address out of range error dialog.This is not critical since you can still download to an arbitrary address in EEPROM using the Erasing & Programming tool within the GUI (or use the CLI tool), but it seems to clearly be a bug and there's no need for everyone to have to figure out the problem and the workaround...so I'm documenting it here.Also annoying (albeit arguabl

Hello,I was using STM32CubeMX, but starting two days ago, when I launch the program, only the splash screen appears and the STM32CubeMX does not proceed any further.1. I have tried deleting the program, restarting the computer, reinstalling it, and running it again.2. Adding a new user is not possible; the user creation permission is restricted to the company's IT administrator.I would appreciate any suggestions on additional steps I could take to resolve this issue.

I recently upgraded my IDE to version 2.0.  I cannot start a project from the board view; where you select the board type and configure the settings.  It would then create the c++ project code for you.  The new version doesn't have anything to help you select the board and it cannot even open up the board configuration editor when you click on the .ioc file.  Is there. a way to revert back to the previous editor version - I think it was version 1.x.18?

I am unable to change the project name in STM32CubeIde, if i change it and try to open it i get error windows cannot find the file. They are all linked files, may be that is causing the issue, what changes i have to do avoid this error. The project is generated using MCSDK and after generation i am trying to change the project name in CubeIde. 

Hii Community member,I need technical help from someone who had faced this issue earlier described as below:I am currently working on STM32H723ZG mcu in which i had interfaced NAND flash of MX30LF4G28AC using FMC peripheral.As per our hardware test routine, I am checking flash test in which first a block gets erased and then each page is verify whether it is erased or not. Then a dummy buffer of 4096 get writes in a page and then read back into another buffer and comparing them. During comparison, my test passes for some pages and fails for some pages within block. When checked for failed pages, it is found that only last byte i.e. 4095th byte is differing. Although i had done configuration for 4Gbit model in cubeMx, my test routine is working for 2Gbit model.I would welcome any suggestion or some guidance point to resolve my issue.If any code snippet required, i will share on this chat.@TDK 

I have a Discovery board B-L072Z-LRWAN1 and I am trying to set up a project using CubeIDE but get the following, So I check to see if the L0 & LRWAN packages are in the repository, Yes, they're there. I click OK & Cube carries on setting itself up & up pops the ioc window. I press configure & generate & get some C code but the build option is greyed out.   What am I missing here?      

Hello! I am using an STM32U545 and VS Code for programming. I am experiencing the following issue: I am working with STOP mode, and once the MCU enters this state, I can no longer reprogram it. When using STM32CubeIDE, I did not encounter this problem (I believe this is related to the connect-under-reset feature, which VS Code seems to lack when programming).Is there anything I can do to avoid this issue, other than using STM32CubeProgrammer to erase the memory or adding a delay at the start of the program to give myself time to program the device after a manual reset?

We have a board with a stm32u5. were VDDIO are connected to 1.8 V and  the I2C bus have pullup to 3.0 V. Some I2C devices uses 3.0 V logic levels and som 1.8 V. Between which voltage levels shall i measure the rise and falltime that i enter in cubemx. 30%->70% of 1.8 V or 3.0 V .We have possibility to turn off and on some devices on the bus that changes the rise and falltime on the bus. Shall then the longer or shorter rise/falltimes be used?One reason we are asking is that our design engineers wonder why the signal of the clock never is piece wise equal in on and off timing as it is the case with other I2C masters 

I have been working with a custom board using the STM32U073 for while, and have made a program that can active the USB system memory DFU. After this I suddenly cannot program the board anymore using the STM32CubeProgrammer.I can read all the flash memory, but cannot program the flash anymore.... Debugger connected Waiting for debugger connection... vchg_ctrl_run (duration_ms=16174368) at xxx/vchg_ctrl.c:108 108 setVchg(vchg_state); // Set the charger state based on the conditions connected to remote target localhost:61234 Note: automatically using hardware breakpoints for read-only addresses. load "xxx/build/Debug/hp2_charger_stm32_new.elf" Loading section .isr_vector, size 0xc0 lma 0x8000000 Loading section .text, size 0x10318 lma 0x80000c0 Loading section .rodata, size 0x754 lma 0x80103d8 Loading section .ARM, size 0x8 lma 0x8010b2c Loading section .init_array, size 0x4 lma 0x8010b34 Loading section .fini_array, size 0x4 lma 0x8010b38 Loading section .data, size 0x138 lma 0x8010b3c

I updated CubeIDE to 2.0.0 (now CubeMX is separated) on MacOS. I started new project and want to set semihosting for debug. I did the configuration as I used to do in previous projects, but now when I try to run, I receive following error:Info : [STM32WB5MMGHx.cpu] Cortex-M4 r0p1 processor detectedInfo : [STM32WB5MMGHx.cpu] target has 6 breakpoints, 4 watchpointsInfo : [STM32WB5MMGHx.cpu] Examination succeedInfo : starting gdb server for STM32WB5MMGHx.cpu on 3333Info : Listening on port 3333 for gdb connectionssemihosting is enabledsemihosting fileio is enabledError: The 'gdb_report_data_abort' command must be used before 'init'.Below my configuration of OpenOCD: Where should I put the gdb_report_data_abort command?   

Hello,I am experiencing a flash upload issue with STM32CubeIDE(v1.19.0).The MCU I am using is STM32C091GCU6 with 256 KB of internal Flash.I am currently developing code to display image (IMG) data on an LCD.The image data is stored in Flash, copied to SRAM using memcpy(), and then transmitted to the LCD via SPI DMA.From the MAP file, I can confirm both the Flash addresses of the image data and the SRAM copy destination.The relevant MAP file entries are shown below: .rodata.IMG_HORIZONTAL0x08004840 0xfd20 ./Core/Src/font.o0x08004840 IMG_HORIZONTAL.rodata.IMG_VERTICAL0x08014560 0xfd20 ./Core/Src/font.o0x08014560 IMG_VERTICALAfter this configuration, when I build and debug using STM32CubeIDE, the reported uploaded memory size is only 128 KB.Because my code accesses image data located above the 128 KB Flash boundary, a HardFault occurs when running under CubeIDE debug.However, when I take the same build output file and program it using STM32CubeProgrammer(v2.19.0), the firmware is cor

Hi there,I'm using an N6 with the latest version of IDE and MX with the FSBL/Appli dual project structure as per the FSBL LRUN template, and MX is incorrectly managing code. When using X-CUBE-FREERTOS in Application mode, code generation and cleanup is buggy. I've attached a FreeMarker template error generated WITHIN app_freertos.cWhen removing FreeRTOS from the project, MX fails to remove void MX_FREERTOS_Init(void); and MX_FREERTOS_Init(); from main.c. It also doesn't remove the head app_freertos.h and FreeRTOSConfig.h header files, but does remove the source file. I get the following compiler error:make[1]: *** No rule to make target '/Users/h7/STM32CubeIDE/workspace_1.16.1/N6Project/Appli/Src/app_freertos.c', needed by 'Application/User/app_freertos.o'. Stop.I'm also finding that the files that I have added to the build exclusion list in libraries that I've included in Middlewares/Third_Party are being reset. After a code generation, those files that MX should not be touc

Hello,I have observed this issue in version 6.16.1 across several MCU series (F3, F4, H5, H7), though it appears likely that all earlier versions are affected.The generated .cmake toolchain files incorrectly treat the --specs=nano.specs option as linker-only. This option should be applied globally, as it also affects the system include paths used during compilation. Specifically, it causes the compiler to include arm-none-eabi/include/newlib-nano/newlib.h instead of the standard arm-none-eabi/include/newlib.h.While this mismatch probably does not break ABI compatibility—since the structures provided from the standard headers are larger than those used in the compiled newlib-nano library—it does negate the RAM usage benefits of newlib-nano. This is particularly problematic when using the USE_NEWLIB_REENTRANT FreeRTOS option.Regards,Peter 

Hi, using STM32 Cube Programmer and STM32 Trusted Package Creator W2.21, I was unable to detect the HSM card, getting error 0x88000002. I had to downgrade to V2.14, as mentionned in several posts to get it detected successfully.I use HID Omnikey 3121 reader.Any solution to be able to use last version 2.21 and HSM card ?

The release notes for v2.2.0 say that feature is in there, but I can't seem to find it.I tried the "Full Chip Erase" feature & it cleared everything EXCEPT the EEPROM.

The STM32CubeProgrammer does not appear to be able to read system memory from an STM32L051 when using the UART interface however it is able to do so when using the SWD interface.  When using the UART interface, both flash and EEPROM can be read, but not system memory.  This is on a factory fresh part with no readout protection set (0xAA).c:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin>STM32_Programmer_CLI.exe --connect port=COM5 -r8 0x1FF80050 8 ------------------------------------------------------------------- STM32CubeProgrammer v2.21.0 ------------------------------------------------------------------- Serial Port COM5 is successfully opened. Port configuration: parity = even, baudrate = 115200, data-bit = 8, stop-bit = 1.0, flow-control = off Activating device: OK Board : -- Chip ID: 0x417 BootLoader protocol version: 3.1 Device name : STM32L05x/L06x/L010 Flash size : 64 KBytes (default) Device type : MCU Revision ID : -- Device CPU : Cortex-

I'm using STM32_Programmer_CLI software v.2.20.0 to program an ST Nucleo board (NUCLEO-C071RB).I wish the software were better at automatically handling situations that make it fail.For example, this command does work normally for uploading firmware to the board:STM32_Programmer_CLI --connect port=swd --download firmware.elf --startHowever, if you have enabled read-out protection (RDP) by setting RDP=0 in the option bytes, then it fails with "Error: failed to erase memory"  (and for some reason, it prints that message twice).  If read-out protection truly does prevent you from erasing, the software should be smart enough to detect that RDP is on and then turn it off temporarily.  Instead, we have to manually ask the software to do that:STM32_Programmer_CLI --connect port=swd -ob RDP=0xAA --download firmware.elf --startNext, if you have enabled write protection for a relevant portion of flash, the software fails with the same "Error: failed to erase memory" error messages

I downloaded and installed stm cube programmer, but every time I try to open it, I immediately get an error message saying that it quit unexpectedly. Currently running mac high sierra 10.13.6. How can I fix this problem?

Hello,I inherited an old software project from a colleague who retired. (He originally worked on Windows XP.)The software was designed to run on an STM32L-Discovery board.Since some packages need to be maintained, I want to build the software on a Linux machine (Ubuntu 24.04.4 LTS). I managed to create a CMake project that successfully builds the binary for the target.The issue I’m facing now is that I can’t flash the binary to the target hardware because STM32CubeProgrammer displays the following message:“Error: Old ST-LINK firmware version. Upgrade ST-LINK firmware.”I also tried on a Windows 10 machine and got the same result.On the official board page [1], there’s no mention of STM32CubeProgrammer.I’ve been searching for a solution since this morning, but I haven’t found the right hint yet.Can anyone confirm whether CubeProgrammer is unable to write to this Discovery board?Can anyone recommend a programmer I can use to flash the binary? (I know a few are listed in the documentation,

HelloI am connecting the ST-LINK and downloading the firmware to the programmer.I have a question. Can I do power from ST-LINK and download firmware instead of supplying external power to the MCU? Currently, I use external power, but I wonder if there is such a way.Thank you.

 I'm currently working on a project using an STM32G473RCT6. I've integrated the STL Lib (Self-Test Library) and intended to use STM32_Programmer_cli.exe with the -sl option to add the CRC block.The application starts at 0x08040000 and continues for a maximum of 128K, up to 0x08060000.There will therefore be an area of 0x20000/1024=128 CRCs, which will occupy 128×4=512 bytes.In practice, the application itself can only occupy 0x1FE00 bytes because the last block will be available for the CRC Area.Based on the STL documentation, these CRCs will be inserted at address 0x08060000−512=0x0805FE00.The command I'm using is:STM32_Programmer_cli.exe -sl "firmware.bin" 0x08040000 0x08060000 0x400The resulting binary has the entire section between the end of the original binary and 0x0805FE00 padded with 0xFF.Upon checking the CRCs that were inserted starting from 0x0805FE00, I can see that the first ones correctly match the CRC of the application blocks. However, when it reaches the CRCs cor

Friends, I've encountered a bug while running CubeIDE 2.0 on my Ubuntu (KDE desktop). When I open my project, I notice the code editing area flickers. This often happens when the sidebar scrollbar is activated (forgive me, I'm not sure how to describe this element). Has anyone else experienced a similar issue? How should I resolve it?