TX2 Flash Jetson OS error

Trying to install Jetpack 4.4 on the Tx2. The flash OS task fails at 0%. Can somebody direct me to which logs should I check and debug this issue?

Flash Jetson TX2: Failed to execute commands with GenericInstaller

  • 10:23:50 INFO: null
  • 10:23:55 INFO: Automatic trying to flash the target device with Manual Flash option…
  • 10:23:56 INFO: CUDA Toolkit for L4T: start to download h.ttps://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.4-ga/JETPACK_44_b186/cuda-repo-l4t-10-2-local-10.2.89_1.0-1_arm64.deb to /home/sakethk98/Downloads/nvidia/sdkm_downloads/cuda-repo-l4t-10-2-local-10.2.89_1.0-1_arm64.deb
  • 10:23:56 INFO: OpenCV on Target: start to download h.ttps://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.4-ga/JETPACK_44_b186/OpenCV-4.1.1-2-gd5a58aa75-aarch64-libs.deb to /home/sakethk98/Downloads/nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-aarch64-libs.deb
  • 10:23:56 INFO: OpenCV on Target: start to download h.ttps://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.4-ga/JETPACK_44_b186/OpenCV-4.1.1-2-gd5a58aa75-aarch64-dev.deb to /home/sakethk98/Downloads/nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-aarch64-dev.deb
  • 10:23:56 INFO: OpenCV on Target: start to download h.ttps://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.4-ga/JETPACK_44_b186/OpenCV-4.1.1-2-gd5a58aa75-aarch64-licenses.deb to /home/sakethk98/Downloads/nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-aarch64-licenses.deb
  • 10:23:56 INFO: OpenCV on Target: start to download h.ttps://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.4-ga/JETPACK_44_b186/OpenCV-4.1.1-2-gd5a58aa75-aarch64-python.deb to /home/sakethk98/Downloads/nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-aarch64-python.deb
  • 10:23:56 INFO: OpenCV on Target: start to download h.ttps://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.4-ga/JETPACK_44_b186/OpenCV-4.1.1-2-gd5a58aa75-aarch64-samples.deb to /home/sakethk98/Downloads/nvidia/sdkm_downloads/OpenCV-4.1.1-2-gd5a58aa75-aarch64-samples.deb
  • 10:23:56 INFO: Only one NVIDIA device detected, as expected.
  • 10:23:56 INFO: Jetson device is in recovery mode.
  • 10:23:56 INFO: Bus 001 Device 009: ID 0955:7c18 NVidia Corp.
  • 10:23:56 INFO: command finished successfully
  • 10:23:56 INFO: Verified, 0955:7c18 detected in recovery mode.
  • 10:23:56 INFO: Device Mode Host Setup in Flash: [ Disk Avail:166.31 GB ]
  • 10:23:56 INFO: Device Mode Host Setup in Flash: Using GenericInstaller to Install NV_DEVICE_MODE_SETUP_IMAGE_COMP
  • 10:23:56 INFO: Device Mode Host Setup in Flash: change working directory to /home/sakethk98/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_TX2
  • 10:23:56 INFO: Device Mode Host Setup in Flash: [ Component Install Started ]
  • 10:23:56 INFO: Device Mode Host Setup in Flash: current working directory is /home/sakethk98/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_TX2
  • 10:23:56 INFO: Device Mode Host Setup in Flash: exec_command [host]:
  • 10:23:56 INFO: Device Mode Host Setup in Flash: **********************
  • 10:23:56 INFO: Device Mode Host Setup in Flash: #!/bin/bash
  • 10:23:56 INFO: Device Mode Host Setup in Flash: set -e
  • 10:23:56 INFO: Device Mode Host Setup in Flash: set +e
  • 10:23:56 INFO: Device Mode Host Setup in Flash: eth_port_name=$(ip route show default | awk ‘/default via/ {print $5; exit}’)
  • 10:23:56 INFO: Device Mode Host Setup in Flash: if [[ $eth_port_name == ‘’ ]]; then
  • 10:23:56 INFO: Device Mode Host Setup in Flash: echo ‘Can not found route default $eth_port_name, device mode setup failed!’
  • 10:23:56 INFO: Device Mode Host Setup in Flash: exit 0
  • 10:23:56 INFO: Device Mode Host Setup in Flash: fi
  • 10:23:56 INFO: Device Mode Host Setup in Flash: echo ‘Found route default’ $eth_port_name’, setting up device mode’
  • 10:23:56 INFO: Device Mode Host Setup in Flash: setup_t=‘192.168.55.0/24’
  • 10:23:56 INFO: Device Mode Host Setup in Flash: sudo iptables -t nat -A POSTROUTING -s $setup_t -o $eth_port_name -j MASQUERADE
  • 10:23:56 INFO: Device Mode Host Setup in Flash: sudo iptables -A FORWARD -s $setup_t -o $eth_port_name -j ACCEPT
  • 10:23:56 INFO: Device Mode Host Setup in Flash: sudo iptables -A FORWARD -d $setup_t -m state --state ESTABLISHED,RELATED -i $eth_port_name -j ACCEPT
  • 10:23:56 INFO: Device Mode Host Setup in Flash: sudo sysctl -w net.ipv4.ip_forward=1
  • 10:23:56 INFO: Device Mode Host Setup in Flash: check_google_dns=$(dig @8.8.8.8 nvidia.com || true)
  • 10:23:56 INFO: Device Mode Host Setup in Flash: if [[ $check_google_dns == ‘Got answer’ ]]; then
  • 10:23:56 INFO: Device Mode Host Setup in Flash: echo ‘Device mode on host successfuly set with DNS 8.8.8.8!’
  • 10:23:56 INFO: Device Mode Host Setup in Flash: exit 0
  • 10:23:56 INFO: Device Mode Host Setup in Flash: else
  • 10:23:56 INFO: Device Mode Host Setup in Flash: echo ‘Default google DNS is not working, trying to find a valid server in local host settings!’
  • 10:23:56 INFO: Device Mode Host Setup in Flash: dns_list=$(nmcli -t device show eth_port_name | grep 'DNS' | grep -o '[^:]*')
  • 10:23:56 INFO: Device Mode Host Setup in Flash: for dns in $dns_list; do
  • 10:23:56 INFO: Device Mode Host Setup in Flash: check_dns=$(dig @$dns nvidia.com || true)
  • 10:23:56 INFO: Device Mode Host Setup in Flash: if [[ $check_dns == ‘Got answer’ ]]; then
  • 10:23:56 INFO: Device Mode Host Setup in Flash: sudo iptables -t nat -A PREROUTING -p tcp -d 8.8.8.8 --dport 53 -j DNAT --to-destination $dns
  • 10:23:56 INFO: Device Mode Host Setup in Flash: sudo iptables -t nat -A PREROUTING -p udp -d 8.8.8.8 --dport 53 -j DNAT --to-destination $dns
  • 10:23:56 INFO: Device Mode Host Setup in Flash: echo ‘Device mode on host successfuly set with DNS’ $dns’!’
  • 10:23:56 INFO: Device Mode Host Setup in Flash: exit 0
  • 10:23:56 INFO: Device Mode Host Setup in Flash: fi
  • 10:23:56 INFO: Device Mode Host Setup in Flash: done
  • 10:23:56 INFO: Device Mode Host Setup in Flash: echo ‘Can not found a valid DNS server, device mode setup failed!’
  • 10:23:56 INFO: Device Mode Host Setup in Flash: echo ‘If needed to use device mode, please change the target default dns to a valid server by following the steps in release note.’
  • 10:23:56 INFO: Device Mode Host Setup in Flash: exit 0
  • 10:23:56 INFO: Device Mode Host Setup in Flash: fi
  • 10:23:56 INFO: Device Mode Host Setup in Flash: **********************
  • 10:23:56 INFO: Device Mode Host Setup in Flash: exec_command: /tmp/tmp_NV_DEVICE_MODE_SETUP_IMAGE_COMP.sh
  • 10:23:56 INFO: Device Mode Host Setup in Flash: Found route default wlp3s0, setting up device mode
  • 10:23:56 INFO: Device Mode Host Setup in Flash: [host] [sudo] password for sakethk98:
  • 10:23:56 INFO: Device Mode Host Setup in Flash:
  • 10:23:56 INFO: Device Mode Host Setup in Flash: net.ipv4.ip_forward = 1
  • 10:23:56 INFO: Device Mode Host Setup in Flash: Device mode on host successfuly set with DNS 8.8.8.8!
  • 10:23:56 INFO: Device Mode Host Setup in Flash: [ Component Install Finished Successfully ]
  • 10:23:56 INFO: Device Mode Host Setup in Flash: [ 8.00 KB released. Disk Avail: 166.31 GB ]
  • 10:23:56 INFO: Device Mode Host Setup in Flash: [ NV_DEVICE_MODE_SETUP_IMAGE_COMP Install took 0s ]
  • 10:23:56 INFO: Device Mode Host Setup in Flash: command finished successfully
  • 10:23:56 INFO: Flash Jetson TX2: [ Disk Avail:166.31 GB ]
  • 10:23:56 INFO: Flash Jetson TX2: Using GenericInstaller to Install NV_L4T_FLASH_TX2_WITH_OS_IMAGE_COMP
  • 10:23:56 INFO: Flash Jetson TX2: change working directory to /home/sakethk98/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_TX2/Linux_for_Tegra
  • 10:23:56 INFO: Flash Jetson TX2: [ Component Install Started ]
  • 10:23:56 INFO: Flash Jetson TX2: current working directory is /home/sakethk98/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_TX2/Linux_for_Tegra
  • 10:23:56 INFO: Flash Jetson TX2: exec_command [host]:
  • 10:23:56 INFO: Flash Jetson TX2: **********************
  • 10:23:56 INFO: Flash Jetson TX2: #!/bin/bash
  • 10:23:56 INFO: Flash Jetson TX2: set -e
  • 10:23:56 INFO: Flash Jetson TX2: set -e
  • 10:23:56 INFO: Flash Jetson TX2: if [ -e ./bootloader/system.img ]; then
  • 10:23:56 INFO: Flash Jetson TX2: echo sudo ./flash.sh --no-systemimg jetson-tx2 mmcblk0p1
  • 10:23:56 INFO: Flash Jetson TX2: sudo ./flash.sh --no-systemimg jetson-tx2 mmcblk0p1
  • 10:23:56 INFO: Flash Jetson TX2: else
  • 10:23:56 INFO: Flash Jetson TX2: echo sudo ./flash.sh jetson-tx2 mmcblk0p1
  • 10:23:56 INFO: Flash Jetson TX2: sudo ./flash.sh jetson-tx2 mmcblk0p1
  • 10:23:56 INFO: Flash Jetson TX2: fi
  • 10:23:56 INFO: Flash Jetson TX2: sleep 20
  • 10:23:56 INFO: Flash Jetson TX2: **********************
  • 10:23:56 INFO: Flash Jetson TX2: exec_command: /tmp/tmp_NV_L4T_FLASH_TX2_WITH_OS_IMAGE_COMP.sh
  • 10:23:56 INFO: Flash Jetson TX2: sudo ./flash.sh jetson-tx2 mmcblk0p1
  • 10:23:56 INFO: Flash Jetson TX2: [ Component Install Finished with Error ]
  • 10:23:56 INFO: Flash Jetson TX2: [ 8.00 KB used. Disk Avail: 166.31 GB ]
  • 10:23:56 INFO: Flash Jetson TX2: [ NV_L4T_FLASH_TX2_WITH_OS_IMAGE_COMP Install took 0s ]
  • 10:23:56 INFO: Flash Jetson TX2:
  • 10:23:56 INFO: Flash Jetson TX2:
  • 10:24:27 INFO: OpenCV on Target: stopped downloading h.ttps://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.4-ga/JETPACK_44_b186/OpenCV-4.1.1-2-gd5a58aa75-aarch64-libs.deb
  • 10:24:27 INFO: CUDA Toolkit for L4T: stopped downloading h.ttps://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.4-ga/JETPACK_44_b186/cuda-repo-l4t-10-2-local-10.2.89_1.0-1_arm64.deb
  • 10:24:32 INFO: OpenCV on Target: stopped downloading h.ttps://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.4-ga/JETPACK_44_b186/OpenCV-4.1.1-2-gd5a58aa75-aarch64-dev.deb
  • 10:24:32 INFO: OpenCV on Target: stopped downloading h.ttps://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.4-ga/JETPACK_44_b186/OpenCV-4.1.1-2-gd5a58aa75-aarch64-licenses.deb
  • 10:24:37 INFO: OpenCV on Target: stopped downloading h.ttps://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.4-ga/JETPACK_44_b186/OpenCV-4.1.1-2-gd5a58aa75-aarch64-python.deb
  • 10:24:37 INFO: OpenCV on Target: stopped downloading h.ttps://developer.nvidia.com/assets/embedded/secure/tools/files/jetpack-sdks/jetpack-4.4-ga/JETPACK_44_b186/OpenCV-4.1.1-2-gd5a58aa75-aarch64-samples.deb

