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

kruft
Associate II
May 27, 2019

1) Problem with Stemwin graphics. If I choose stm32l4r7vi MCU I cannot use ILI9341 driver of stemwin library, I see message: "ILI9341 is available only with MCU STM32F429_439 and when SPI peripheral enabled"(see attach). But why I cannot use this with stm32l4r7vi via FMC interface?0690X000008wR4CQAU.png

2) And next bug or feature: If you make "Generate code" and choose EWARM8 and then choose EWARM7 and repeat "Generate code" CubeMX not create correct EWARM7 files (solution: clear folder with project files)

3) Next bug: CubeMX generate for EWARM 7 cmsis_iccarm.h with next define:

#define __RESTRICT      __restrict

but right: #define __RESTRICT      restrict

4) There is a problem with Stemwin generation for 8 bit MCU 8080 LCD_X_Config(void) contain PortAPI.pfWrite16_A0 (may be after 16 bit to 8 bit switch in CubeMX)

MTeun
Associate
June 4, 2019

Similar problem with older ioc file. Cannot migrate...

2019-06-04 09:09:54,766 [INFO] MainDdrPanel:242 - [DDR PANEL] hideMenu

2019-06-04 09:09:58,898 [INFO] ImportTextPane:162 - (OptionalMessage_ERROR) IP (ADC1) : Parameter (Rank) has Id (0#ChannelRegularConversion) currently not set

2019-06-04 09:09:58,898 [INFO] ImportTextPane:162 - (OptionalMessage_ERROR) IP (ADC1) : Parameter (Channel) has Id (0#ChannelRegularConversion) currently not set

2019-06-04 09:09:58,899 [INFO] ImportTextPane:162 - (OptionalMessage_ERROR) IP (ADC1) : Parameter (SamplingTime) has Id (0#ChannelRegularConversion) currently not set

2019-06-04 09:09:58,902 [INFO] ImportTextPane:162 - (OptionalMessage_ERROR) IP (RCC) : Invalid parameter (FamilyName)

2019-06-04 09:09:58,904 [INFO] ImportTextPane:162 - (OptionalMessage_ERROR) IP (RCC) : Parameter (SDMMC2Freq_Value) has invalid value (216000000)

2019-06-04 09:09:59,167 [INFO] UtilMem:74 - End LoadConfig() Used Memory: 206508032 Bytes (317718528)

Exception in thread "AWT-EventQueue-0" java.lang.NoSuchFieldError: VeryLightGray25percent

   at com.st.microxplorer.plugins.thirdparty.gui.view.Constants.<clinit>(Constants.java:17)

   at com.st.microxplorer.plugins.thirdparty.gui.view.FilterPanel.createResetButton(FilterPanel.java:137)

   at com.st.microxplorer.plugins.thirdparty.gui.view.FilterPanel.<init>(FilterPanel.java:121)

   at com.st.microxplorer.plugins.thirdparty.gui.view.UITreeTableRework.buildMainPanel(UITreeTableRework.java:903)

   at com.st.microxplorer.plugins.thirdparty.gui.view.UITreeTableRework.buildPanels(UITreeTableRework.java:798)

   at com.st.microxplorer.plugins.thirdparty.gui.view.UITreeTableRework.<init>(UITreeTableRework.java:144)

   at com.st.microxplorer.plugins.thirdparty.gui.ThirdPartyMVC.<init>(ThirdPartyMVC.java:48)

   at com.st.microxplorer.plugins.thirdparty.ThirdParty.propertyChange(ThirdParty.java:643)

   at java.desktop/java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:341)

   at java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:333)

   at java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:266)

   at com.st.microxplorer.util.MXPropertyChangeSupport.firePropertyChange(MXPropertyChangeSupport.java:45)

   at com.st.microxplorer.mxsystem.MxSystem.completeLoadConfig(MxSystem.java:598)

   at com.st.microxplorer.plugins.filemanager.engine.OpenFileManager.LoadConfig(OpenFileManager.java:281)

   at com.st.microxplorer.plugins.filemanager.engine.OpenFileManager.loadConfigurationFile(OpenFileManager.java:198)

   at com.st.microxplorer.plugins.filemanager.engine.OpenFileManager.userChoiceLoadConfig(OpenFileManager.java:100)

   at com.st.microxplorer.plugins.filemanager.engine.MainFileManager.userChoiceAndLoadConfig(MainFileManager.java:169)

   at com.st.microxplorer.plugins.filemanager.FileManagerView$3.actionPerformed(FileManagerView.java:514)

   at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967)

   at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308)

   at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405)

   at java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262)

   at java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:369)

   at java.desktop/javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1020)

   at java.desktop/javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1064)

   at java.desktop/java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:297)

   at java.desktop/java.awt.Component.processMouseEvent(Component.java:6632)

   at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342)

   at java.desktop/java.awt.Component.processEvent(Component.java:6397)

   at java.desktop/java.awt.Container.processEvent(Container.java:2263)

   at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5008)

   at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)

   at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)

   at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)

   at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547)

   at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)

   at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)

   at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772)

   at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)

   at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)

   at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)

   at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)

   at java.base/java.security.AccessController.doPrivileged(Native Method)

   at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)

   at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)

   at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)

   at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)

   at java.base/java.security.AccessController.doPrivileged(Native Method)

   at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)

   at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)

   at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)

   at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)

   at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)

   at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)

   at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)

   at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)

Swithgin back to 5.0.1 as well

IHS1
Associate II
June 24, 2019

This version not allow code generation for H7 LL (release v1.4.0).

Dave Nadler
Senior III
June 25, 2019

@Nawres GHARBI​ - Where is the Eclipse plug-in version of this CubeMX?

The link you posted above seems to only provide the stand-alone EXE version.

Output of the stand-alone version cannot be read by the current STcubeIDE!

So, anyone that uses the version from the above link will be completely stuck!

I have asked the question on the Atollic forum but received no response.

https://forum.atollic.com/viewtopic.php?f=6&t=1868&p=4497#p4497

Thanks in advance for any help here,

Best Regards, Dave

Lars Beiderbecke
Senior III
September 4, 2019

Funny, I'm running CubeMX 5.3.0 right now ...

When I try to open my project, it asks me if I want to migrate my project to the latest firmware version. If I answer "migrate", my mouse pointer turns to "busy", and that's it. No status indicator, no progress bar, nothing.

How many hours am I supposed to wait? And what is it doing? I just want to enter my project with the new firmware being active, and I'll apply any changes needed myself.

EDIT: Oh, any I cannot "continue" either, which means my project is hosed, since I can no longer open it. Great job!

Piranha
Principal III
September 4, 2019

ST now offers downloading of previous versions. Go back to 5.2.1 or whatever works for You.

But even better don't use that buggy bloatware generation "feature" and develop a real actually working code. ;) Even if using HAL, which is also flawed, the result can be much better that CubeMX generated crap.

Romain1
Associate III
October 14, 2019

I'm having issues with incorrect Makefiles being generated with CubeMX 5.3.0 for STM32WB. After fixing the typos in the Makefile the compilation succeeds.

Where can/should I report this?

No thread for STM32CubeMX 5.3.0.

Can't create a new question for some reason...