Important Notice for STM32CubeMX Users
Current Release: STM32CubeMX 6.12.1
Purpose: This release primarily addresses issues related to STM32MPUs.
Problem: Issues introduced with the generated code for Makefile and CMake projects.
Recommendation:
- For MCU Users: If you are using an MCU (not an MPU), it is recommended to stay on STM32CubeMX 6.12.0.
- For MPU Users generating code for MCUs: follow the instructions below.
Issue Description:
- Problem: When compiling a CMake or Makefile project, a build error occurs due to a syntax error related to the linker file.

- Cause: The .data, .bss, and ._user_heap_stack sections are not attributed to the RAM memory region. Additionally, the RAM attribute is missing from the highest address in the user stack calculation formula.


Solution:
- Attribute Memory Sections: Ensure that the .data, .bss, and ._user_heap_stack sections are attributed to the appropriate RAM memory region
.
- Update Stack Calculation: Add the RAM attribute to the highest address in the user stack calculation formula.

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.