2025-11-27 10:32 PM - last edited on 2025-11-28 2:01 AM by mƎALLEm
Hi there, im using Nucleo-F446RE , ST HAL and CubeMX, and im learning to configure the clock
I use HSE Bypass mode (MCO from the st-link in the nucleo), everything perfect here
In the RM i found out that, when using HSE BYPASS mode, PH1 (OSC_OU) should be left in HI-Z state
What does HI-Z means in STM32 MCUs? does it mean configuring the pin as digital input? or it means configuring the pin as analog input?
Or it depends?
When selecting HSE BYPASS MODE the chip image in the .ioc file gets set like this:
But if i try to set PH1 (OSC_OUT) as GPIO a conflict is generated, so, how can i set the state of PH1 as HI-Z?
Also, why does PH1 gets reserved and configured in the chip as OSC_OUT? is this to avoid configuring it as another thing?
And finally, what it seems very weird to me, why the clock por GPIOH is enabled when CubeMX generates the code if i cant use PH1 as a normal GPIO? (im not using any other PHx PIN)
Thanks in advance and sorry for the english, not a native speaker!
Solved! Go to Solution.
2025-12-03 8:33 PM
Ok, got it, thanks to all!
2026-05-21 2:26 AM - edited 2026-05-21 2:47 AM
Hi all,
Please refer to this thread for more details.
STM32F446RE (and other F4 part numbers) are able to make PH1 as GPIO when HSE in Bypass mode, but we recommend the users to keep it as Hi-Z as that function was not validated / tested.
2026-05-21 2:32 AM
Oh, yet another twist! :)
Thanks for the info.
JW
2026-05-21 2:33 AM
@mƎALLEm wrote:Please refer to this thread for more details.
In particular, this post.
@mƎALLEm wrote:STM32F446RE (and other F4 part numbers) are able to make PH1 as GPIO when HSE in Bypass mode
That post says that some other F4 can't do it at all