SDK Manager for AGX Xavier- Could not detect target hardware

Hello,

I can’t flash my Jetson AGX Xavier with the SDK Manager, I always get this error :
“Could not detect target hardware
Please make sure the target hardware is connected and is in recovery mode, click OK and RETRY.”

  • 10:44:46 ERROR : Flash Jetson AGX Xavier 16GB/32GB : [exec_command]: /bin/bash -c /tmp/tmp_NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP.sh; [error]: exit status 1
  • 10:44:46 INFO : Flash Jetson AGX Xavier 16GB/32GB : [ Component Install Finished with Error ]
  • 10:44:46 INFO : Flash Jetson AGX Xavier 16GB/32GB : [ 4.00 KB used. Disk Avail: 170.99 GB ]
  • 10:44:46 INFO : Flash Jetson AGX Xavier 16GB/32GB : [ NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP Install took 6s ]
  • 10:44:46 ERROR : Flash Jetson AGX Xavier 16GB/32GB : [error]: Run commands failed at step Install: command /tmp/tmp_NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP.sh finished with error
  • 10:44:46 INFO : Flash Jetson AGX Xavier 16GB/32GB :
  • 10:44:46 ERROR : Flash Jetson AGX Xavier 16GB/32GB : command terminated with error
  • 10:44:46 ERROR : Flash Jetson AGX Xavier 16GB/32GB : Install ‘Flash Jetson AGX Xavier 16GB/32GB’ failure, command < using adapter to install NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER to /home/zfj/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER > terminated with error.
  • 10:44:46 INFO : Device Mode Host Setup in Target SDK : Install ‘Device Mode Host Setup in Target SDK’ Skipped
  • 10:44:46 INFO : DateTime Target Setup : Install ‘DateTime Target Setup’ Skipped
  • 10:44:46 INFO : CUDA Toolkit for L4T : Install ‘CUDA Toolkit for L4T’ Skipped
  • 10:44:46 INFO : cuDNN on Target : Install ‘cuDNN on Target’ Skipped
  • 10:44:46 INFO : TensorRT on Target : Install ‘TensorRT on Target’ Skipped
  • 10:44:46 INFO : OpenCV on Target : Install ‘OpenCV on Target’ Skipped
  • 10:44:46 INFO : VisionWorks on Target : Install ‘VisionWorks on Target’ Skipped
  • 10:44:46 INFO : VPI on Target : Install ‘VPI on Target’ Skipped
  • 10:44:46 INFO : NVIDIA Container Runtime with Docker integration (Beta) : Install ‘NVIDIA Container Runtime with Docker integration (Beta)’ Skipped
  • 10:44:46 INFO : Multimedia API : Install ‘Multimedia API’ Skipped
  • 10:44:47 INFO : All done!

My host is under Ubuntu 18.04.
My AGX Xavier is in recovery mode. The usb cable is connected from the AGX Xavier to my PC.
My host and the AGX Xavier are connected on a switch with access to the internet.

I tried to plug every USB port on my host PC, but it is no use.
here’s the ‘lsusb’ output:
$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 1c4f:0034 SiGma Micro
Bus 001 Device 009: ID 0955:7019 NVidia Corp.
Bus 001 Device 003: ID 1c4f:0026 SiGma Micro Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Could you help me?
Thanks.

Hi 15123904739,

Are you connect USB type-C cable on J512 port from Xavier to host machine? [User Guide]
Please also try flash image by manually:

  1. Put Jetson-Xavier into recovery mode
  2. cd /home/zfj/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra
  3. Flash:
    $ sudo ./flash.sh jetson-xavier mmcblk0p1

hi, carolyuu!
I have connected USB type-C cable on J512 port from Xavier to host machine,but it still shows ‘Could not detect target hardware.Please make sure the target hardware is connected and is in recovery mode, click OK and RETRY.’
I tried your code, but it failed.

zfj@zfj-Z370-HD3:~ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Bus 001 Device 003: ID 1c4f:0026 SiGma Micro Keyboard Bus 001 Device 015: ID 0955:7019 NVidia Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub zfj@zfj-Z370-HD3:~ cd /home/zfj/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra
zfj@zfj-Z370-HD3:~/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra$ sudo ./flash.sh jetson-xavier mmcblk0p1
[sudo] zfj 的密码:
###############################################################################

L4T BSP Information:

R32 , REVISION: 4.2

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

This is valid for starting a flash. However, if the host PC is a VM, then VMs tend to fail USB mid-flash. Is the host native, or VM?

it’s the host native. In addition, I tried every USB port in host native.

The USB-Type C line is original. of course, I tried with other USB-Type C lines. They all failed.

Is there any other solutions?

Continuing the discussion from SDK Manager for AGX Xavier- Could not detect target hardware:

when it goes 1.0%, I always get the error–“Could not detect target hardware
Please make sure the target hardware is connected and is in recovery mode, click OK and RETRY.”

Hi,

I had a similar issue, and it was solved by uninstalling tlp (apt purge tlp, then reboot), see eg https://developer.download.nvidia.com/embedded/L4T/r32-3-1_Release_v1.0/Jetson_Linux_Driver_Package_Release_Notes_R32.3.1_GA.pdf or ERROR : Flash Jetson TX2 : lost connection

The USB-C near the power button and 40-pin header is mandatory for recovery mode use. If recovery mode cannot be reached (holding recovery while either cycling power or powering up), then it is highly suspect that there is an actual hardware failure.

You might try flashing on command line. If you find the directory under “~/nvidia/nvidia_sdk/JetPack...named after release and P2888/Linux_for_Tegra/”, then you might see if this works after first verifying lsusb shows the Jetson in recovery mode:
sudo ./flash.sh jetson-xavier mmcblk0p1 2>&1 | tee log_flash.txt
(the extra is to provide a log of the flash result)

If command line also fails, then it should provide different debug information. If you are unable to reach recovery mode, then it seems somewhere in the chain of hardware there is an actual hardware failure.

Hi 15123904739,

Please install python3 on your host machine and run SDK Manager again.
Thanks!

1 Like