Skip to main content
Nawres GHARBI
ST Technical Moderator
April 25, 2019
Question

STM32CubeMX 5.2.0 released

  • April 25, 2019
  • 22 replies
  • 6205 views

Dear community

We are pleased to announce the release of STM32CubeMX v5.2.0

What is new in STM32CubeMX V5.2.0?

• Added the support of new dual-core part numbers in the STM32H7 Series:

– Added the support of dual-core configuration, code, and project generation: context assignment (CM4, CM7, both CM4 and CM7 with initializer), Boot0 mode support (both CPUs booting at once), resource manager, and power domains (D1, D2 and D3).

– Added the support of new part numbers: STM32H74x and STM32H75x.

– Added the support of the PCC feature, examples, and Tj versus Ta calculation for the dual-core devices in the STM32H7 Series.

– Added the support of new boards: STM32H747I-DISCO, STM32H747I-DISC1, STM32H745I-DISCO, NUCLEO-H745ZI-Q, NUCLEO-H755ZI-Q, NUCLEOH743ZI2, NUCLEO-H753ZI, STM32H743I-EVAL2, STM32H753I-EVAL2, STM32H747I-EVAL, and STM32H757I-EVAL.

• Added the support of new single-core part numbers in the STM32H7 Series: STM32H742x.

• Added the support of a new board for the STM32H7 Value Line: STM32H750B-DK.

• Added the support of new devices with 64 Kbytes of Flash memory in the STM32G0 Series with examples in STM32CubeMX format available in the STM32Cube_FW_G0_1.2.0 STM32CubeG0 MCU Package.

– Added the support of new part numbers: STM32G030x, STM32G031x and STM32G041x.

– Added the support of the extended-mode feature for SO8, TSSOP20 and WLCSP18 packages. This feature allows multiple configurations of parallel IOs.

• Added the support of the STM32G4 Series with first examples in STM32CubeMX format available in the STM32Cube_FW_G4_1.4.0 STM32CubeG4 MCU Package.

– Added the support of devices in the STM32G4 Series: STM32G431x, STM32G441x, STM32G471x, STM32G473x, STM32G474x, STM32G484x, and STM32GBK1CBT.

– Added the support of boards based on devices in the STM32G4 Series: STM32G474E-EVAL, STM32G484E-EVAL, STM32G474E-EVAL1, NUCLEOG474RE, NUCLEO-G431RB and NUCLEO-G431KB.

• New toolchain support: STM32CubeIDE.

• Added the support of PCC examples for the STM32MP1 Series.

• Integration of the Cross Selector tool with both STMicroelectronics and competitors data.

Known limitations

Please refer to the RN

Fixed issues

57095 Calling HAL_PWR_EnableBkUpAccess() is only done for the STM32F1 Series.

57986 Bug in STM32CubeMX / STM32F0 LL Library internal ADC channel.

58265 [MX-Code Generation]: Release build not defining compiler.

62052 [MX-GUI] STM32CubeMX reset after dragging the chip in pinout view with Chinese translator activated.

62446 [MX-F7][SAI] Internal synchronization does not work.

63612 [MX-Graphics]: GFXSimulator warning is displayed

63747 [MX-TIM] TIM14 for STM32G0 does not support the input clearing source.

63762 [MX-CAN] CAN1 clock enable to be generated if only CAN2 is enabled.

63768 [MX-SPI] Cannot configure CRC poly.

Firmware package versions

STM32F0 V1.10.0

STM32F1 V1.7.0

STM32F2 V1.7.0

STM32F3 V1.10.0

STM32F4 V1.24.1

STM32F7 V1.15.0

STM32G0 V1.2.0

STM32G4 V1.0.0

STM32H7 V1.4.0

STM32L0 V1.11.2

STM32L1 V1.9.0

STM32L4 V1.14.0

STM32MP1 V1.0.1

STM32WB V1.1.0

Get the new version now

https://www.st.com/en/development-tools/stm32cubemx.html?sc=stm32cubemx

This topic has been closed for replies.

22 replies

Charlie CHEN
Associate III
April 26, 2019

Hi @Nawres GHARBI​ ,

Thanks for your introduction,there`re helpful and useful.

May I ask a question about STM32Cubmx?

I`m using STM32H743 MCU,and I have a problem why it didn`t release the Graphic function.

Cause I`m trying to build it to TouchGFX.

0690X000008Aw4YQAS.png

Thank you!

Nawres GHARBI
ST Technical Moderator
April 29, 2019

Hi @Charlie CHEN​ 

The support of STM32H7 TouchGFX has been delayed to a later release.

I will share an expected delivery date later.

Regards,

Nawres.

MaxMax
Associate II
June 10, 2019

Hi @Nawres GHARBI​,

