STM32CubeMX errata 6.11.x

1. Main fixed issues for 6.11.1

ID Summary
176638 STM32CubeMX V6.11.0 has lost 3 modes for all the STM32H7 series but the STM32H7Rx/7Sx microcontrollers on ADC3.

In STM32CubeMX V6.11.0, three modes (VBat Channel, Temperature Sensor Channel, Vrefint Channel) have accidently been removed for ADC3.

This defect impacts all the STM32H7 series but the STM32H7Rx/7Sx microcontrollers.

The STM32CubeMX V6.11.1 reinstates the lost modes.

176645 STM32CubeMX V6.11.0 has lost the "JTAG (5 pins)" debug mode for all the STM32H7 series but the STM32H7Rx/7Sx microcontrollers.

In STM32CubeMX V6.11.0, the "JTAG (5 pins)" debug mode is no longer present for the user to select.

If the user saves the project using that debug mode, STM32CubeMX V6.11.0 automatically selects "JTAG (4 pins)" instead.

This defect impacts all the STM32H7 series but the STM32H7Rx/7Sx microcontrollers.

The "JTAG (5 pins)" debug mode is back in STM32CubeMX6.11.1.

176658 STM32CubeMX V6.11.0 does not generate the call to the "HAL_PWREx_EnableVddA()" function for the STM32U5 series.

In STM32CubeMX V6.11.0, the call to the function "HAL_PWREx_EnableVddA()" is not generated as it should.

This defect impacts all STM32U5 MCUs.

The STM32CubeMX V6.11.1 fixes this issue.

176763 An issue affects ADC oversampling when writing OVSR bits for all the STM32H7 series but the STM32H7Rx/7Sx microcontrollers.

When enabling the regular oversampling for ADC using HAL, the HAL driver does not write the OVSS bits correctly.

This defect impacts all the STM32H7 series but the STM32H7Rx/7Sx microcontrollers.

With STM32CubeMX V6.11.1, the register is written correctly.

177071 Compilation error related to the MX_FLASH_Init() function for the STM32H5 series.

In STM32CubeMX V6.11.0, when enabling FLASH, activating the 'USERType_Config' parameter, and then generating the code, a compilation error occurs stating that 'USERType_Config2' is undeclared.

This defect impacts all STM32H5 MCUs.

The STM32CubeMX V6.11.1 resolves this compilation error.

177285 An error occurs when switching the timebase source from SysTick to a timer for the STM32C0 series

In STM32CubeMX V6.11.0, when switching the timebase from SysTick to a timer and generating a project using the STM32CubeIDE toolchain, a compilation error states that stm32c0xx_hal_tim.h is missing.

This defect impacts all STM32C0 MCUs

The STM32CubeMX V6.11.1 resolves this generation error.

2. Main fixed issues for 6.11.0

ID Summary
138388 STM32MP13x: the ioc file cannot be opened if generated from STM32CubeMX standalone.
151683 Fixing LSE driver capability levels.
159135 Fixing missing RTC initialization code in nonsecure context.
159544 Secure folder created when "Secure Project" is not set to be generated.
164200 Change the relative path of directory for user actions before and after code generation.
166529 TRACESWO not working in dual core mode.
166708 Boot path user experience enhanced.
167288 AF11/ETH details for STM32H573xx are inconsistent.
168041 Fixing a build error when using STM32CubeIDE with VirtualMode in USART3.IPParameters.
168059 Boot path: Debug authentication deactivation can lead to bricked device.
168811 STM32CubeMX does not copy all necessary I3C headers.
168977 Resolve the missing code for the ADC injected mode using LL driver when using STM32H7 series.
169175 Function HAL_PWREx_EnableVddUSB() needs to be called for proper USB operation.
169278 Fixing the filter of the MCU selector with ETH, SMPS, and 2 Mbytes of flash memory.
169336 ETH is missing on STM32H5.
169503 Adjust the configuration file to remove the UART/USART #defines when no UART/USART peripheral is selected.
170681 Problem with installing OPUS with STM32CubeMX.
172964 Correction of Nominal Time SegX to start at 1 when using FDCAN.

3. Known limitations

  • On Linux®, when a self-upgrade occurs, the STM32CubeMX V6.9.0 and the later releases do not restart automatically. The user must restart STM32CubeMX manually to finalize the update.
  • For a project with both AES and mbedTLS activated, if the option “Generate peripheral initialization as a pair of '.c/.h' files per peripheral” is checked in the CodeGenerator tab, an issue occurs when compiling under IAR Embedded Workbench®. It is advised to uncheck this option.
  • After selecting “List Pinout Compatible MCUs”, the import process may not work properly (mainly for multicore or Arm® TrustZone®(a) enabled projects).
  • DMA handlers are not generated for the DCMI and PSSI peripherals.
  • In the case of file access issue during a compilation with some examples on partner IDEs (for instance with the “cannot open-source input file” error message), consider to move either the full package manually, or just the example. For the example, use the Example Selector from STM32CubeMX, closer to the root of the disk (long path issue).
  • If “CAD resources” feature is not fully functional when using “Use System Proxy parameters”, try to use the “Manual Configuration of Proxy Server” or “No proxy” instead. (Menu : [Updater Settings…]>[Connection Parameters])
  • When unzipping a package on a macOS® system, use an official macOS® application such as the default graphical archive application, or the ditto tool in the command line:
    $ditto -x -k setupArchive.zip
    If a Linux®-like application is used (such as unzip), the expanded files lose the signature and are not recognized as signed.
Note: a. Arm and TrustZone are registered trademarks of Arm Limited (or its subsidiaries) in the US and/or elsewhere.

3.1. When selecting microcontrollers in the STM32F4 series and STM32F7 series

  • IPv6 activation is not yet fully supported by the EWARM and MDK-ARM toolchains. Thus, it causes compilation errors with MDK-ARM and compilation warnings with EWARM.

3.2. When selecting microcontrollers in the STM32G0 series

  • Regarding the cohabitation between USB and USB Power Delivery, the VID and PID of USB Power Delivery and USB are not automatically aligned. VID/PID values must be aligned manually.
  • When both the USB Power Delivery and FreeRTOS™ CMSIS_V1 middleware are enabled at the same time, the FreeRTOS™ eTaskGetState parameter must be enabled in the include parameters tab.

3.3. When selecting microcontrollers in the STM32H5 series

  • When migrating projects with OEM-iROT boot path from STM32CubeMX V6.8.x to STM32CubeMX V6.10.x or later releases, the user might need to reconfigure ROT_Provisioning.
  • If the Secure Manager configuration is updated through the TPC used in standalone mode, the user must relaunch the provisioning.bat.
  • The makefile generation no longer works as soon as the project structure is changed from "Secure Project only" or "Non Secure Project only" to "Secure Project and Non Secure Project enabled (dual project)".
  • In Microsoft® Azure® NetX Duo, some configuration flags, which are not used in the STM32Cube firmware package examples, might be nonfunctional when combined.

3.4. When selecting microcontrollers in the STM32H7 series

  • For the STM32H7Rx/7Sx microcontrollers in the STM32H7 series, to enable debugging for ExtMemLoader projects with MDK-ARM, user must do the following:
    • Display the "Option for target dialog"
    • under the Debug tab uncheck "Run to main"
      Run to main.png
    • under the Utilities tab uncheck "Update Target before Debugging"
      Update Target before Debugging.png
  • MDMA and HSEM are not supported in LL. Only HAL is supported.
  • When activating any mode under SPDIFRX:
    • The alternate function configuration code is not generated in the HAL_SPDIFRX_MspInit function in the stm32h7xx_hal_msp.c file.
    • Add the workaround code in the user section after “GPIO_InitStruct.Speed =GPIO_SPEED_FREQ_LOW;” as described in Table 2 depending on the channel and selected pin.
Table 2. Workaround for alternate function configuration code
Channel Selected pin Workaround code
IN0 PD7 /* USER CODE BEGIN alternate function configuration */
GPIO_InitStruct.Alternate = GPIO_AF9_SPDIF;
/* USER CODE END alternate function configuration */
PG11 /* USER CODE BEGIN alternate function configuration */
GPIO_InitStruct.Alternate = GPIO_AF8_SPDIF;
/* USER CODE END alternate function configuration */
IN1 PD8 /* USER CODE BEGIN alternate function configuration */
GPIO_InitStruct.Alternate = GPIO_AF9_SPDIF;
/* USER CODE END alternate function configuration */
PG12 /* USER CODE BEGIN alternate function configuration */
GPIO_InitStruct.Alternate = GPIO_AF8_SPDIF;
/* USER CODE END alternate function configuration */
IN2 PC4 /* USER CODE BEGIN alternate function configuration */
GPIO_InitStruct.Alternate = GPIO_AF9_SPDIF;
/* USER CODE END alternate function configuration */
PG8 /* USER CODE BEGIN alternate function configuration */
GPIO_InitStruct.Alternate = GPIO_AF8_SPDIF;
/* USER CODE END alternate function configuration */
IN3 PC5 /* USER CODE BEGIN alternate function configuration */
GPIO_InitStruct.Alternate = GPIO_AF9_SPDIF;
/* USER CODE END alternate function configuration */
PG9 /* USER CODE BEGIN alternate function configuration */
GPIO_InitStruct.Alternate = GPIO_AF8_SPDIF;
/* USER CODE END alternate function configuration */

3.5. When selecting dual-core microcontrollers in the STM32H7 series

  • Only Boot0 is supported: both cores boot at once.
  • Import from and to dual-core STM32H7 is not supported.
  • For memory-to-memory DMA or BDMA or MDMA configuration, the initialization code is generated for both cores.
  • OpenAMP issue when compiling under EWARM and MDK-ARM when OpenAMP is activated under STM32CubeMX:
    • To avoid link errors in OpenAMP when compiling in EWARM IDE, add the next four lines of code in the linker files (.icf):
/* Create region for OPENAMP */
define symbol __OPENAMP_region_start__ = 0x38000400;
define symbol __OPENAMP_region_size__ = 0xFC00;
export symbol __OPENAMP_region_start__;
export symbol __OPENAMP_region_size__;
  • To avoid link errors in OpenAMP when compiling in MDK-ARM IDE, add the next four lines of code in the linker files (.sct):
; ***** Create region for OPENAMP *****
.resource_table +0 ALIGN 4 { ; resource table
*(.resource_table)
}
; Shared Memory area used by OpenAMP
__OpenAMP_SHMEM__ 0x38000400 EMPTY 0xFC00 {}
  • OpenAMP under STM32CubeIDE needs linker file update:
    • The following lines must be added under the .ld file:
/* Specify the memory areas */
MEMORY
{
...
m_ipc_shm (RW) : ORIGIN = 0x38000400, LENGTH = 63K
}
/* Symbols needed for OpenAMP to enable rpmsg */
__OPENAMP_region_start__=ORIGIN(m_ipc_shm);
__OPENAMP_region_end__=ORIGIN(m_ipc_shm)+LENGTH(m_ipc_shm);

3.6. When selecting microcontrollers in the STM32L5 series

  • Arm® TrustZone® support:
    • Fixed default SAU is configured in the application partition_stm32l552xx.h and partition_stm32l562xx.h files.
    • Import does not work for TrustZone® projects (TZEN=1).
  • To facilitate the peripheral privilege configuration, from STM32CubeMX V6.2.0, the GTZC peripheral is split into two domains: secure and nonsecure. The side effect is that, in the case of project migration from a release version before V6.2.0, if GTZC is configured in both the secure and nonsecure domains with previously configured privilege peripherals on a nonsecure peripheral, this configuration is lost during the migration. The GTZC_NS privileges must be configured again.
  • Regarding the cohabitation between USB and USB Power Delivery, the VID and PID of USB Power Delivery and USB are not automatically aligned. VID/PID values must be aligned manually.

3.7. When selecting microcontrollers in the STM32U5 series

  • Regarding the cohabitation between Azure® RTOS USBX and USB Power Delivery, the VID and PID of USB Power Delivery and USBX are not automatically aligned. VID/PID values must be aligned manually.
  • To avoid linking issues with Keil® MDK-ARM when a USBX Core System is enabled, "Device CoreStack FS" or "Host CoreStack FS" must be enabled according to the USB_OTG_FS selected mode.
  • To avoid compilation issues when one DMA channel request is activated for one TIMx peripheral, replace htim_xx by htim_base. For example, replace:
    __HAL_LINKDMA(htim_oc, hdma[TIM_DMA_ID_CC1], handle_GPDMA1_Channel11);
    by
    __HAL_LINKDMA(htim_base, hdma[TIM_DMA_ID_CC1], handle_GPDMA1_Channel11);
  • In Microsoft® Azure® NetX Duo, some configuration flags, which are not used in the STM32Cube firmware package examples, might be nonfunctional when combined.

