Jetson AGX Time/BIOS Time/Network Issues

Hi,

My AGX doesn’t retain its times after reboots. I think this is also causing it to not be able to use internet from host (via USB-C cable). The OS Clock sets to sometime in Jan2018 and BIOS clock sets to 200-01-01.

I am able to change the OS clock using date command. That allows Wifi to connect to internet but not via USB-C that I had multiple time after re-flashing. I am pretty sure it needs to be on right time at reboot for this which it is not.

I am NOT able to change BIOS clock using hwclock using

hwclock --systohc

or any other command. Nor does the time I set using ‘date’ retains after reboot.

Any solutions.

Cheers,
Vib

EDIT: Apparently if I try to install one of the packages from sdkmanageron host, the internet sharing is back on and stays persistent for that session. But how to make it permanent?

I don’t have a solution for you other than “normally this updates over the network via NTP during boot”. Jetsons don’t have a BIOS (embedded systems in general don’t have a BIOS…this is a desktop PC when speaking of BIOS or UEFI). I believe there is a supercap which can keep time correct for a short period, but no button battery.

Btw, incorrect time rarely has any effect on whether networking works, nor whether USB works. On the other hand, the USB device mode “synthetic” ethernet card might require extra setup on your host if you want to use this outside of flash. In a case where it doesn’t work you might want to post the output for these commands on both host and Xavier:

ifconfig
route
ping 192.168.55.1

(192.168.55.1 is the USB interface on the Xavier if the interface is running…knowing if it pings from both Xavier and host would be important clues)

Sorry, my bad. I meant system clock not BIOS clock. The network configuration is fine I can ping both host and Jetson through each other and self. My problem is regrading sharing the internet from host to Jetson. Right now I am using USB wifi module for internet (also synchronises Jetson with right time) and yes, it (wifi) doesn’t connect to internet if device is on past date.

This is from host

eno1      Link encap:Ethernet  HWaddr 50:65:f3:23:06:b3  
          inet addr:137.195.xxx.xxx  Bcast:137.195.xxx.xxx  Mask:255.255.255.192
          inet6 addr: fe80::f973:c268:2f81:2b50/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1097664 errors:0 dropped:0 overruns:0 frame:0
          TX packets:557952 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1429664079 (1.4 GB)  TX bytes:104324286 (104.3 MB)
          Interrupt:20 Memory:ef100000-ef120000 

enp0s20u5 Link encap:Ethernet  HWaddr 42:4d:54:18:cb:e8  
          inet addr:192.168.55.100  Bcast:192.168.55.255  Mask:255.255.255.0
          inet6 addr: fe80::ab5c:50c3:447e:979f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:942 errors:0 dropped:0 overruns:0 frame:0
          TX packets:130 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:75978 (75.9 KB)  TX bytes:32828 (32.8 KB)

enp0s20u5i5 Link encap:Ethernet  HWaddr 42:4d:54:18:cb:ea  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:113 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:15590 (15.5 KB)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:2434995 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2434995 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:64738832058 (64.7 GB)  TX bytes:64738832058 (64.7 GB)

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         mec-firewall2-g 0.0.0.0         UG    100    0        0 eno1
137.195.xx.xx   *               255.255.255.192 U     100    0        0 eno1
nameserve.hw.ac mec-firewall2-g 255.255.255.255 UGH   100    0        0 eno1
link-local      *               255.255.0.0     U     1000   0        0 eno1
192.168.55.0    *               255.255.255.0   U     100    0        0 enp0s20u5

PING 192.168.55.1 (192.168.55.1) 56(84) bytes of data.
64 bytes from 192.168.55.1: icmp_seq=1 ttl=64 time=0.732 ms
64 bytes from 192.168.55.1: icmp_seq=2 ttl=64 time=0.733 ms
64 bytes from 192.168.55.1: icmp_seq=3 ttl=64 time=0.742 ms

--- 192.168.55.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.732/0.735/0.742/0.031 ms

and this from jetson

eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:04:4b:cb:da:f8  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 40  

l4tbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.55.1  netmask 255.255.255.0  broadcast 192.168.55.255
        inet6 fe80::443a:81ff:febf:e4a0  prefixlen 64  scopeid 0x20<link>
        inet6 fe80::1  prefixlen 128  scopeid 0x20<link>
        ether 42:4d:54:18:cb:e9  txqueuelen 1000  (Ethernet)
        RX packets 57  bytes 10247 (10.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 42  bytes 7418 (7.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 124  bytes 9468 (9.4 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 124  bytes 9468 (9.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

rndis0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::404d:54ff:fe18:cbe9  prefixlen 64  scopeid 0x20<link>
        ether 42:4d:54:18:cb:e9  txqueuelen 1000  (Ethernet)
        RX packets 57  bytes 10247 (10.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 56  bytes 12322 (12.3 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::404d:54ff:fe18:cbeb  prefixlen 64  scopeid 0x20<link>
        ether 42:4d:54:18:cb:eb  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 84  bytes 13645 (13.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 137.195.xx.xx  netmask 255.255.252.0  broadcast 137.195.xx.xx
        inet6 fe80::8dc7:6c52:a9ff:1fd0  prefixlen 64  scopeid 0x20<link>
        ether 78:d2:94:98:54:e2  txqueuelen 1000  (Ethernet)
        RX packets 14969  bytes 4888717 (4.8 MB)
        RX errors 0  dropped 153  overruns 0  frame 0
        TX packets 53  bytes 7419 (7.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         _gateway        0.0.0.0         UG    600    0        0 wlan0
default         T-EM-331        0.0.0.0         UG    32766  0        0 l4tbr0
137.195.xx.xx   0.0.0.0         255.255.252.0   U     600    0        0 wlan0
link-local      0.0.0.0         255.255.0.0     U     1000   0        0 l4tbr0
192.168.55.0    0.0.0.0         255.255.255.0   U     0      0        0 l4tbr0

PING 192.168.55.1 (192.168.55.1) 56(84) bytes of data.
64 bytes from 192.168.55.1: icmp_seq=1 ttl=64 time=0.135 ms
64 bytes from 192.168.55.1: icmp_seq=2 ttl=64 time=0.226 ms
64 bytes from 192.168.55.1: icmp_seq=3 ttl=64 time=0.163 ms

--- 192.168.55.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2047ms
rtt min/avg/max/mdev = 0.135/0.174/0.226/0.041 ms

Just to recap some information, the wired eth0 has no address and won’t be used. This won’t be able to update via NTP, but other network might. The 192.168.55.x address requires the USB “fake” ethernet to be connected to the host. For the Jetson to update NTP through this connection the host itself would need to be told to all bridging from this interface to the internet through the host’s eno1 interface. The host calls the Jetson USB interface enp0s20u5.

If the host does not allow bridging (or sharing/forwarding) of eno1 by enp0s20u5, then NTP will fail. Have you set your host to permanently allow enp0s20u5 to access the internet? The default would probably be “no”, so there will be some sort of network configuration tool to allow that access (I’m not sure which interface tool…I’m using a Fedora host and actual separate router).

The actual clock has only a super capacitor backing it up, and not a battery. There might be a way to create a backup battery scheme for that clock, but I’ve never done so and don’t know what would be needed.