did you already get information on the expected delivery date?

Is it just the integration in CubeMX, or are the TouchGFX libraries for H7 devices missing in general? I can't seem to find information about this. I want to migrate from a STM32F767 to STM32H743, but I'm not sure whether this can readily be done right now, or if there is still something missing on the STM-side that I'd need to wait for.

Best regards,

Max

LAfon
Associate II
April 26, 2019

This version seems to still not allow code generation for H7 LL (released with new v1.4.0).

Martin Meijerman
Associate II
April 29, 2019

Hi @hans12345691.5549423946210898E12 (Community Member)​,

This release of STM32CubeMX also seems to allow the CPU clocks of the STM32H753ZIT to be set to 480MHz, this used to be 400MHz.

The odd thing is that STM32CubeMX does not allow the PLL to be configured to this frequency.

The minimum value of DIVP1 is 2, meaning that for 480MHz SYSCLK the output of DIVN1 needs to be 960MHz, STM32CubeMX gives an error when trying to do this:0690X000008B2UhQAK.jpg

Is there a solution for this?

Thanks in advance!

Best regards,

Martin Meijerman

Software Engineer

caleb
Associate III
May 15, 2019

Did you ever find a solution for running at 480MHz? We should need to go to 'Power Regulator Voltage Scale 0' (VOS0, DS12110 Rev 7, Page 240, Note 2) , and only on device revision V, and you must make sure the LDO regulator is on (DS12110 Rev 7, Page 215, Note 4). Table 147 says that the max VCO output frequency is 960 MHz, which would allow a 480MHz clock, but the STM32CubeMX 5.2.0 only alows up to 836MHz, even when I set the VOS to VOS0. So, maybe set the VOS0, and manually set (in code) the PLL to 480MHz? But only if you have a rev V silicon....

Martin Meijerman
Associate II
May 16, 2019

Hi Caleb,

I did not get an answer yet...

Guess that, indeed, we will have to hardcode the multiplier of the PLL to reach higher clock speeds.

I failed to notice that only revision V supports that speed, that introduces some nice dependencies :-/... Supply chain etc.

Best regards,

Martin

Bertrand1
Senior
April 29, 2019

After the update and during the fisrt CubeMX startup after, I have an error " unable to write on the installation folder..." or something like that. I tried to re-install 3 times always in admin privilege. The only working ways has been to back to 5.1.

Bertrand

GS1
Senior III
May 3, 2019

I have found 3 problems in the new release (and switched back to 5.0.1. (because I don't have the time to get more issues based on CubeMX!):

  • After converting my STM32H7 project from 5.0.1 to 5.2.0 all pins of the SWD / JTAG Debug-Port have been set to Reset State!
  • USB Virtual COM port on the PC will get a new Port number due to a changed setting of the USB serial number
  • Communication via USB VCP does not work any more. I have set USE_HAL_PCD_REGISTER_CALLBACKS to 1. Could this be the reason that USB is not working anymore?

Martin Meijerman
Associate II
May 6, 2019

This version of STM32CubeMX hangs when trying to open a ioc file made with an old version of STM32CubeMX and choosing to continue rather than migrate.

See attached ioc file.

PGogt
Associate II
May 7, 2019

I too have the same problem. The 5.2 version of CubeMX hangs while trying to open files created in ver 5.0 and then upgraded to ver 5.1.

SBybe
Associate II
May 7, 2019

Hello! CubeMX 5.2.0 Timer input configuration error in One pulse STM32F407 mode. Cube defines pin as output. The previous version was also. On the STM32F103 with the same settings, the pin is defined correctly as an input!

dave.W
Associate
May 9, 2019

Hi,

I have problems generating code in V5.2.0 of STM32CubeMX for 'Other Toolchains (GPDSC)'. If I configure FreeRTOS the cmsis_os file references do not appear in the generated .gpdsc file. Reverting to V5.1.0 and following the same configuration the following lines are generated in the .gpdsc file:

    <file category="source" condition="" name="Middlewares\Third_Party\FreeRTOS\Source\CMSIS_RTOS\cmsis_os.c"/>

    <file category="header" condition="" name="Middlewares\Third_Party\FreeRTOS\Source\CMSIS_RTOS\cmsis_os.h"/>

cwonlee
Visitor II
May 17, 2019

Hi,

I have a problem to compile a generated code in CubeMx5.2 with STM32Cube FW_F4 V1.24.1 firmware.

I'm using Nucleo STM32F446ZE MCU in this test.

If I select a tool chain to "IAR7.6" then  the generated code  has a lot of compile errors.

I also tested other tool chain with "IAR 8.2" and "KEIL5.xx", this case was OK,  and STM32F0 firlware + IAR7.6 case also OK.