Aurix - no access, failed to find flashing SDK

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

Hi,

SW Version: DRIVE-V5.1.6-E3550-EB-Aurix-With3LSS-ForHyperion-StepA-3.05.04

I have rebooted the unit and i get black screen from all the hdmi outputs, also i don’t have ssh connection to the unit.
I am able to connect to minicom via usb connected to the “debug” usb port and i am able to see basic shell commands.

I am getting video output via “XB” hdmi port and it looks like it is the output for xavier B device, i can’t get a valid network ip , it seems that networkmanger.service is not running.

So the question is how do I start the “first” device? and how can we flash it ?
I managed to set the device in recovery mode but i still can’t find the correct sdk via the sdk manager tool.

Thanks for your help

3

Dear @adi4,
As I understand, you seem to have issue with accessing Tegra A.
Are you able to access Tegra A via minicom serial console?
What is the current DRIVE SW version installed on target?
what is the output of lsusb on host when you connect target and host via USB cable?

4

Hi @SivaRamaKrishnaNV,

Thank you for the quick response. Here is the info:

  • This is what i see when running version command on minicom SW Version: DRIVE-V5.1.6-E3550-EB-Aurix-With3LSS-ForHyperion-StepA-3.05.04
  • The output of lsusb: Bus 001 Device 114: ID 0955:7019 NVidia Corp
  • I don’t know how to access a specific Tegra

Thanks,
Adi

5

Dear @adi4,
Please confirm usb cable is connected between host and debug port of target?
If so, you should be able to access target from host using minicom.

Please run tegrarecovery x1 off & tegrareset x1 & tegrarecovery x2 off & tegrareset x2 commands on Aurix console.

Please use sudo minicom -D /dev/ttyUSB2 to accessTegraA and sudo minicom -D /dev/ttyUSB6 to access TegraB from host

7

@SivaRamaKrishnaNV for some reason, my colleague response was flagged. Can you please help us with the current state?

8

Dear @adi4,

  • Check the DRIVE OS version on Tegra using cat /etc/nvidia/version-ubuntu-rootfs.txt.
  • Is tegra connected to internet? If so, please share connection diagram and ifconfig output on target.
  • Try connecting Tegra A from Tegra B via ssh nvidia@10.42.0.28

can’t find the correct sdk via the sdk manager tool.

Could you share the list of DRIVE releases you see when you select DRIVE AGX platform in UI?

9

Dear @SivaRamaKrishnaNV ,

We realized that we don’t have Drive product option in the SDK manager. Yesterday we applied to get this product category.
We didn’t get this confirmed yet.

In addition:

  • Drive OS version: 5.1.6.1-16902563
  • We can’t ping to Tegra A (10.42.0.28) from Tegra B (Getting FROM 10.42.0.29 icmp_seq=1 Destination Host Unreachable)
  • We connect the Tegra to the internet via port 10GbE2, but we still don’t have internet connection
  • ifconfig output from TegraB:
nvidia@tegra-ubuntu:~$ ifconfig 
can0: flags=193<UP,RUNNING,NOARP>  mtu 16
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 10  (UNSPEC)
        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 106  

can1: flags=193<UP,RUNNING,NOARP>  mtu 16
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 10  (UNSPEC)
        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 107  

enp3s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.0.11  netmask 255.255.255.0  broadcast 192.168.0.255
        ether 00:04:4b:f6:72:d7  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

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::204:4bff:fef6:72d4  prefixlen 64  scopeid 0x20<link>
        ether 00:04:4b:f6:72:d4  txqueuelen 1000  (Ethernet)
        RX packets 14722  bytes 706896 (706.8 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 257194  bytes 16746307 (16.7 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 84  

eth0.200: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.42.0.29  netmask 255.255.255.0  broadcast 10.42.0.255
        inet6 fe80::204:4bff:fef6:72d4  prefixlen 64  scopeid 0x20<link>
        ether 00:04:4b:f6:72:d4  txqueuelen 1000  (Ethernet)
        RX packets 14719  bytes 706722 (706.7 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 72037  bytes 3035434 (3.0 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

hv0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.12.4  netmask 255.255.255.0  broadcast 192.168.12.255
        inet6 fe80::886:4cff:fef8:e900  prefixlen 64  scopeid 0x20<link>
        ether 0a:86:4c:f8:e9:00  txqueuelen 1000  (Ethernet)
        RX packets 4  bytes 292 (292.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 179  bytes 16688 (16.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  

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 1000  (Local Loopback)
        RX packets 108207  bytes 8275965 (8.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 108207  bytes 8275965 (8.2 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Many thanks for your support

10

Dear @adi4,
Do you still have this issue? Did you get Approval to DRIVE AGX Developer program?