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.
You should check if C512 is mounted on your board. It is not super tiny as below showing.
If it is not mounted, the following backup cells may be attached to this pin:
Super Capacitor (gold cap, double layer electrolytic)
Standard capacitors (tantalum)
Rechargeable Lithium Manganese cells
the top of the battery (finally is this a battery or a capacitor?) . By the way, I thought the voltage of the top of the battery and the top “holder” that is on it would be the same.
Result of measurement:
2.9 V
When I disconnect power, it goes to 0 V in 30 seconds. :S
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
My application doesn’t requires internet, and has not access to it while is making inferences - It’s in a vehicle -. Do I need 4G because jetson RTC battery is a joke?
cheers,
it is super cheap because you don’t need anything like RTK,
for simpler things that don’t mind a slight drift we even send GPS over CAN so our onboard edge nodes can correct their internal clocks and have time coherent internal logs etc.
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