2021-03-31 03:38 PM
I came across this Ethernet example:
It is giving me an issue regarding configuring HSE in bypass mode. The maximum core frequency l can get is 96MHz compared to 400 MHz in the example.
Thank you for any assistance.
Solved! Go to Solution.
2021-03-31 04:34 PM
> The maximum core frequency l can get is 96MHz compared to 400 MHz in the example.
This is a known issue. As too often with this forum, it's easier to reply again than search for the original answer.
Go to RCC parameters and select voltage scale 0. Then it will let you have 400 MHz.
> none of the ST provided board examples using BYPASS mode.
Nucleo boards use BYPASS mode (at least some of them), and all Cube examples for these boards naturally use BYPASS mode.
-- pa
2021-03-31 03:47 PM
None of the board examples use BYPASS mode, not sure the logic there.
Make sure HSE_VALUE is 25000000 in the stm32h7xx_hal_conf.h file
Use the SystemClock_Config() from
STM32Cube_FW_H7_V1.8.0\Projects\STM32H745I-DISCO\Applications\FatFs\FatFs_Shared_Device\CM7\Src\main.c
2021-03-31 04:13 PM
Thank you for replying.
You are correct about none of the ST provided board examples using BYPASS mode. I was trying to implement the user created example in the link. Your advice will set the core to 400MHz. What is your opinion on the linkerscript?
2021-03-31 04:34 PM
> The maximum core frequency l can get is 96MHz compared to 400 MHz in the example.
This is a known issue. As too often with this forum, it's easier to reply again than search for the original answer.
Go to RCC parameters and select voltage scale 0. Then it will let you have 400 MHz.
> none of the ST provided board examples using BYPASS mode.
Nucleo boards use BYPASS mode (at least some of them), and all Cube examples for these boards naturally use BYPASS mode.
-- pa
2021-04-02 01:18 AM
Clive is right:
The value assigned should have been RCC_HSE_BYPASS. Well, that's just one of countless bugs in STM32 broken bloatware.