Jetpack 6 L4T 36.3 - Orin Resets Clock to Unix Epoch on startup

Autonomous Machines Jetson & Embedded Systems Jetson AGX Orin
1

I am having an issue with the Orin’s after updating them all to Jetpack 6, 36.3. On a power cycle the Orins reset their clocks to Unix Epoch, when before on Jetpack 5 this never occured.

I have setup an NTP which does work, however I require the RTC when internet connectivity is not guaranteed.

I have set the time several times via the CLI, however when the computer discharges fully the clocks reset - which was never an issue two weeks ago when the ORIN’s were on Jetpack 5.

Is this a known issue/ has anyone else experienced this.

Any help would be greatly appreciated!

Thanks!

4

Hi rj.bundy,

Are you using the devkit or custom board for AGX Orin?

Do you mean the “sudo reboot” reset the time?

Please share the result of the following commands on your board.

$ timedatectl status
$ sudo hwclock --verbose

Do you have RTC battery on your board?

5

I have two jetsons with the same issue. One is a Stereolabs NX, and the other a AGX devkit.

No sudo reboot works fine when I set the time, it does not keep time when the power to the computers is cut off and then reapplied.

Yes there is a RTC battery, as this issue was never prevelant before Jetpack 6.

This is what I get from running the timedatectl and hwclock commands:

indro@robot_name:~$ timedatectl status
               Local time: Wed 1969-12-31 19:01:41 EST
           Universal time: Thu 1970-01-01 00:01:41 UTC
                 RTC time: Thu 1970-01-01 00:01:40
                Time zone: America/Toronto (EST, -0500)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no
indro@robot_name:~$ sudo hwclock --verbose
[sudo] password for indro: 
hwclock from util-linux 2.37.2
System Time: 109.040815
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 1970/01/01 00:01:49
Hw clock time : 1970/01/01 00:01:49 = 109 seconds since 1969
Time since last adjustment is 109 seconds
Calculated Hardware Clock drift is 0.000000 seconds
1969-12-31 19:01:48.745637-05:00
6

Let’s focus on the behavior of the devkit.

It is expected to get the time reset if you cut off the power since there’s no RTC battery on the devkit.

Do you connect the board to the internet?
If so, your time should get synced through network.

7

It is connected to the internet and it does get time synced through it now, however on startup it is always 1970, which never occured before the upgrade to Jetpack 6. On Jetpack 5 NTP was not required since once we set the time it would keep the time - now it resets.

Since this is on an autonomous robot the internet can not be relied on when it is operating in areas with poor or no internet connection.

8

Could you confirm the time is correct now and run sudo reboot to check the time after boot up?

Do you mean the RTC time still reset to 1970 even if you have RTC battery connected?

10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.