2024-09-18 03:40 AM - edited 2024-09-24 01:24 AM
Hello community,
We are pleased to announce you that the minor release STM32CubeMX V6.12.1 is now available for download on st.com.
Main issues fixed in this minor release:
Check the errata under this link for more details.
Note : ONLY installer for OS (Windows, Linux ) is available for this version of STM32CubeMX 6.12.1. For macOS, please use the self-upgrade mechanism as described in the release note.
Where do I obtain STM32CubeMX 6.12.1 ?
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2024-09-18 03:46 AM - edited 2024-09-18 03:49 AM
@Semer CHERNI don't forget to 'Pin' the post!
(and un-pin the one about 6.12.0?)
@Semer CHERNI wrote:Where do I obtain STM32CubeMX 6.11.1 ?
Did you mean 6.12.1 ?
2024-09-19 11:45 AM
On https://www.st.com/en/development-tools/stm32cubemx.html#tools-software, the .1 version is not available for Mac, just windows and linux
2024-09-28 01:29 PM
Do not use this version if you are using "make". Developers introduced new bug:
2024-10-03 09:01 AM
Hello
I want to share the info that the installer for macOS is now available on st.com.
KR,
Semer.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2024-10-04 09:38 AM
I don't know if this happened with v6.12 or 6.12.1, but there has been an annoying, no reason for this to change done to the UI. For the Parameter Settings tab the "Show/Hide description area" is enabled by default. If you turn it off and then go to another peripheral, and then back to the one you were originally looking at, it's back on!
Why was this done, and why is there no way to turn off this obnoxious behavior, and who thought this was a good idea?
2024-10-05 10:32 AM
Issue Summary with STM32CubeMX 6.12.1 `.ld` File:
I'm using STM32CubeMX 6.12.1 on Windows 11, with Visual Studio Code (VSCode) and STM32CubeCLT, instead of STM32CubeIDE. The linker script (`.ld`) generated by this version has several critical issues:
1. Syntax Errors in Memory Definition:
- The generated `.ld` file has incorrect syntax in the memory areas, specifically when handling the RAM and FLASH regions, causing the linker to fail.
2. Incorrect Heap and Stack Definitions:
- The file contains problematic heap and stack size definitions, which lead to issues in memory allocation during runtime.
3. Undefined References:
- Several key system symbols like `SystemCoreClock` and `SystemInit` are missing or not correctly referenced, leading to unresolved symbol errors during the build.
4. Toolchain Compatibility:
- The issues arise when using STM32CubeMX 6.12.1 in combination with external toolchains like STM32CubeCLT (instead of CubeIDE), where the generated file leads to build failures due to incomplete or incorrect linker script configurations.
Here is a sample of the error output from VSCode:
```
C:/ST/STM32CubeCLT_1.16.0/GNU-tools-for-STM32/bin/ld.exe:
CMakeFiles/firmware.dir/startup_stm32f103xb.s.obj: in function `Reset_Handler':
C:/~/Desktop/firmware/startup_stm32f103xb.s:64: undefined reference to `SystemInit'
C:/ST/STM32CubeCLT_1.16.0/GNU-tools-for-STM32/bin/ld.exe:
CMakeFiles/firmware.dir/Core/Src/main.cpp.obj: in function `SystemClock_Config()':
C:/~/Desktop/firmware/Core/Src/main.cpp:143: undefined reference to `HAL_RCC_OscConfig'
```
This issue seems related to the linker script generated by CubeMX in version 6.12.1, as older versions do not produce these problems.
2024-10-08 04:31 AM
Several bugs and issues: