STM32CubeMX 5.1.0 released
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-02-25 2:28 AM
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
- Labels:
-
STM32CubeMX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-02-25 6:44 AM
@Nawres GHARBI​ How do we access the bug tracker where the details of the CubeMX fixed and outstanding issues are explained?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-02-25 7:05 AM
Nawres, I suspect there might be something wrong with the package for MacOS
- CubeMX builtin "Check for Updates" doesn't detect an update from 5.0.1
- So I downloaded it from the website and extracted the zip. There is a Windows EXE for running CubeMX, but nothing for installing, so I can't even use the "java -jar" workaround from the doc file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-02-25 8:38 AM
@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 ;)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-02-25 8:59 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-02-25 10:39 AM
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;
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-02-25 11:30 AM
Can we trust RC6 or should I wait for a final release?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-02-26 12:11 AM
could you please attach the used ioc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-02-26 12:13 AM
Hi @Dave Nadler​
The bug tracker isn't accessible for the moment but it is planned to be in the future
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-02-26 12:15 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-02-26 12:17 AM
Hi @Joerg Wagner​
The RC6 is the final release for 5.1.0
