8 years, 11 months ago.

Something's not right.

Why does it take 10 seconds to start code execution after reset on my Nucleo F401 with the latest mbed library? An older version does not have this problem. Thanks.

1 Answer

8 years, 11 months ago.

Do you have the top part connected to it?

Problem is that normally top part delivers an 8MHz clock. If that isn't available, it will look for a crystal. If that isn't available, it will use its internal oscillator.

Why it takes 10 second: Somewhere in the last few months an update has happened with changed the timeouts on that from the extremely long 500ms (for an MCU thats eternity) to the ridiculously long 5000ms (5 seconds, and that twice, so there you got your 10 seconds). And no one seems to be intent on fixing it.

Accepted Answer

Further to Erik's answer please see short discussion we had a while ago with a work around https://developer.mbed.org/questions/54160/Start-up-time-Nucleo-F411RE/?c=18538 Regards

posted by Martin Simpson 27 Aug 2015