3.8. When selecting microcontrollers in the STM32WB series

  • THREAD is not supported in the power consumption calculator (PCC) for the STM32WB series.
  • The value of the CFG_BLE_MAX_CONN_EVENT_LENGTH parameter in the file app_conf.h is wrongly formatted: uint16_t is used instead of uint32_t. This impacts the Data Throughput of the application since the max value is 0xFFFF, while it should be 0xFFFF FFFF. The defined value must be changed manually in the generated code.

3.9. When selecting microcontrollers in the STM32WBA series

  • When the selected middleware is STM32WPAN for Bluetooth® Low Energy with the parameter CFG_BLE_NUM_LINK set above 8, use the Bluetooth® Low Energy link layer library LinkLayer_BLE_Basic_20_links_lib.a with the header file from the path \link_layer\ll_cmd_lib\config\ble_basic_20_links.

3.10. When selecting microcontrollers in the STM32WL series

  • If LoRaWAN®, SubGHZ_Phy or SigfoxTM middleware is used with the option Generate peripheral initialization as a pair of '.c/.h' files per peripheral disabled, it is advised to untick the visibility of the SUBGHZ and IPCC peripherals in [Project Manager]>[Advanced Settings] Generated Function Calls panel to avoid an issue when compiling.
  • Import from and to dual-core is not working for the STM32WL series.
  • For dual-core products, IPCC LL + RF middleware (LoRaWAN®, SigfoxTM, and SubGHZ_Phy) are not supported.
  • If a Sigfox project is generated with MDK-ARM, the following option must be set in the project Options C/C++(AC6) panel: Misc Controls: -fshort-enums
  • The SUBGHZ peripheral is forced on the Cortex®-M0+.
  • In the case of a project migration from a release version before V6.2.0, to facilitate the GTZC configuration, some previously default configuration ("enabled"/"disabled") has been moved to "default" configuration. This new state provides the default configuration of the MCU without any code generation. Users specifically needing this code generation must modify this state.
  • When compiling under IAR Embedded Workbench®, in case of dual-core products, the user must activate the share mode in both CM4 and CM0PLUS ST-LINK project options.
  • The "Time base: System tick timer" value selected in the NVIC configuration panel is not used for the code generation. This value must be updated by the end user in the generated code.
  • KMS and STM32Cube Azure® RTOS ThreadX cannot be enabled in the same core.

3.11. When selecting microprocessors in the STM32MP1 series

  • DMA nodes are generated in the device tree, but the DMA properties in the IP clients nodes are not generated.
  • Import from and to MPU projects does not work properly.
  • Dual-core project structure compatibility break : the action to import (migrate or continue) projects created with versions earlier than STM32CubeMX V5.3.0 is supported but requires the manual copy of USER SECTIONS for the device tree and Cortex®-M4 firmware from the former folder structure (DeviceTree/Inc/Src) to the new one (CA7/DeviceTree - CM4/Src - CM4/Inc).
  • Additional software is not supported.
  • RCC generation in Production mode is not supported on the coprocessor side. Only the Engineering mode is supported.
    By default, the STM32CubeMX-generated code is compliant with the Engineering mode. Therefore, the call of the following clock functions must be removed in the Production mode since these clocks are then managed by Linux®: SystemClock_Config(), PeriphCommonClock_Config(), and HAL_RCCEx_PeriphCLKConfig():
    • The system parts (SystemClock_Config() and PeriphCommonClock_Config()) can be removed in STM32CubeMX by selecting [Not Generate function call] for RCC in the Project Manager, then Advanced Settings tabs.
    • HAL_RCCEx_PeriphCLKConfig() must be removed manually from file stm32mp1xx_hal_msp.c (STM32CubeMX-generated code).
    • To make the user code compatible with both the engineering and production modes, the above RCC functions can be put under dynamic condition
      if(IS_ENGINEERING_BOOT_MODE()).
  • On macOS®, installation issues may result from the fact that the install is not signed. Use the following procedure:
    • Download STM32CubeMX on a Window® OS personal computer.
    • Copy the downloaded install into the macOS® personal computer.
    • Launch the install.
  • OpenAMP warning when compiling under MDK-ARM if OpenAMP is not activated under STM32CubeMX:
    • Remove the next four lines of code from the linker files (.sct) to avoid warning “No section matches pattern *(.resource_table)”:
