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

Developer board only: time event shows random UTC after deep reset #77

Open
RobertK66 opened this issue May 14, 2023 · 2 comments
Open
Labels
bug Something isn't working

Comments

@RobertK66
Copy link
Owner

The event sent after reset or after receiving the 'T' command should not fill the random content stored in RTC when there was no sync at all. This only occurs if there is no MRAM available (e.g. when using a developer board) and the RTC Power was not buffered by Capacitor.

@RobertK66 RobertK66 added the bug Something isn't working label May 14, 2023
@RobertK66 RobertK66 self-assigned this May 14, 2023
@RobertK66
Copy link
Owner Author

There are 2 path in init code which do not set RTC to 1.1.1001 (or a correct synced value from G-RAM):

  • if RTC oscillator is not running and not started/stable after 400ms (status -> RTC_STAT_XTAL_ERROR)
  • if RTC is running, G-RAM Checksum is ok BUT the status prior to Reset was 'Not synced' -> here we should expect a 'valid RTC' somewhere after 1.1.1001 but not Random content !!?

@RobertK66
Copy link
Owner Author

i will

  • add the Rtc status to the time event
  • init RTC to 1.1.1001 even without XTAL working

@RobertK66 RobertK66 removed their assignment Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant