-
Notifications
You must be signed in to change notification settings - Fork 2
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
Real time clock seems slow #14
Comments
Hi, How do you measure time? If you compare it to host time, it is expected anyway. Those simulations are not real-time, so virtual time should be used. |
I understand. Thanks. |
This is to be checked. If other timer than RTC is in use and simulation accuracy is set to enough precision, then virtual time should be reported correctly. |
I'm using https://docs.rs/embassy-time/latest/embassy_time/struct.Instant.html which apparently does NOT use the RTC. |
Hi, maybe you have a log or firmware with visible RTC slowness. It will be easier to debug :) |
I think this is unfixable because the simulation is not 1:1 time. So, feel free to close it as "won't fix". p.s. If you want, I can give you the latest *.bin for my clock app with instructions how to set and display seconds and you can watch it drift. The emulation runs about 1/2 the speed of real time. |
Greetings. It's working great and is even now useable. Here are some minor issues that I notice:
It gets its time from the real-time clock that tells how long the device has been running. That seems to be about 5 seconds per minute slow.
Thanks for your work on this project.
The text was updated successfully, but these errors were encountered: