-
Notifications
You must be signed in to change notification settings - Fork 3k
STM32F4 set HSE timeout value to 100ms #4422
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
/morph test |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputExample Build failed! |
Please restart morph test as error was not linked to the PR |
Will do after we generate rc2 (lot of PR are in the queue at the moment) |
It does not work for me neither. I am using a NUCLEO-F401RE with default board configuration and I have made the change that you propose in the config file "stm32f4xx_hal_conf.h". #define HSE_STARTUP_TIMEOUT 100U /*!< Time out for HSE start up, in ms */ #define LSE_STARTUP_TIMEOUT 100U /*!< Time out for LSE start up, in ms */ I have tried with mbed_122 version and it works properly, but, for instance, if I update to mbed_142 or mbed_144 the board does not start to work until 10 seconds. Is there a way to solve it? Thanks in advance. |
@sad948 |
@jeromecoutant
If I download to the board this example with the mbed_122 version it starts to work almost instantly, but when I do it with mbed_142 or mbed_144 it takes 10 seconds to start working. Is there a way to solve it? Thanks in advance. |
yes, you have to apply this pull request.... |
bump :-) |
As soon as 5.5.1 CI finished, all needs: CI will be queued |
/morph test |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
Description
HSE timeout value is set to 100ms
This is aligned with official ST cube since v1.11.0
This fix #1096
Status
READY