We are pleased to announce that the minor version 6.16.1 of STM32CubeMX is available.
What is new in 6.16.1:
This release addresses and resolves the issues outlined below:
- Users of STM32CubeMX version 6.13.0 and later may encounter a HardFault exception on STM32C0 products (STM32C011x, STM32C031x, STM32C051x, STM32C071x, STM32C091x, and STM32C092x) when using the internal HSI clock with HSI_SYS_DIV set to 1:
- When a user configures the system clock frequency (SYSCLK) at 24MHz value or greater, changes the HSI_SYS_DIV from its default value from 4 to 1, and increases the RCC SYSCLK Prescaler value (HSI_SYS_DIV1 > 1), STM32CubeMX generates code that temporarily configures SYSCLK with RCC_SYSCLK_DIV equal to 1. This causes the SYSCLK to be set at 48 MHz and the Flash wait state to be set at 0, which is outside of the allowed range.
- After migrating to STM32CubeMX 6.16.0, the ADC injected channels stopped working correctly for the STM32F3 products:
- The value for the Queue Injected Context parameter was changed from ENABLE in version 6.15.0 to DISABLE in version 6.16.0.
- The users were encountering some issues with CAD resource download functionality:
- When attempting to download any CAD file, the STM32CubeMX 6.16.0 freezes after showing an empty window.
- Linker file setting and the Code Language are not saved during the migration from STM32CubeIDE 1.19.0 to STM32CubeIDE 2.0.0:
- When updating the project from STM32CubeMX standalone, the Linker file assignment is deleted, the code generation type changes from C++ to C, and compilation errors occur.
Main fixed issues in 6.16.1:
Refer to the STM32 microcontroller wiki at:
https://wiki.st.com/stm32mcu/wiki/STM32CubeMX_errata_6.16.x
Known problems and limitations in 6.16.1:
Refer to the STM32 microcontroller wiki at:
https://wiki.st.com/stm32mcu/wiki/STM32CubeMX_errata_6.16.x
How to get STM32CubeMX 6.16.1:
- Under this link
- Or update your current installation of STM32CubeMX using: Help > Check for Updates
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
