I’ve learned after reading lots of date-time issues about the RTC clock and it’s batteries, that:
By default, AGX Dev Kit has a RTC battery, called supercapacitor or C512. Normally it should long for weeks.
That a 2pin CMOS battery can be used, just as a backup.
Is that correct?
If I disconnect even a minute the AGX loose it’s time. I need desperately internet access to get ntp to maintain time and don’t comeback to 1970. This no only happens with one agx , it happens with 3 AGX we’ve got.
I notice this issue happens to a lot of people, and to all xavier I’ve tested. No matter what Jetpack (4.4 to 5.1) I use.
Had the same issue, The battery drains pretty quick and the clock drifts away. Why don’t you try to make an NTP server with a GPS or so source if internet is not always available? (depends on the application) if not anything makes life lot easier when parsing logfiles :D
In any case , this is not the solution for a problem with the rtc clock. Every computer I’ve bought in my life keep the clock for a long long time. Every embedded device I bought too. But an Nvidia product of thousand dollars can’t? I mean,Ive got 4 Xavier AGX, if the failure is confirmed by Nvidia, I can assure this is not a bug or issue. It’s a design problem. Hard to digest and understand.
With the price tag is awful that: I have to learn and configure lots of things , buying a gps I shouldn’t need, and dedicate time and effort to implement it and maintain.
[ 2.919986] kernel: tegra_rtc c2a0000.rtc: registered as rtc1
[ 2.922877] kernel: tegra_rtc c2a0000.rtc: setting system clock to 1970-01-01T00:00:29 UTC (29)
[ 2.930866] kernel: tegra_rtc c2a0000.rtc: Tegra internal Real Time Clock