*added ‘.’ in https cause new users can’t post links

There are logs for JetPack/SDKM in “~/.nvsdkm”. However, are you using a VM? This would be the most common cause of such an error. During flash USB disconnects and reconnects, and VMs tend to lose the reconnect.

Also, third party charger cables tend to fail, but not immediately like that.

No i am not using a VM. I am on a Ubuntu 18.04 machine.

Here is the log :

FYI, if you rename a log with a “.txt” file extension, then you can upload directly here and it is easier.

I am more familiar with the flash.sh logging, but from what I can see…

  • Login worked for the Jetson software line.
  • Several host side packages correctly installed.
  • Some Jetson side components did not install due to some dependency conflict.

For this latter point, Jetson side dependencies would never get a chance to install if the flash did not complete.

Your flash software would be located at:
~/nvidia/nvidia_sdk/JetPack_...version.../Linux_for_Tegra/

If you go there, then there will be subdirectory “rootfs/”. Does that have content? If so, put the Jetson in recovery mode with the micro-B USB connected, and flash like this on command line for a new log:
sudo ./flash.sh jetson-tx2 mmcblk0p1 2>&1 | tee log_flash.txt
…then attach “log_flash.txt” to the forum. This should give flash information instead of SDKM information.

Yes, there’s content in the “rootfs” directory. I ran the command and here’s the log.

