Aurix releasing ownership of GMSL

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

We have been having an issue where our cameras would just drop out suddenly and throw either IOCTL 121 or 79. We noticed that at the exact same time as the camera cutouts, we see the following messages in the aurix console:

Releasing ownership for Camera Group: 0 from Tegra: 0
Releasing ownership for Camera Group: 2 from Tegra: 0
Releasing ownership for Camera Group: 1 from Tegra: 0

Any idea what would cause the aurix to release ownership of the cameras?

nvidia@tegra-ubuntu:/usr/local/driveworks/bin$ sudo /bin/bash /etc/systemd/scripts/nv_aurix_check_fw.sh -auto_update
starting Aurix FW checking...
Checking arguments...
No_Response_From_Aurix
--------------------------------------------------------------------
!!! IMPORTANT INFORMATION BELOW REGARDING Aurix FW (PLEASE READ) !!!

No response from Aurix FW. It seems
vlan iface not configured properly
Please check your nv_tacp_init systemd service

THIS MESSAGE WILL CONTINUE TO BE SHOWN UNTIL ACTION MENTIONED IS TAKEN
With action taken, this script will be muted and not shown again
----------------------------------------------------------------------

nvidia@tegra-ubuntu:~$ sudo systemctl status nv_tacp_init.service
● nv_tacp_init.service - Initialization of TACP
   Loaded: loaded (/lib/systemd/system/nv_tacp_init.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Fri 2019-09-27 09:11:28 PDT; 15min ago
 Main PID: 1084 (code=exited, status=0/SUCCESS)

Sep 27 09:11:26 tegra-ubuntu bash[1084]: Initialize Tegra to Aurix communication protocol...
Sep 27 09:11:26 tegra-ubuntu bash[1084]: removing any existing tacp config.
Sep 27 09:11:26 tegra-ubuntu bash[1084]: trying VLAN interface first
Sep 27 09:11:26 tegra-ubuntu bash[1084]: Creating VLAN iface eth0.200
Sep 27 09:11:26 tegra-ubuntu bash[1084]: Setting ip 10.42.0.28 to eth0.200
Sep 27 09:11:27 tegra-ubuntu bash[1084]: communication over vlan interface passed. Continuing with vlan interface
Sep 27 09:11:27 tegra-ubuntu bash[1084]: link /etc/tacp/tacp.cfg --> /etc/tacp/tacp_vlan.cfg
Sep 27 09:11:27 tegra-ubuntu bash[1084]: Creating VLAN iface eth0.200
Sep 27 09:11:27 tegra-ubuntu bash[1084]: Setting ip 10.42.0.28 to eth0.200
Sep 27 09:11:28 tegra-ubuntu systemd[1]: Started Initialization of TACP.

nvidia@tegra-ubuntu:~$ ifconfig eth0.200
eth0.200  Link encap:Ethernet  HWaddr 00:04:4b:af:77:05  
          inet addr:10.42.0.28  Bcast:10.42.0.255  Mask:255.255.255.0
          inet6 addr: fe80::204:4bff:feaf:7705/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1428  Metric:1
          RX packets:500 errors:0 dropped:0 overruns:0 frame:0
          TX packets:652 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:24658 (24.6 KB)  TX bytes:42202 (42.2 KB)

Not sure if that matters…

2

Ok, it looks like the issue is we were running

sudo dhclient

and it was killing other connections as well.

We basically cleared all systemd/network/* files and only have one file:

nvidia@tegra-ubuntu:/etc/systemd/network$ cat 99-nv_enp4s0_default.network 
[Match]
Name=enp*s0

[Network]
DHCP=ipv4

hopefully that helps others.

3

Dear matthew.jones,

Could you please let me what version of DRIVE Software are you using?
Maybe 9.0 and SDK version is 5.1.0.2?

Could you please help to check if you can connect Aurix via minicom tool?
[url]DRIVE OS Linux