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

RobertK66 / obc_1769_core

Implements hardware abstractions and Layer2(3) modules for usage of the OBC hardware in cubesat projects

GNU General Public License v3.0

1 stars 1 forks source link

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

Open RobertK66 opened 1 year ago

RobertK66 commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

i will

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