; ***** Comment these 4 lines if OPENAMP is not used *****
.resource_table +0 ALIGN 4 { ; resource table
*(.resource_table)
}
; Shared Memory area used by OpenAMP
__OpenAMP_SHMEM__ 0x10040000 EMPTY 0x8000 {}
  • Device tree generation: the "pwr" user section name is changed to "pwr_regulators".
    • Existing code in the "pwr" user section must be backed up and reported manually into the new "pwr_regulators" user section after code generation.
  • About the HRTIM peripheral: for the "Set Source Selection" & "Reset Source Selection" parameters, the "No source is selected" must be manually set for any unused source before decreasing the number of sources.
  • When using the STM32CubeMP13 bare-metal firmware, the secure mode of the peripheral RTC is not available for the STM32MP13xx microprocessors. It is only available when the STM32CubeMP1 MCU package is used.
  • When using the STM32CubeMP13 bare-metal firmware and activating Azure® RTOS ThreadX, the STM32CubeIDE linker file must contain the following section to avoid compilation issues:
.stack:
:{
: _stack_bottom = ABSOLUTE(.) ;
: /* Allocate room for stack. This must be large enough for the
: IRQ, FIQ, and SYS stack if nested interrupts are
: enabled.*/
: . = ALIGN(8) ;
: . += 32768 ;
: _sp = . - 16 ;
: _stack_top = ABSOLUTE(.) ;
: } >RAM
: _end = .;

3.12. When using the memory management tool

  • When using Memory Management Tool, the toolchains CMake and makefile are not supported.
  • When using Extmem Manager with LRUN boot mode, the memory management tool cannot generate a linker file including the region named "LOAD_REGION". This region is displayed in the UI as reserved. This limitation is valid for all toolchain/IDE.
  • The options “ISR”, “BootInfo”, and “ThreadX” are not available in the linker file for the MDK-ARM toolchain.
  • When "ThreadHep section" is selected, the linker file is not updated accordingly.
  • When "isrvercor" is selected, the linker file is not updated accordingly.
  • When "Boot Info" is selected (available only in the STM32WB series), the linker file is not updated to reflect the change.

3.13. When using Start From Board

  • The functionality is fully available only for NUCLEO-C031C6, NUCLEO-U031R8, NUCLEO-U083RC, NUCLEO-U5A5ZJ-Q, NUCLEO-H563ZI, NUCLEO-H533RE, and NUCLEO-H7S3L8.
  • With the NUCLEO-U5A5ZJ-Q and NUCLEO-H563ZI, NUCLEO-H533RE, the functionality is not available with TrustZone® activated.
  • The functionality is not compatible with software packs implementing BSP drivers.

3.14. When using the Example Selector

  • When starting an example from the Example Selector and regenerating the code, some files can be duplicated. It can lead to potential compilation issues. In this case, remove the duplicated files.

3.15. When using additional software packs

  • If a software component refers to a specific peripheral, this peripheral must be initialized with HAL APIs (not with LL APIs).
  • When using dual-core devices, if a software component refers to a specific peripheral, this peripheral must be assigned only to the same core as the software component.
  • When a pack is disabled, the generated files are not removed from the project.
    • Workaround: remove these files manually.
  • Possible issues with component dependencies in the Additional Software components selection window.
    • Workaround: click on the Refresh button from the Embedded Software Packages Manager.
  • When using the GNSS pack, users must not migrate their project from 3.x to 4.0.0.
  • Functionalities that are not supported:
    • maxInstances, isDefaultVariant, generator attributes of the component element
    • Dtz, Ddsp, Dsecure attributes of the condition element
    • repository element
    • tag and url attributes of a release element
    • dominate element
    • public attributes for the file element
    • preIncludeLocal and preIncludeGlobal file category attributes
    • Pre_Include_Local_h element
    • Pre_Include_Global_h element
    • Pack components where attribute values come with a "." character
  • Compilation issues when using both X-CUBE-AZRTOS-H7 v1.1.0 and OpenAMP middleware in the same project with minimum version MDK-ARM v5.32:
    X-CUBE-AZRTOS-H7 v1.1.0 requires Arm C compiler version 6 while OpenAMP is not compatible with this version (only Arm C compiler version 5 is supported). The workaround consists in using X-CUBE-AZRTOS-H7 v1.0.0 instead. This one is compatible with Arm C compiler version 5.
  • In the case of an error message when downloading SEGGER I-CUBE-embOS:
    • Download SEGGER.I-CUBE-embOS manually from the SEGGER download site at https://www.segger.com/downloads/embos.
    • Open the STM32CubeMX Embedded Software Packages Manager.
    • Use the option Load from Local and select the pack.

