Skip to content
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

Nucleo board Slow Code execution at power up - need to always reset #26643

Closed
NearbySolutions opened this issue Jul 3, 2020 · 2 comments
Closed
Labels
bug The issue is a bug, or the PR is fixing a bug

Comments

@NearbySolutions
Copy link

I am developing a system based on STM32 SoC using Nucleo board and found that when powering on the board the code is executing slower than normal. When i press the RESET button on the board everything come back to normal and my code is executing normally.

To investigate the issue i decided to execute the Blinking LED sample app delivered with Zephyr code and figured out that the same issue is happening also. The main loop should blink the LED every second but it's blinking a lot slower until i press the reset button. After the reset the LED blink normally.

I decided to debug it and saw that it seems to be related to the irq_unlock code which takes longer. From what i saw so far, it seems to be related to context switching taking really long to execute.

To Reproduce
Steps to reproduce the behavior:

  1. Go to the blinking LED sample folder in zephyr/samples/basic/blinky
  2. west build -p auto -b nucleo_f303re .
  3. west flash --openocd /usr/local/bin/openocd

Expected behavior
The LED on the board should blink every second.

Impact
showstopper since i always need to manually reset the board

Environment (please complete the following information):

  • OS: MacOS
  • GNU ARM Embedded
  • Last Master branch version

Additional context
Add any other context about the problem here.

@NearbySolutions NearbySolutions added the bug The issue is a bug, or the PR is fixing a bug label Jul 3, 2020
@tagunil
Copy link
Collaborator

tagunil commented Jul 5, 2020

Could you please re-test now with #26036 merged?

@NearbySolutions
Copy link
Author

Hi @tagunil it fixes the problem ! Thanks for your help on that !!
No more latency at the startup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug
Projects
None yet
Development

No branches or pull requests

2 participants