-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[v2.7] application booted from v3.x mcuboot uptime resets #56604
Comments
@nordicjm - any chance you could provide a fix? |
Not likely, can't determine cause |
@anangl is there a PR that needs to be ported? |
I have no idea, to be honest. I don't know what could cause such behavior. |
Assigning to @anangl and @nordic-krch it seems to be something wrong with |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
Ping on @anangl and @nordic-krch |
The issue is not actually related to mcuboot. It can be also observed in |
Fixed by #59154. |
Describe the bug
It seems that with #56528 applied to mcuboot, a 2.7-built application which uses uptime will ungracefully seem to lose it's uptime value after about 8.5 minutes, that is, the device will continue functioning but e.g. using
kernel uptime
from the shell will wrongly output an uptime value of seconds rather than 10 minutes which is wrong.To Reproduce
kernel uptime
andkernel threads
output every minute, after the 8.5 minute mark, seemingly the uptime has set to 0.Expected behavior
Uptime to continue incrementing
Impact
Showstopper, applications seemingly are unaware of the true uptime. Note that this only happens when older images e.g. 2.7 are booted from new versions of mcuboot e.g. from zephyr 3.x onwards
Environment (please complete the following information):
main
with above PR for mcuboot andv2.7-branch
for applicationThe text was updated successfully, but these errors were encountered: