STM32CubeMX 6.12.1 released (updated)

[Semer CHERNI]

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:

• ADC init code error.
  • When ADC is configured in multimode, an issue with the initialization code structure occurred in the LL Mode due to choosing a value for the "Delay between 2 sampling phases" parameter not matching the constants defined in the LL library file "stm32h7xx_ll_adc.h".
• The IOC file provided with the STM32MP257F-EV1 board on STM32CubeMX 6.12.0 does not allow the generation of the correct device tree.
  • The STM32CubeMX V6.12.1 solves the issue by modifying the device tree files related to the STM32MP257F-EV1 board.
• FLEXGEN data must be generated for each assigned IP on Cortex®-M33 context.
  • When configuring a peripheral in the Cortex®-M33 context, the FLEXCLKGEN settings for the RCC node in the device tree (DT) are not generated.
  • The STM32CubeMX V6.12.1 fixes this issue by configuring the FLEXCLKGEN for the specified IPs in the Cortex®-M33 context.
• The pin A19 isn't assignable for both DDR3 and DDR4.
  • The STM32CubeMX V6.12.1 is allowing pin A19 to be assignable for both DDR3 and DDR4
• Code Generation error in MX_FLASH_Init() function when setting BOR level
  • When activating the FLASH and setting a BOR(Brown-Out Reset)level, the code generation produces an error. Specifically, an if statement appears inside the MX_FLASH_Init() function without any condition after the line HAL_FLASHEx_OBGetConfig(&pOBInit);This if statement extends to the end of the function, causing incorrect behavior.
• Wrong stack size value for STM32G473RET3Z series.
  • STM32CubeMX 6.12.1 fixes the stack size by setting it to 0x600.
• The STM32H725VGH3 microcontroller did not appear in the list of available MCUs.
  • In the STM32CubeMX V6.12.1, the STM32H725VGH3 MCU is added.
• An exception occurred after setting a valid "memclk" value in the DDR_CTRL_PHY register.
  • The values for the parameter "memclk" are outside the permissible range. The STM32CubeMX V6.12.1 is fixing the issue by setting the right range for "memclk" parameter.

Check the errata under this link for more details.

Note : The installers for the three supported OSs are available on st.com.

Where do I obtain STM32CubeMX 6.12.1 ?

• STM32CubeMX 6.12.1: STM32CubeMX - STM32Cube initialization code generator - STMicroelectronics
• Or in the Home view click on "Check for Updates"

[Andrew Neil]

@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 ?

[Andrei Chichak]

On https://www.st.com/en/development-tools/stm32cubemx.html#tools-software, the .1 version is not available for Mac, just windows and linux

[LLeva.1]

Do not use this version if you are using "make". Developers introduced new bug:

https://community.st.com/t5/stm32cubemx-mcus/flash-ld-syntax-error-when-upgrding-to-cubemx-v6-12-1/td-p/722343

[Semer CHERNI]

Hello

I want to share the info that the installer for macOS is now available on st.com.

KR,
Semer.

[smercurio]

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?

[asmandar]

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.

[unsigned_char_array]

Several bugs and issues:

1. During installation the installer doesn't open an app in the task bar and the window is not in focus so it is behind all active windows (in Windows 11). So if you double click the extracted installer nothing seems to happen. This is a bug.
2. Indentation bug in generated main.c still present: https://community.st.com/t5/stm32cubemx-mcus/stm32cubemx-inconsistent-indentation-for-mx-touchgfx-process/td-p/691271
3. Installer filename structure changed, this is annoying when archiving installers as they are no longer lexicographically sorted. en.stm32cubemx-win-vx-y-z.zip -> en.SetupSTM32CubeMX-x.y.z-Win.zip . Why the change?
4. Default install location is not in program files but in appdata and this cannot be changed unless installer is run as admin.