Skip to main content
Nawres GHARBI
Nawres GHARBI
ST Technical Moderator
Feb 25, 2019 10:28 AM UTC
Question

STM32CubeMX 5.1.0 released

Dear community

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

What’s new ?

 

  • Performance enhancements for improved user experience.
  • Font size is now customizable (Click "Window" -> "Font size")
  • User interface updates
  • Graphics updates: TrueSTUDIO® is supported by TouchGFX Designer.

  • Added the support of the first MPU: STM32MP1 Series.
    • New devices: STM32MP151xx, STM32MP153xx, and STM32MP157xx.
    • New boards: STM32MP157A-EV1, STM32MP157C-EV1 and STM32MP157C-DK2
    • Features: Tj versus Ta calculation for PCC, DDR Test Suite, Device Tree generation, etc.
  • Added the support of the STM32WB Series:
  • New devices: STM32WB55xx.
    • Examples in MX format available in the STM32Cube_FW_WB_1.0.0 STM32CubeWB MCU Package.
    • Features: PCC Bluetooth® Low Energy feature.
  • Added the support of USBPD Middleware for G0 Series

Supported STM32Cube package versions:

·          STM32F0 V1.9.0

·          STM32F1 V1.7.0

·          STM32F2 V1.7.0

·          STM32F3 V1.10.0

·          STM32F4 V1.24.0

·          STM32F7 V1.15.0

·          STM32G0 V1.1.0

·          STM32H7 V1.3.2

·          STM32L0 V1.11.0

·          STM32L1 V1.8.1

·          STM32L4 V1.13.0

·          STM32MP1 V1.0.0

·          STM32WB V1.0.0

Main Fixed issues

 

  • 46874 [MX-Clock] include frac formulas in frequency calculation when PLL frac is enabled.
  • 51206 [MX-TIM] Break filter to be removed for TIM15, 16 and 17.
  • 53264 [MX-Pinout][STM32H750IBKx] G10 must be VSS and not VDD.
  • 55690 [MX-Board] Wrong configuration of special PHY reg for STM32F746 Discovery.
  • 56760 RCC for LTDC clock of STM32L4R9.
  • 56828 [MX-ETH]PHY DP83848 should support also RMII mode.
  • 56999 FreeRTOS™ initialization sequence.
  • 57348 [MX-LWIP] Exception generated due to undefined parameter in the ftl.
  • 57520 [MX-SPI] Missing Alternate Function Open Drain in SPI configuration mode.
  • 58043 [MX-TouchSensing] Missing user label in function MyTKeys_ErrorStateProcess().

Known limitations

Please read the Release note for the known limitations

https://www.st.com/resource/en/release_note/dm00107607.pdf

This topic has been closed for replies.

30 replies

Noppe.Jack
Noppe.Jack
Senior
Feb 25, 2019 12:58 PM UTC

Hi Nawres,

Thank you for this update and for such a great tool in general. I have two quick questions:

  1. Curiosity: When do you think the update will be available for download?
  2. Serious: Where can I get more info on the issue & fix for the item "56999 FreeRTOS™ initialization sequence."

Nawres GHARBI
Nawres GHARBIAuthor
ST Technical Moderator
Feb 25, 2019 1:12 PM UTC

Hi @Noppe.Jack​ 

The update will be available very soon for download, just few hours for the website to synchronize

Concerning 56999 FreeRTOS™ initialization sequence, it has been fixed and will be available in the 5.1.0

Hope you enjoy the new release

Noppe.Jack
Noppe.Jack
Senior
Feb 25, 2019 1:18 PM UTC

Thanks ... any info on what the original problem was? (I want to see if this relates to a problem I was having).

MNapi
MNapi
Senior II
Feb 25, 2019 2:05 PM UTC

Hi I have been working lately with STM32L416KBU6

When I setup the clock in cube mx for example 50 MHz I get in Keil, which looks like half the speed 25 MHz. I wonder if there is a bug in Cube MX.

I noticed that he clocks are never accurate, I can never get like nice 1 MHz or 2 MHz. I wonder it is cheap low end board and you cannot expect too much.

 RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_MSI;

 RCC_OscInitStruct.MSIState = RCC_MSI_ON;

 RCC_OscInitStruct.MSICalibrationValue = 0;

 RCC_OscInitStruct.MSIClockRange = RCC_MSIRANGE_6;

 RCC_OscInitStruct.PLL.PLLState = RCC_PLL_ON;

 RCC_OscInitStruct.PLL.PLLSource = RCC_PLLSOURCE_MSI;

 RCC_OscInitStruct.PLL.PLLM = 1;

 RCC_OscInitStruct.PLL.PLLN = 25;

 RCC_OscInitStruct.PLL.PLLQ = RCC_PLLQ_DIV2;

 RCC_OscInitStruct.PLL.PLLR = RCC_PLLR_DIV2;

 if (HAL_RCC_OscConfig(&RCC_OscInitStruct) != HAL_OK)

