STM32CubeMX
Release fixes ¶
Main fixed issues for 6.18.0 ¶
|
ID |
Summary |
|---|---|
|
TMX1-57673 |
In STM32CubeMX version 6.17.0, STM32CubeMX projects that use STM32U575 products could not activate ETH as MII_PTP_SYNCHRO. STM32CubeMX version 6.18.0 fixes this issue. |
|
TMX1-57142 |
On macOS aarch64 systems without Rosetta installed, STM32CubeMX version 6.17.0 for aarch64 could not launch. STM32CubeMX version 6.18.0 fixes this issue. |
|
TMX1-56876 |
When a new project was created with STM32MP215F-DK, if UART4 in MN33NS was activated and code was generated, the UART clock initialization was not generated. STM32CubeMX version 6.18.0 fixes this issue. |
|
TMX1-56659 |
When STM32CubeMX version 6.17 generated a project for STM32H743ZIT6 with ADC3 enabled and IN6 activated, hadc3.Init.ClockPrescaler = ADC_CLOCK_ASYNC_DIV2 was not generated in the static void MX_ADC3_Init(void) function. STM32CubeMX version 6.18.0 fixes this issue. |
|
TMX1-56323 |
When a new STM32U5 project was created with STM32CubeMX version 6.16.1, enabling JPEG and generating code did not generate the Utilities/JPEG directory that contains the JPEG files. STM32CubeMX version 6.18.0 fixes this issue. |
|
TMX1-56778 |
In STM32CubeMX version 6.17.0, when the pin stacking option was used in pinout for STM32H743, enabling pin stacking with PB2 (SAI1_SD_A, GPIO_Input selected) caused STM32CubeMX to freeze and display an error in the console. STM32CubeMX version 6.18.0 fixes this issue. |