Jetson AGX failing during recovery flashing

Hi, my Jetson AGX has been failing with the following log when trying to re-flash. I’ve attempted previous advice here, it’s however not been suitable for my issue. My device appears to be breaking during the same stage each time.

14:26:13 INFO: File System and OS - target_image: Removing QEMU binary from rootfs
14:26:13 INFO: File System and OS - target_image: Removing stashed Debian packages from rootfs
14:26:13 INFO: File System and OS - target_image: L4T BSP package installation completed!
14:26:13 INFO: File System and OS - target_image: Rename ubuntu.desktop --> ux-ubuntu.desktop
14:26:13 INFO: File System and OS - target_image: Disable the ondemand service by changing the runlevels to 'K'
14:26:13 INFO: File System and OS - target_image: Success!
14:26:13 INFO: File System and OS - target_image: command finished successfully
14:26:13 INFO: Start to check if only one device connected...
14:26:13 DEBUG: running command < true >
14:26:14 INFO: command finished successfully
14:26:14 DEBUG: running command < [ `lsusb | grep -c "0955:"` -ne 1 ] >
14:26:14 DEBUG: command terminated with error
14:26:14 INFO: Only one NVIDIA device detected, as expected.
14:26:14 INFO: Start to check if in device recovery mode...
14:26:14 DEBUG: running command < true >
14:26:14 INFO: command finished successfully
14:26:14 DEBUG: running command < lsusb | grep 0955:7020 >
14:26:14 DEBUG: command terminated with error
14:26:14 INFO: Jetson device is in recovery mode.
14:26:14 INFO: Start to check if the right device connected...
14:26:14 DEBUG: running command < true >
14:26:14 INFO: command finished successfully
14:26:14 DEBUG: running command < lsusb | grep -E '0955:7019|0955:7819' >
14:26:14 INFO: Bus 001 Device 004: ID 0955:7019 NVidia Corp.
14:26:14 INFO: command finished successfully
14:26:14 INFO: Verified, 0955:7019 or 0955:7819 detected in recovery mode.
14:26:14 DEBUG: running command < true >
14:26:14 INFO: command finished successfully
14:26:14 DEBUG: running command < /tmp/device_mode_host_setup.sh >
14:26:14 INFO: Found route default enp0s3, setting up device mode
14:26:14 INFO: net.ipv4.ip_forward = 1
14:26:14 INFO: Device mode on host successfully set with DNS 8.8.8.8!
14:26:14 INFO: command finished successfully
14:26:14 DEBUG: running command < true >
14:26:14 INFO: command finished successfully
14:26:14 DEBUG: Flash Jetson AGX Xavier - flash: using adapter to install NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS to /home/damian/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_AGX_XAVIER_TARGETS
14:26:14 INFO: Flash Jetson AGX Xavier - flash: sudo ./nvautoflash.sh
14:26:14 INFO: Flash Jetson AGX Xavier - flash: *** Checking ONLINE mode ... OK.
14:26:14 INFO: Flash Jetson AGX Xavier - flash: *** Checking target board connection ... 1 connections found.
14:26:14 ERROR: Flash Jetson AGX Xavier - flash: command terminated with error
14:26:14 SUMMARY: DateTime Target Setup - target: Depends on failed component

I’m using Ubuntu 18.04 on Virtualbox with 10gig RAM, I noticed at the same time as the error, I get a disconnected device ping (however, this quickly returns back to connected). I believe that my USB-C connector may be the issue, however I cannot find any advice online as to the minimal requirements for the cable used for flashing.

I’ve been recovery flashing as my device has encountered the same issues as found here, could they potentially be related to the recovery flashing issue?

When attempting to run - sudo ./flash.sh jetson-xavier mmcblk0p1 // For Jetson Xavier for manual flash

I encounter an issue of “probing the target board failed”, even though the connection appears to be fine when looking at
lsusb (I have an ID 0955:7019 Nvidia Corp for the device)

Could somebody help me understand why my device is refusing to flash in recovery mode?

You need to use Ubuntu 18.04 on the x86 Linux host not on the VM.

hello damian.bemben,

it usually the communication issue through VM, please try with native ubuntuOS to flash your target.

That ended up solving my issue, however I read some articles (JetPack 3.0/3.1 Install with a VM) that seemed to suggest there is a possibility flashing via VM.

In the end putting in a dual-boot solved my issues however, and was far easier. So i’d recommend where possible to dual-boot with Ubuntu 18.04 and flash jetson that way.

You can flash with a VM if you can forward the USB device of the jetson from the host.
This is really only possible on VMWare Workstation, not other virtualization solutions (e g, neither Hyper-V nor Fusion nor KVM nor VirtualBox seem to support this feature.)
And even on VMWare Workstation, you have to set up the forwarding once the device is in flash mode, which is a PITA.
Dual-booting is much more reliable, if you don’t have hardware enough to just keep a Linux host around for general purpose development.