Skip to content

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

Merged
merged 1 commit into from
Jun 26, 2017

Conversation

jeromecoutant
Copy link
Collaborator

Description

HSE timeout value is set to 100ms
This is aligned with official ST cube since v1.11.0

This fix #1096

Status

READY

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 5, 2017

/morph test

@mbed-bot
Copy link

mbed-bot commented Jun 5, 2017

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 450

Example Build failed!

@jeromecoutant
Copy link
Collaborator Author

Please restart morph test as error was not linked to the PR

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 9, 2017

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)

@sad948
Copy link

sad948 commented Jun 14, 2017

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.

@jeromecoutant
Copy link
Collaborator Author

@sad948
please raise a new issue with the code you are executing
There should be another problem as this patch.
Thx

@sad948
Copy link

sad948 commented Jun 15, 2017

@jeromecoutant
The code I am using is the example of the blinking led, but you can try with any other example in the mbed online compiler and the same issue always happens.

#include "mbed.h"

DigitalOut myled(LED1);

int main() {
while(1) {
myled = 1; // LED is ON
wait(0.2); // 200 ms
myled = 0; // LED is OFF
wait(1.0); // 1 sec
}
}

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.

@jeromecoutant
Copy link
Collaborator Author

Is there a way to solve it?

yes, you have to apply this pull request....

@theotherjimmy
Copy link
Contributor

@adbridge @0xc0170 @sg- This is not being ironed into our waffle. It's going to need a re-run of morph test when we have room in the pipeline.

@jeromecoutant
Copy link
Collaborator Author

bump :-)

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 21, 2017

bump :-)

As soon as 5.5.1 CI finished, all needs: CI will be queued

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 26, 2017

/morph test

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 633

All builds and test passed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

STM32F4: HSE timeout increased from 0.5s to 5s, needs 10seconds to fallback to HSI
7 participants