3.16. STM32CubeIDE toolchain

  • It is functional only with a Java 8 64-bit virtual machine with versions earlier than STM32CubeMX V5.6.1.

3.17. DDR test suite

  • STM32CubeProgrammer (STM32CubeProg) is not supported from v2.10.0 onwards.

3.18. User manual

  • Some chapters in the user manual STM32CubeMX for STM32 configuration and initialization C code generation (UM1718) are not fully up to date.

3.19. Symbolic links on Ubuntu

  • When using Ubuntu 20.04 if you use a symbolic link to refer to the "Firmware Relative Path" in the STM32CubMX Project Manager tab, it will be translated to the absolute path before saving down.


4. Recommendations

4.1. Command line authentication required

Since introduction of authentication at the command level, we recommend our costumers to review their scripts. They should make sur they are authenticating before trying to download a package or before trying to generate code on the command line. Failure to do so will result on errors displayed on the command line.

4.2. DDR binaries for the STM32MP1 boards

The DDR binaries needed to connect to the STM32MP1 boards are available from the GitHub website at https://github.com/ with the keyword STMicroelectronics/STM32DDRFWUTIL.

4.3. List pinout-compatible microcontrollers

The loading of microcontrollers can take a long time if all series and all packages are selected. If the loading takes too long, stop it, refine the microcontroller filters on a dedicated series or package, and restart the loading.

4.4. How to improve the wake-up from Stop sequences without relying on the global SystemClock_Config()

The SystemClock_Config provided in the HAL examples is intended to be used to configure the system clock at startup. It is not recommended to use it to restore the clock settings after a Stop mode.
To keep the wake-up as quick as possible, it is highly recommended to restore only what has been changed by the hardware to enter the Low-power mode. This is typically the case for the oscillators and system clock sources. The RCC configuration registers are unchanged, and there is no need to restore them.
Typically, after a Stop mode, it is recommended to call a separate SystemClockConfig_STOP after the wake-up that enables the LSE and PLL, and selects PLL as system clock source (LSE and PLL are disabled in Stop mode). Find below an example of SystemClockConfig_STOP (provided in the HID_Standalone_LPM application):

static void SystemClockConfig_STOP(void)
{
#if defined (USB_USE_LSE_MSI_CLOCK)
:/* Configures system clock after wake-up from STOP: enable LSE,
:PLL and select PLL as system clock source (LSE and PLL are disabled in Stop mode) */
:__HAL_RCC_LSE_CONFIG(RCC_LSE_ON);
:/* Wait till HSE is ready */
:while(__HAL_RCC_GET_FLAG(RCC_FLAG_LSERDY) == RESET)
:{}
:/* Enable the main PLL. */
:__HAL_RCC_PLL_ENABLE();
:/* Wait till PLL is ready */
:while(__HAL_RCC_GET_FLAG(RCC_FLAG_PLLRDY) == RESET)
:{}
:/* Select PLL as SYSCLK */
:MODIFY_REG(RCC->CFGR, RCC_CFGR_SW, RCC_SYSCLKSOURCE_PLLCLK);
:/* Wait till system clock switch to PLL */
:while (__HAL_RCC_GET_SYSCLK_SOURCE() != RCC_CFGR_SWS_PLL)
:{}
#elif defined (USB_USE_HSE_CLOCK)
:/* Configures system clock after wake-up from STOP: enable HSE,
:PLL and select PLL as system clock source (HSE and PLL are disabled in Stop mode) */
:__HAL_RCC_HSE_CONFIG(RCC_HSE_ON);
:/* Wait till HSE is ready */
:while(__HAL_RCC_GET_FLAG(RCC_FLAG_HSERDY) == RESET)
:{}
:/* Enable the main PLL. */
:__HAL_RCC_PLL_ENABLE();
:/* Wait till PLL is ready */
:while(__HAL_RCC_GET_FLAG(RCC_FLAG_PLLRDY) == RESET)
:{}
:/* Select PLL as SYSCLK */
:MODIFY_REG(RCC->CFGR, RCC_CFGR_SW, RCC_SYSCLKSOURCE_PLLCLK);
:/* Wait till system clock switch to PLL */
:while (__HAL_RCC_GET_SYSCLK_SOURCE() != RCC_CFGR_SWS_PLL)
:{}
#endif /* USB_USE_LSE_MSI_CLOCK */
}
Retrieved from "https://wiki.stmicroelectronics.cn/stm32mcu/index.php?title=STM32CubeMX_errata_6.11.x&oldid=56187"