STM32 MCUs Software development tools

Hello ST,FYI - It appears CubeMX was not updated since DP-FPU capability was added to the STM32N6 data sheets.Regards,Dave

I have set XSPI1 to "Hexa SPI" mode. I'm using EXTMEM_MANAGER to manage the memory. I'm unable to select the setting EXTMEM_LINK_CONFIG_16LINE for "Number of memory data lines". Instead there is a info textbox which says "Active only when XSPI enabled in Hexa SPI mode.". The only available option is EXTMEM_LINK_CONFIG_1LINE. This results the EXTMEM_DRIVER_PSRAM_Init function to fail in the Config switch case, as the only options in the switch case are EXTMEM_LINK_CONFIG_16LINE and EXTMEM_LINK_CONFIG_8LINE.If i manually force the Config to be EXTMEM_LINK_CONFIG_16LINE before the switch case, it seems to work.I believe that i should be able to select EXTMEM_LINK_CONFIG_16LINE with MX if my XSPI is configured to Hexa SPI mode. 

CubeMX 6.16.1MacOS 15.7.3STM32F469NIHXMultimedia - DSIHOST - Data and Clock Lanes     -  click,click,clickShow Advanced Parameters - checkHS Transmission fine tuning and LP Transmission fine tuningTransmission Delay on Clock Lane and Transmission Delay on Data LanesThese items refer to 2-bit wide fields in DSI_WPCR1 but CubeMX allows values from 0-10, which would be 3.32-bits wide. By setting the clock transmission delay to, say, 10, the data clock delay gets overwritten as well. Data delay overwrites the low power clock delay, and so on.The actual data range for these items should be [0,3], and HAL_DSI_SetSlewRateAndDelayTuning should probably sanitize the parameter Value before using it.

Hello, We appear to be experiencing a severe code generation bug with CubeMX. After naming and sizing application regions in the memory management tool, what used to generate a correct linker script now generates bad output.Upon generation the linker script STM32U575XX_FLASH.ld now shows:/* Specify the memory areas */ MEMORY { RAM (rwx) : ORIGIN = 0x20000000, LENGTH = 768K FLASH (rx) : ORIGIN = 0x08000000, LENGTH = 2048K /*start of MX regions Auto-generated By STM32CubeMX*/ RAMBK (rw) : ORIGIN = 0x20000000, LENGTH = 768K RAM4 (rwx) : ORIGIN = 0x20000000, LENGTH = 768K SPIFLASH (rwx) : ORIGIN = 0x08000000, LENGTH = 2048K /*end of MX regions*/ }Given that we cannot downgrade the IOC and have performed more work this is an awkward situation and we will manually manage regions in the meantime. This was not an issue before. Please advise what may be going on. 

I am using cubemx to generate a CMAKE project for a NUCLEO_144 based board (NUCLEO_H563).Project generation creates a cmake/stm32cubemx/CmakeLists.txt file that generates a macro define "USE_NUCLEO_144".it also auto creates a stm32h5xx_nucleo_conf.h file that also creates the same define: /** @defgroup STM32H5XX_NUCLEO_CONFIG_Exported_Constants Exported Constants  * @{  *//* Nucleo pin and part number defines */#define USE_NUCLEO_144/* #define USE_NUCLEO_64 */ This creates a duplicate redefinition warning upon build in many places as this header is included throughout my project in many places.This is extremely annoying.I can suppress the warning by adding:

Dear STMicroelectronics,This is a bug report on the UI for STM32CubeMX 6.16.0 running on Windows 11 Pro 25H2.Please report this internally so that it may be fixed in some future version. Steps to reproduceStart STM32CubeMXFile / New ProjectSelect MCU STM32H563RIT6Click button Start ProjectSelect with TrustZone activated and click OKUnder Categories, expand Middleware and Software PacksFor ThreadX, click the greyed out radio button in column M33NSClick it againExpectedThe popup is readable.ActualAfter the second click, the popup is shown partially obscured by the table and is not readable.If you select the row for ThreadX and click the radio button you can get the popup very much obsc

Split from this thread. Yes, but No!CubeMX V6.16 now allows only exactly 32 TX Buffers ((TX Buffer Nbr + TX Fifo Queue Elmts Nbr) == 32).But less then 32 TX Buffer is allows by the Hardware, and some times, required if You want to maximize the RX Buffers.

There's a bug in latest STM32CubeMX v6.16.1. When enabling RAMCFG for Appli on STM32N6 MCU, the IOC file becomes unloadable.I attached the demonstration IOC file. I created new project for STM32N6570-DK board, enabled RAMCFG peripheral for Appli, checked the AXISRAM3-6 areas, defined single continuous area for those SRAMs in MMT and saved the project. After this CubeMX fails to load this IOC file. I get popup:In textual form the error is: Cannot invoke "com.st.microxplorer.mcu.memorymap.MemoryMapService.getInRangeAppRegions(long, long, com.st.microexplorer.mcu.Context)" because "this.mMemor

