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"

[DmitriiChar]

Strange situation that I created the new one. Worked with it and in the one time didn't open any menu as GPIO or System - no one.

Then I closed, open again - tried to open

loading and then nothing

[LLeva.1]

I hope you are not using Windows7? I was forced to migrate all the stuff in production computer due to CubeMX visual bugs.... (visual studio, quartus, cadsoft eagle and other stuff.. uhhh).

Can not confirm your bug. Created new pins, saved, loaded and it is working. Sometimes some window "sliders" joins without leaving properties windows, but just drag the bar and everything appears. Maybe you pressed tiny black triangles? It can screw user interface a bit.

[DmitriiChar]

Thank you. No, have Win10. I'll try again... will see...

[DmitriiChar]

I tied to import my project to new project and see the exception with text: " The current Mcu STM32F103VETx is using block remap as a consequence Pinning status will be ignored" hmmm... What it is? Do you know? Mb it's the problem?

[DmitriiChar]

I found the problem in my case. I didn't install JDK/JRE.. without it works strange and CubeMX don't work at all... Sorry...

[DmitriiChar]

I thought that I found the problem in my case, but I was in a rush... I installed JDK/JRE.. something changed but it's at the feelings level.

I starting new project than set some settings like system, timers, connectivity etc. Then I starting to set pins and... look at the picture. The cursor push TIM1 and nothing changes in the right window. In this point CubeMX do not work at all.

I tried this operation several times and result the same - CubeMX breaks own work day. And my heart too... I reinstalled the CubeMX too - nothing.

Mb problems in some driver or something else. It could be because my PC is a new one. Mb some settings... Mb... Mb... But how it works with another users and don't works with me I don't know.

I tried the old version - the same thing... What it can be?