Skip to main content
Semer CHERNI
ST Employee
March 3, 2025
Question

STM32CubeIDE 1.18.0 released

  • March 3, 2025
  • 2 replies
  • 4401 views

We are pleased to announce that the release 1.18.0 of STM32CubeIDE is available.

What is new in 1.18.0:

  • Microcontrollers, microprocessors, and board lists aligned with STM32CubeMX 6.14.0:
    • Added the support for STM32WBA6xxx microcontrollers in the STM32WBA series
  •  Eclipse® updated to 2024-09  and CDT updated to 11.6.1: Gives the possibility to install the Copilot4Eclipse (Copilot for Eclipse) plugin
  • Updated to GCC 13 as default toolchain
  • Multiple old toolchain version will no longer be supported:​
    • GNU ARM GCC7, GNU ARM GCC9 and GNU ARM GCC10 without ST layer​
    • GNUTOOLS FOR STM32 GCC7 with ST layer
  • Added the support for Fedora® 41 

Main fixed issues in 1.18.0:

Refer to the STM32 microcontroller wiki at:
STM32CubeIDE:STM32CubeIDE errata 1.18.x - stm32mcu

Known problems and limitations in 1.18.0:

Refer to the STM32 microcontroller wiki at:
STM32CubeIDE:STM32CubeIDE errata 1.18.x - stm32mcu

How to get STM32CubeIDE 1.18.0:

  • Under this link
  • Or update your current installation of STM32CubeIDE using: Help > Check for updates (The in-tool update does not allow updating the drivers and STLINK server tool. Full installation is required for this to be done).

2 replies

Visitor II
March 3, 2025

Hi, I'm using STM32H743 for development and after recent IDE update I have found an issue in new GNU Tools v13.3.

 

I have a few variables for DMA and one of them is placed in RAM D3 section, to be accessible by BDMA. With new GNU Tools that variable is placed together with others in RAM D1, so BDMA doesn't have access to it.The only change to GNU Tools v12.3 resolves the issue (without any changes in code)

ivanobono
Associate II
April 2, 2025

I am currently using this version of CubeIDE. [Version: 1.18.0 Build: 24413_20250227_1633 (UTC)] with a STM32G473QET6 CPU

I noticed that in the debugger SFRs window there is an error in the name of the TIM17 registers (they were called TIM16_xxx)

t.png