###############################################################################

L4T BSP Information:

R32 , REVISION: 4.3

###############################################################################
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.

I think I set the TX2 to recovery mode as the device is showing up in the ‘lsusb’ list and am using the usb cable that came with it

This is odd that lsusb shows the device, but the flash software cannot see it. This would be expected with a VM, but not with a native Linux host PC. One thought is to make sure this is a TX2. This is a TX2 forum, and your original post said TX2, so I doubt this would not actually be a TX2. However, is this using a custom carrier board? Or can we verify this is the developer kit?

Also, if the unit were booted and providing a virtual ethernet over USB, then this lsusb might be mistaken for a recovery mode Jetson. Be certain that you hold down the recovery button, and then either power on or cycle power, followed by then letting go of the recovery button. On the host PC, monitor “dmesg --follow”. While monitoring, then insert the USB cable to the host PC, and see what the log is for that cable insert. It if mentions an ethernet device, or mass storage, then the unit is booted and not in recovery mode.

It is a TX2 developer kit. Here’s the log for the usb insert

[ 7572.320566] usb 1-1: new high-speed USB device number 14 using xhci_hcd
[ 7572.469508] usb 1-1: New USB device found, idVendor=0955, idProduct=7c18
[ 7572.469513] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 7572.469516] usb 1-1: Product: APX
[ 7572.469519] usb 1-1: Manufacturer: NVIDIA Corp.

From what you’ve described the flash should see the recovery mode Jetson, and flash.

For the case that the flash command command fails, while dmesg and lsusb have indicated the device is present, I am thinking you may have an actual hardware failure.

One last possibility: Is there anything at all unusual about the Ubuntu 18.04 host PC being used for the flash?

No. I have used this PC to flash it before. The TX2 ran out of memory yesterday and had some issues. So I decided to reflash with the latest jetpack 4.4. And this happened

Someone from NVIDIA will need to comment. From what I can tell the recovery mode is being reached, and is visible from the host PC, but flash is unable to talk to the unit. With no progress at all from even command line flash I am thinking this might be a hardware failure.

Thanks for the help. Do you think it can be something else, like jumper connections on the board?

Most of what the carrier board does won’t care about jumpers so far as the micro-B USB is concerned (while in recovery mode). As long as the unit is powered up, and the micro-B USB cable shows with lsusb, then most other parts of the board will have no effect. If you’ve customized something, then perhaps it is possible there is a side effect, but you’d have to describe the changes. I doubt those changes would cause flash to fail at the very start without even a small amount of communications succeeding.