Hi everyone,I am attempting to set up the new CubeMX version (6.16.0) inside a Docker container, but I am running into issues.Setup:Base Image: Ubuntu 24.04Target Software: STM32CubeMX 6.16.0Goal: Headless installation (auto-install), since CubeMX is no longer bundled with CubeIDE 2.0.0.The Issue: The headless installation fails. According to the User Manual "UM1718", this mode should still be supported. However, the installation process differs from the manual and aborts with an error. Note: The current manual still uses version 6.11.0 in its examples.What I have tried so far:Verified with v6.11.0: I tested the headless installation with the older version 6.11.0. This works perfectly and follows the manual exactly.Quiet Mode: I

I recently tried to use -noreconnect via the cli on windows and it still attempted to reconnect.I was connected via UART and programming option bytes. Here was the command I used:& "C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" -c port=COM14 br=115200 -noreconnect -ob ndbank=0x0I see that there was fix put in for linux. Im wondering if the same bug exists on Windows.Thanks,Daniel 

Hello,Our project is based on the STM32WBA65MI, and we have an external flash chip on the board that we use STM32CubeProgrammer w/a custom external loader to program. This worked well with STM32CubeProgrammer v2.20, but when I updated to STM32CubeProgrammer v2.21, suddenly I was unable to connect to the board using the external loader.This happens as soon as I select the external loader andIf I select verbosity level 3, this is what I see:08:50:10:520 : Selected loader: C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/External

I want to set the BOR_LEV of H523 to 1. If you have any good ideas, please let me know.

Hi everybody, I'm using a custom PCB which is build upon a STM32L431CBT6 MCU. When connecting to the CUBE Programmer i had this error:Error: Database: There's no active configuration for this device. All the 1 configurations are disabled!Then, i confirmed the issue arose from the DeviceID 0x435 .xml file not having the 128K flash memory settings. What i did is code it myself like this:<!-- JTAG_SWD Interface --> <Interface name="JTAG_SWD"> <Configuration number="0x0"> <!-- 256KB--> <FlashSize> <ReadRegister address="0x1FFF75E0" mask="0x0000FFFF" value="0x0100"/> </FlashSize> </Configuration> <Configuration number="0x1"> <!-- 128KB--> <FlashSize> <ReadRegister address="0x1FFF75E0" mask="0x0000FFFF" value="0x0080"/> <