Nawres GHARBI
Nawres GHARBIAuthor
ST Technical Moderator
Feb 25, 2019 2:07 PM UTC

Hi @MNapi​ 

could you please create a separate ticket for this issue please

MNapi
MNapi
Senior II
Feb 25, 2019 2:14 PM UTC

I could if I only knew where and how,

Nawres GHARBI
Nawres GHARBIAuthor
ST Technical Moderator
Feb 25, 2019 2:23 PM UTC

how did you measure the 25 MHz instead of the 50 MHz

MNapi
MNapi
Senior II
Feb 25, 2019 6:39 PM UTC

When I setup PWM or OC clocks for example I did setup the main clock in Clube MX 50 Mhz

I used 50 divider to get 1 MHz instead I was getting something like 490 KHz. They were pretty close but never close. Like the main oscillator was not accurate.

When I did 25 divider I got like 990 KHz. I do have oscilloscope connected to the pins so I can see what is coming out.

I cannot see doing any mistake all looks simple and straightforward in Cube MX

But still if I do 50 MHz in Cube Mx shouldn't I get

RCC_OscInitStruct.PLL.PLLN = 50;

instead of

RCC_OscInitStruct.PLL.PLLN = 25;

Nawres GHARBI
Nawres GHARBIAuthor
ST Technical Moderator
Feb 26, 2019 8:11 AM UTC

could you please attach the used ioc

Dave Nadler
Dave Nadler
Senior III
Feb 25, 2019 2:44 PM UTC

@Nawres GHARBI​ How do we access the bug tracker where the details of the CubeMX fixed and outstanding issues are explained?

Nawres GHARBI
Nawres GHARBIAuthor
ST Technical Moderator
Feb 26, 2019 8:13 AM UTC

Hi @Dave Nadler​ 

The bug tracker isn't accessible for the moment but it is planned to be in the future

Dave Nadler
Dave Nadler
Senior III
Feb 25, 2019 4:38 PM UTC

@Nawres GHARBI​ It would be great if you would post these announcements AFTER the stuff is actually available on the web site (unless you intend to annoy your customers ;)

Nawres GHARBI
Nawres GHARBIAuthor
ST Technical Moderator
Feb 26, 2019 8:15 AM UTC

Hi @Dave Nadler​ 

The package was available on the web site when the post has been published, it may sometimes have a little late to appear to you depending on the web synchronization

anio1491
anio1491
Associate II
Feb 25, 2019 4:59 PM UTC

Hello,

I was able to update my CubeMX (finally) to the release today (v5.1.0), but I am not able to update the L0 firmware package to the lastest version. I can see that there is a new packet available, but the download fails, and therefore, I cannot generate anymore code.

Any idea on what's wrong?

Please see screenshots attached.

Regards,

Andreea

0690X000006DpUMQA0.png

0690X000006DpURQA0.png

Nawres GHARBI
Nawres GHARBIAuthor
ST Technical Moderator
Feb 26, 2019 8:50 AM UTC

Hi @anio1491​ 

Trying to fix a server issue

Joerg Wagner
Joerg Wagner
Senior III
Feb 25, 2019 7:30 PM UTC

Can we trust RC6 or should I wait for a final release?

Nawres GHARBI
Nawres GHARBIAuthor
ST Technical Moderator
Feb 26, 2019 8:17 AM UTC

Hi @Joerg Wagner​ 

The RC6 is the final release for 5.1.0

Joerg Wagner
Joerg Wagner
Senior III
Feb 26, 2019 2:56 PM UTC

How to get rid of this message after generating code?

0690X000006DrRAQA0.png

Migrated a 5.0.1 project and never used GFXSIMULATOR in my life.

I find no appropiate config setting in the file <myproject>.ioc

There is no warning when building a new project from scratch.

Dave Nadler
Dave Nadler
Senior III
Apr 4, 2019 4:53 PM UTC

@Nawres GHARBI​ - Where is CubeMX plug-in 5.1? I'm trying to use this within Atollic.

I downloaded the software on this page: https://www.st.com/en/development-tools/stm32cubemx.html

Unfortunately that seems to be only the stand-alone executable, no plugin ZIP.

Thanks!

Dave Nadler
Dave Nadler
Senior III
Apr 4, 2019 5:38 PM UTC

@Nawres GHARBI​ - Running the stand-alone CubeMX (as plug-in is missing).

Try to generate code, says need to update repository, then fails to download (this bug reported before).

Unable to generate code now...

Help!

Thanks,

Best Regards, Dave

0690X0000089w5OQAQ.png

Terms & ConditionsAccessibility statement