Jetson Xavier will not boot - cannot connect to tty or HDMI

I cannot connect my Jetson Xavier NX to a display using either tty or HDMI. If I connect with the Micro USB I can see it listed in system_profiler (OSX) or with lsusb but I can’t actually connect to the device. I have a flashed SD card.

Actually I think the issue is that it won’t boot. If I check on lsusb it looks like It is in recovery mode as I get an ID 0955:7e19 NVIDIA Corp. APX. Is there any way to force it into setup mode?

If the system is fully booted, then the micro-USB can emulate certain devices, e.g., a virtual network adapter or a virtual mass storage device. The presence of the 0955:7e19 could indicate recovery mode, but it can also indicate a fully booted system due to the custom emulated devices.

If you monitor your PC via command “dmesg --follow”, and then connect the powered up NX’s micro-USB, what do you see in the dmesg log? Once connected, from the host PC side, does “ping” succeed?

FYI, forcing recovery mode is done by shorting the recovery mode pins (one is the actual pin, the other is just ground) while either powering up or resetting power.

thanks for getting back

'dmesg -follow` returns with

[ 6405.407336] usb 3-2: new high-speed USB device number 7 using xhci_hcd
[ 6405.781761] usb 3-2: New USB device found, idVendor=0955, idProduct=7e19, bcdDevice= 1.02
[ 6405.781767] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6405.781838] usb 3-2: Product: APX
[ 6405.781842] usb 3-2: Manufacturer: NVIDIA Corp.

`ping’ does not succeed.

This might be in recovery mode. When connected what do you see from “lsblk -f”? I am curious if a new block device shows up.

lsblk -f
NAME   FSTYPE   LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0  squashfs                                                  0   100% /snap/core18/1880
loop1  squashfs                                                  0   100% /snap/gnome-3-34-1804/36
loop2  squashfs                                                  0   100% /snap/gtk-common-themes/1506
loop3  squashfs                                                  0   100% /snap/snap-store/467
loop4  squashfs                                                  0   100% /snap/snapd/8542
loop5  squashfs                                                  0   100% /snap/core18/1885
loop6  squashfs                                                  0   100% /snap/snapd/8790
├─sda1 vfat           9D2E-F55E                               511M     0% /boot/efi
└─sda5 ext4           69eff245-072d-4fb7-8b5e-a1ae116690ff   11.2G    36% /

i have a 500GB samsung SSD attached and a 128GB SD Card. I don’t think the SD card is being read.

Assuming the lsblk -f is from the host PC with the Jetson’s micro-B USB cable connected, then indeed the Jetson’s normal sample mass storage device emulation is not showing up. This would be consistent with either being in recovery mode, or optionally a failed boot.

…for this above, are you saying these also do not show up on the host PC with lsblk -f? I too did not see these on your lsblk -f, and if the PC cannot see these devices, then any copy to the devices would also fail even if the devices are otherwise functional. Can you give more details about what you see from the host PC for those devices?