Hi, I am trying to debug my STM32N6570-DK board, i followed the steps listed under 4.1.3 (Debugging the application) in the getting started instruction list (https://www.st.com.cn/resource/en/application_note/an6265-getting-started-with-stm32n6-mcus-in-stm32cubeide-stmicroelectronics.pdf). When i try to debug the application, it starts normally (code uploads to the external memory), but when i click resume to start the program, the debugger loses connection and eventually exits debug mode. The program I am trying to debug was made using TouchGFX, it's configured as an FreeRTOS project. This is the output the debugger gives to me:Starting server with the following options:Persistent Mode : DisabledLogging Level : 1Listen Port Number : 61234Status Refr

Even I am using the latest CubeProgrammer v2.21.0, it indicates an update available but when I check it, there is no update and the updater log does not update, it cannot update its last update date as well.I know not so important but quite annoying problem, i`d like to mention, 

STM32CubeIDE for VS Code is there a memory window? like MDK Memory window   

Started project (using STM32CubeMX) with STM32C011J4M6 (SO8 package, 16K flash).Using STM32CubeIDEVersion: 1.19.0Build: 25607_20250703_0907 (UTC)Application now requires >16K (flash (code+flash data space) so replaced MCU part with STM32C011J6M6 (SO8 package, 32K flash).After adding content to project source code (a font file, taking the expected total flash space over 16384 bytes) build does not complete.I believe the root cause is that I've not told STM32CubeIDE of change to the larger-flash version of the chip (same family, just larger flash).What file(s) need to be edited to enable the larger flash size (or do I need to revert to STM32CubeMX and then splice the now under-development project source code into the new project? C:/ST/STM32CubeIDE_1.19.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.13.3.rel1.win32_1.0.0.202411081344/tools/bin

Have been fighting ST-LINK_gdbserver over the last few days and am hoping that someone can shed some light.  I'm using JetBrains CLion with the ST-LINK gdb server. I have this configured in the "Debug Servers" setting. I want to get my ITM / printf calls to appear in my "MCU Console" window in CLion. So I have my SWO Enabled, I specify my clock (400Mhz / STM32H743), my divider (1000, should give 400kbaud data coming out), and my TCP port for the SWO data to appear on (59999). I've overridden my `_write` function to push to the ITM_SendChar function.  I press debug, JetBrains compiles, runs the ST-LINK_gdbserver, passes in the correct flags, "-z 59999 -a 400000000 -b 1000 ", and the GDB then connects to the GDB port (61234 - default).  However I don't see any SWO output via ST-LINK_gdbserver. If I run the STM32_Programmer_CLI in a separate terminal window with "./STM32_

I have the Nucleo-144 board N657X0Q.It appears to work (i believe there is demo code pre-installed - it is flashing a red led and the frequency changes when I press the user button).  However, I cannot get the Cube IDE or Cube Programmer to work with it.  I am just trying to read memory using the cube programmer as a test.  It connects, gets the information about the board, uploads the loader firmware, and then when it tries to read it gets an error and disconnects.The log file is attached.  I have tried using two different machines as hosts, and tried 2 different usb cables (both are suggestions from several posts I found).  I have tried reducing the speed, and using the "under reset" and "hotplug" modes to no avail.  I have selected the correct external loader before doing the check.  I am using a separate power supply on the user USB to rule out any problems with enough power from the host machines on the USB port.

Hi everyone,I am experiencing an issue with STM32CubeMX version 6.16.0 while working on an STM32U375xx based project.When I set the Toolchain/IDE to CMake, the code generation process completes successfully, but the linker script (STM32U375xx_FLASH.ld) is missing from the project structure. I have checked both the root directory and the cmake/ folder, but the file is nowhere to be found.Interestingly, if I switch the Toolchain to STM32CubeIDE, the .ld file is generated as expected. This suggests a potential issue or a change in behavior specifically for the CMake generator with the new U3 series in this version of CubeMX.Environment details:MCU: STM32U375xxSTM32CubeMX Version: 6.16.0Toolchain:&nbs

This fault is still happening since Oct 2024. However I found a workaround documented here -->https://stackoverflow.com/questions/78850472/stm32cubeprogrammer-flash-loader-cannot-be-loadedIn case the link has died, you need to do the following...Connect STM32CubeProgrammer to your STM32 device and note the "Device ID" listed in the "Target Information" window bottom right of the CubeProgrammer app, e.g. for an STM32F103 this will be 0x410.cd into your "STM32CubeProgrammer/bin/FlashLoader" folder.duplicate the file that matches your device ID (e.g. for an STM32F103 the file would be 0x410.stldr)and then rename the duplicated file "0x".Then restart STM32CubeProgrammer and it will now work properly. 

Hello,I have the issue that the FlashLoader is detected but not set correctly. The error message is:flash loader cannot be loaded. FlashLoaderPath = CubeProgrammer/bin/FlashLoader/0xAs a workaround I can create a copy of the correct FlashLoader and name it 0x, but I think this should work automatically. I am running on Linux and the issue exists for several versions of CubeProgrammer and on multiple Linux distros for me. My current version 2.21.0.The issue is really annoying if you switch boards and forget to copy-rename the correct FlashLoader.    

I am using STM32Cube IDE version 1.4.1 where I'm debugging 1st the CM4 Core which is getting debugged and then I tried to debug CM0+ core which is not going into debug mode and showing the error :Target unknown error 32Error in initializing ST-LINK device.Reason: Unknown. Please check power and cabling to target.I tried this tooLaunching the configurationsLaunch the Cortex®‑M4 configuration to download both the Cortex®‑M0+ and Cortex®‑M4 images.Resume the Cortex®‑M4 core until the C2BOOT bit is set in power control register 4 (PWR_CR4) to enablethe Cortex®‑M0+.Launch the Cortex®‑M0+ configuration using the arrow next to the debug icon. The Cortex®‑M0+ is in therunning mode and the user can halt it after the debugger is started.The core CM4 got into debugged mode but then the Core CM0+ is showing :Debugger Connected

Hi I am just getting started with STM32CubeIDE for a project I am doing at my university!I have made an account and installed the software, and I got the board (NUCLEO-L552ZE-Q), I wanted to start a new project with the board to try and blink and LED.But somehow I cant find it anywhere where to create a new project that is not an empty project because I want my board automatically connected to my project, because I have read some online where they said a question "Initialize all peripherals with their default Mode?" will appear once you created a new project and want to connect the board.The alternatives I get when pressing Create/Import STM32 Project is:1. STM32CubeIDE Empty Project2. C++ Project3. C project4. STM32 CMake ProjectPlease let me know if I have done something wrong with the installation or if there is something I missed.Thanks in advance!

I have a NUCLEO-F030R8 development kit and an X-NUCLEO-WB05N-B01 (STM32WB05N) expansion board.I am using an ST-Link V3 for programming and debugging.I believe that I have connected the boards according to the official X-CUBE-WB05N Getting Started documentation (v1.1.0). The wiring, pin mappings, and configuration settings have been done based on the document.I am trying to communicate between the NUCLEO-F030R8 (host MCU) and the STM32WB05N over SPI.The SPI pins, IRQ, and reset connections are configured according to the documentation. However, in this setup, the STM32WB05N does not appear to reset properly, and SPI communication cannot be started.On the STM32CubeMX side:The X-CUBE-WB05N v1.1.0 expansion package is selectedSPI configuration and pin assignments are set as