AGX SDK running OS 5.2, only USB3XB works

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

Please provide the following info (check/uncheck the boxes after clicking “+ Create Topic”):
Software Version
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
Linux
QNX
other

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
1.4.1.7402
other

Host Machine Version
native Ubuntu 18.04
other

I installed GNOME so I can work directly on the platform but the only signal out is XB for the HDMI and USB3XB for the USB. Not a big deal for now but I would like the rest of the USB port to work.

3

Dear @andrea_Faction,
When you connect to Tegra B( via XB HDMI port) only USB XavierB is expected to work. Could you confirm if you have connected to Tegra A(via XA1 HDMI port) and tried using USB xavierA ports?

4

if I connect XA1 and USB2XA, nothing happens, it looks like it is not detecting the monitor. I rebooted just in case, still nothing.

5

Hi @andrea_Faction ,

Could you check if any suspicious kernel message on Xavier A? Thanks.

6

I am not sure what I am looking for but I do not see anything suspicious:

Update: previous post was from TegraB. This is from TegraA via Minicom on USB2 on the host

journalctl -b | grep fail
Apr 09 19:43:13 tegra-ubuntu kernel: OF: fdt: Reserved memory: failed to reserve memory for node ‘fb0_carveout’: base 0x0000000000000000, size 0 MiB
Apr 09 19:43:13 tegra-ubuntu kernel: OF: fdt: Reserved memory: failed to reserve memory for node ‘fb0_carveout’: base 0x0000000000000000, size 0 MiB
Apr 09 19:43:13 tegra-ubuntu kernel: OF: fdt: Reserved memory: failed to reserve memory for node ‘fb1_carveout’: base 0x0000000000000000, size 0 MiB
Apr 09 19:43:13 tegra-ubuntu kernel: OF: fdt: Reserved memory: failed to reserve memory for node ‘fb1_carveout’: base 0x0000000000000000, size 0 MiB
Apr 09 19:43:13 tegra-ubuntu kernel: OF: fdt: Reserved memory: failed to reserve memory for node ‘fb2_carveout’: base 0x0000000000000000, size 0 MiB
Apr 09 19:43:13 tegra-ubuntu kernel: OF: fdt: Reserved memory: failed to reserve memory for node ‘fb2_carveout’: base 0x0000000000000000, size 0 MiB
Apr 09 19:43:13 tegra-ubuntu kernel: OF: fdt: Reserved memory: failed to reserve memory for node ‘fb3_carveout’: base 0x0000000000000000, size 0 MiB
Apr 09 19:43:13 tegra-ubuntu kernel: OF: fdt: Reserved memory: failed to reserve memory for node ‘fb3_carveout’: base 0x0000000000000000, size 0 MiB
Apr 09 19:43:13 tegra-ubuntu kernel: nvethernet 2490000.ethernet: failed to get phy reset gpio
Apr 09 19:43:13 tegra-ubuntu kernel: trusty-irq trusty:irq: trusty_irq_create_irq_mapping failed (-75)
Apr 09 19:43:13 tegra-ubuntu kernel: trusty-irq trusty:irq: failed to initialize irq 449, irq will be ignored
Apr 09 19:43:13 tegra-ubuntu kernel: mmc0: Switching to 1.8V signalling voltage failed
Apr 09 19:43:16 tegra-ubuntu [601]: failed to execute ‘/lib/udev/mtp-probe’ ‘mtp-probe /sys/devices/3610000.xhci/usb1/1-3 1 2’: No such file or directory
Apr 09 19:43:16 tegra-ubuntu [602]: failed to execute ‘/lib/udev/mtp-probe’ ‘mtp-probe /sys/devices/3610000.xhci/usb1/1-2 1 3’: No such file or directory
Apr 09 19:43:18 tegra-ubuntu sh[660]: Linux dt tree search failed!
Apr 09 19:45:29 tegra-ubuntu DUV3[897]: [ERR][dulink_remote_ops.c:463]Remote operation returned failure
Apr 09 19:45:29 tegra-ubuntu DUV3[897]: [ERR][dulink_remote_ops.c:1187]Remote operation returned failure
Apr 09 19:45:46 tegra-ubuntu systemd[1]: Dependency failed for One-time setup of encryption for encrypted home.
Apr 09 19:45:46 tegra-ubuntu systemd[1]: nv_encrypt_run_once.service: Job nv_encrypt_run_once.service/start failed with result ‘dependency’.
Apr 09 19:45:46 tegra-ubuntu systemd[1]: dev-vblkdev50.device: Job dev-vblkdev50.device/start failed with result ‘timeout’.

7

I am not able to tell if your problems are related to the messages yet. But if XB HDMI works on your side, you should know ubuntu desktop isn’t installed by default of DRIVE OS 5.2.0, right?

For you XA problems, comparing messages between XA and XB may be a good way to figure out them.

8

Well, right you are, Tegra A did not have the desktop installed it. I just installed it, all good. I did not realize Tegra A and Tegra B are completely disjoint.

9

Good to hear all clarified. Thanks.

10

BTW: I want to make sure I did this correctly: I installed Drive OS 5.2 using SDK Manager. This created two distinct Ubuntu machines, one per Xavier. Then I installed DriveWork on Xavier B and if I want to run it on Xavier A, I have to repeat the installation on that machine. Please confirm my understanding is correct and thus we should think of each Xavier as its own machine with shared hardware resources, specifically, over PCI.

11

Yes, you need to install DriveWorks to whichever Xavier DriveWorks applications run on.