Skip to main content
DGeor.4
DGeor.4
Associate
March 2, 2021
Solved

RCC_CR_HSEBYP definition removed from CMSIS in STM32CubeWB v1.10.0

  • March 2, 2021
  • 2 replies
  • 1192 views

In STM32CubeWB v1.10.0, the definitions of RCC_CR_HSEBYP (HSE bypass control) were removed from the CMSIS files for STM32WB5x MCUs. Also parts of the HAL that configure HSE bypass mode were removed. In the release notes it says "Remove RCC_CR_HSEBYP" but there is no further detail about this.

I could not find any mention of HSEBYP in the latest errata for the STM32WB5x.

What is the reason this definition was removed from the CMSIS and HAL, does this HSE bypass feature still work on STM32WB5x parts?

This topic has been closed for replies.
Best answer by Imen.D

Hello @DGeor.4​ and welcome to the STM32 Community =)

All HSE32 BYPASS description/definition are removed from STM32WBxx reference manuals and HAL, to be replaced by HSE32 clock input mode.

Please, mark the answer as "Best Answer" by clicking on the "Select as Best" button if it fully answered your question, this can be very helpful for Community users to find this solution more quickly.

Imen

2 replies

I
Imen.DBest answer
ST Technical Moderator
March 3, 2021

Hello @DGeor.4​ and welcome to the STM32 Community =)

All HSE32 BYPASS description/definition are removed from STM32WBxx reference manuals and HAL, to be replaced by HSE32 clock input mode.

Please, mark the answer as "Best Answer" by clicking on the "Select as Best" button if it fully answered your question, this can be very helpful for Community users to find this solution more quickly.

Imen

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
DGeor.4
DGeor.4Author
Associate
March 4, 2021

Thank you for the answer.

I see in the latest version of the reference manual (RM0434 rev6), section 8.2.1, that using an external clock (previously called HSE bypass mode) has the same configuration as using a crystal. Is that correct? So all the code needs to do is enable HSEON and the MCU will automatically detect if its a crystal or an external clock?

Terms & ConditionsAccessibility statement