CubeL4, HAL_RCC_OscConfig leaves HSE_ON set even if HSERDY is not set within timeout delay

[MVoge.4]

Dear all,

I just found out that the CubeL4 function HAL_RCC_OscConfig() does not reset the HSEON bit (in the RCC, CR-register) in case that the HSE does not start and the function creates a timeout.

I am just facing an issue where the HSE-crystal does not start reliably over temperature (32MHz, oscillation safety factor is met, load capacitors are correct - reviewed and measured by quartz manufacturer, 100ms startup timeout). Retries, however, help - but only if HSEON is cleared again. Since this is not done by HAL_RCC_OscConfig() I have to turn off HSEON manually.

So I would like to ask if this behavior can be fixed in future versions? Or is this a intended behavior?

Best regards

Markus

PS: Here is further information:

CPU: STM32L496QEIx

CubeL4: Version 1.16

[Jacob WOODRUFF]

Hi All,

This question was routed to our online support team for direct support from our specialist team. Any other customers can submit cases directly to us on the ST.com website.

Regards,

Jake

ST Support