Skip to main content
Semer CHERNI
ST Employee
July 1, 2024
Question

STM32CubeIDE 1.16.0 released

  • July 1, 2024
  • 9 replies
  • 5991 views

STM32CubeIDE 1.16.0 was released today on st.com as well as an in-tool update patch.

  • What is new in 1.16.0?
    • Microcontroller and board lists aligned with STM32CubeMX v6.12.0 : STM32C0, STM32WB0 and STM32MP25XX
    • Added CMake support for multicontext projects (Multi-Context ,Trust zone , Multi-core)
    • Added new features for CMake project configuration
    • Basic CMake support now also with Ninja
    • Added the OZ in the optimization level to the build settings
  • Main fixed issues:
    • Refer to the STM32 microcontrollers wiki under this link.
  • Known issues fixed and problems and limitations:
    • Refer to the STM32 microcontrollers wiki under this link.
  • Where do I obtain STM32CubeIDE 1.16.0?

9 replies

Andrew Neil
Super User
July 1, 2024

Has this done anything to address the many & vociferous objections to the login requirement?

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
padawan
Senior
July 2, 2024

And again,

jumping around after debugging.

https://community.st.com/t5/stm32cubeide-mcus/jumping-to-random-file-after-pressing-run-button/m-p/691078

Once again, opening a ticket and promising to resolve it "as soon as possible" is not a solution!

What a poor performance after several years.

Padawan

 

Visitor II
July 15, 2024

Did the debugger no longer start at the mainand the debugger cursor stops at another file?? Is this the problem you are worried about?

I guess I will downgrate to the 1.15.0 version.

padawan
Senior
July 15, 2024

Hi carleslsThat will not help.

The error has existed for years.

They "solved" it by opening a ticket 

padawan

Gaston
Associate III
July 3, 2024
Visitor II
July 15, 2024

Is it normal for the debugger cursor start in another code different to the beginning of the main?

Thank you.

TKusc.1
Associate
July 19, 2024

Hello,

usually I download the Linux package STM32CubeIDE, but with 1.16.0, the link is broken. I can only download the former 1.15.1. The 1.16.0 or the latest package from STM32CubeIDE-Lnx at https://www.st.com/stm32cubeide is broken. I have tried latest Firefox and Chromium browser. All other packages for Debian etc. seem to work.
Please update the Linux package. BR Thomas.

PHolt.1
Senior
July 26, 2024

I posted another thread here somewhere on this. 1.16.0 breaks a STLINK V2 or V3 debugger connection. So I went back to 1.14.1.

Andrew Neil
Super User
July 29, 2024

@PHolt.1 wrote:

I posted another thread here somewhere on this. 1.16.0 breaks a STLINK V2 or V3 debugger connection. 


This: https://community.st.com/t5/stm32cubeide-mcus/cube-ide-1-16-0-and-stlink-v3-cannot-find-debugger/td-p/702136 ?

 

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
Associate
August 30, 2024

STM32CubeIde 1.16 (Version: 1.16.0 Build: 21983_20240628_1741 (UTC)) works only partially on Ubuntu 24.04 LTS.

Build works but debug can't work because it requires too old libs :

Could not determine GDB version using command: arm-none-eabi-gdb --version
arm-none-eabi-gdb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory

Cheating creating symbolic link to newer lib version is not working (it could have worked as a dirty patch if there is enough compatibility between both libs version)

ln -s libtinfo.so.6.4 libtinfo.so.5
ln -s libncurses.so.6.4 libncurses.so.5

It reveals which versions are required by STM32CubeIde / arm-none-eabi-gdb build, which seems way too limited :

Could not determine GDB version using command: arm-none-eabi-gdb --version

arm-none-eabi-gdb: /lib/x86_64-linux-gnu/libncurses.so.5: version `NCURSES_5.3.20021019' not found (required by arm-none-eabi-gdb)

arm-none-eabi-gdb: /lib/x86_64-linux-gnu/libncurses.so.5: version `NCURSES_5.1.20000708' not found (required by arm-none-eabi-gdb)

arm-none-eabi-gdb: /lib/x86_64-linux-gnu/libncurses.so.5: version `NCURSES_5.6.20061217' not found (required by arm-none-eabi-gdb)

arm-none-eabi-gdb: /lib/x86_64-linux-gnu/libncurses.so.5: version `NCURSES_5.0.19991023' not found (required by arm-none-eabi-gdb)

arm-none-eabi-gdb: /lib/x86_64-linux-gnu/libtinfo.so.5: version `NCURSES_TINFO_5.0.19991023' not found (required by arm-none-eabi-gdb)

Maybe it's possible to rebuilt the compiler to get a working GDB...

I need to find a fix for this in order to be able to test a newly design board correctly.

Visitor II
September 4, 2024

After upgrading to 1.16.0 the code generated from my .ioc file does not compile.  This used to work before the upgrade.  The two problems are:

  1. the reference to pOBInit (line 11) which is not declared anywhere
  2. the bogus if () statement (line 12)

The device is a STM32U595xJT6Q

 

 

static void MX_FLASH_Init(void)
{

 /* USER CODE BEGIN FLASH_Init 0 */

 /* USER CODE END FLASH_Init 0 */

 /* USER CODE BEGIN FLASH_Init 1 */

 /* USER CODE END FLASH_Init 1 */
 HAL_FLASHEx_OBGetConfig(&pOBInit);
 if ()
 {
 if (HAL_FLASH_Unlock() != HAL_OK)
 {
 Error_Handler();
 }
 if (HAL_FLASH_Lock() != HAL_OK)
 {
 Error_Handler();
 }
 }
 /* USER CODE BEGIN FLASH_Init 2 */

 /* USER CODE END FLASH_Init 2 */

}

 

 

m4l490n
Associate III
September 18, 2024

I can't install it in Ubuntu 24.04. I'm getting the following:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 st-stm32cubeide-1.16.0 : Depends: libncurses5 but it is not installable
 Depends: libpython2.7 but it is not installable
 Depends: libwebkit2gtk-4.0-37 but it is not installable
E: Unable to correct problems, you have held broken packages.