Jetson SDK Components: recovery mode problem

Hello.

I am trying to make a fresh install of Jetson Jetpack 4.2. My setup is:

  • Nvidia Jetson Xavier Model P2972
  • SDK Manager 0.9.11.3405
    Host:
  • Ubuntu 16.04
  • CUDA 10.0

I am able to follow until the Jetson OS image is installed. Afterward I have the following problem. When Im already in the login page in the OS, and the SDK manager is supossed to install Jetson SDK Components, it complains saying

‘Jetson device is in recovery mode’

so I understand it should not be in recovery mode at that point.

I shutdown and power up again Jetson Xavier until the login page. Now I run again sdkmanager from host’s console and now it complains

“Could not detect target hardware. Please make sure target hardware is connected and is in Recovery mode, click OK and RETRY”

So it was complaining because it was in Recovery now and now it is saying it should be in Recovery mode??

I shutdown again and now enter in Recovery mode. I run again sdkmanager from host console and follow the process again until the login window. It complains again that the device is in Recovery mode and from there it is a loop, complaining it should be in recovery mode, then that it should not be in Recovery mode…

What is the issue?

I uploaded screeshots here: https://imgur.com/a/KOPinn2

Thanks

Hi juanmedrano.ec09,

Are you connect the HDMI cable?
After completed the flash, you need initial setup process (setup your username, password and language…), then the device boots to Linux Desktop. At this point, please enter your username and password to continue install again.

Thanks!

That screenshot has something subtle…it is complaining that the device is in recovery mode, and that is a problem for package additions. The Jetson needs to be fully booted and not in recovery mode…kind of the reverse of what might be expected (try rebooting the Xavier if it didn’t boot automatically after a flash).

Did you manage to solve this issue? I tried rebooting the Xavier but still encountered the same “recovery mode” error.

Same problem here but solved it. It seems that the GUI for network settings is only able to activate a single ethernet connection a time. In the top right corner right click on the network symbol, choose settings for the usb ethernet device and activate it.

@carolyuu I already tried continuing wit the process after logging with no success. Is there any other method to install SDK Components without the SDK manager? I cannot solve this issue

@ linuxdev I already treid rebooting manually ensuring jetson is not in recovery mode. No success.

@ user_jay, I am still unable to solve this issue

@ OliverUR, could please describe in more detail what you did? Which network exactly did you connected to? The network settings you are talking about is in the host computer network settings, in SDK manager or in Xavier? Exactly at which point did you do this? Did you do it when the "Jetson is in recovery mode appears?

I tried changing network at exactly that moment, but still no success. Which network exactly did you connected to? I see 3 networks appear but none of them where able to get me pass the "Jetson is in recovery mode message. https://imgur.com/a/E3YcTCz

Hi juanmedrano.ec09,

After you see the ubuntu desktop on Jetson device, are you able to ping 192.168.55.1?

You can refer this topic: https://devtalk.nvidia.com/default/topic/1048660

Hello,

Thanks for your response. I saw and followed the recommendations on the topic you linked. I read and followed the first section on “Using Ethernet Protocol” of the file README-usb-dev-mode.txt.

  1. It is mentioned in that file that

“Linux for Tegra assigns a static IPv4 address of 192.168.55.1 to Jetson, and runs a DHCP server to automatically assign an IPv4 address to your host machine. This provides point-to-point connectivity.”

However this does not happen in my case. When Jetson Xavier is on and I can see the Ubuntu desktop, the new network interfaces “enp0s20f0u1” and “enp0s20f0u1i5” appear but NONE OF THEM have an IP address in the 192.168.55.x network assigned. The original interface enp2s0 remains with the original IP address it has always had. https://imgur.com/a/vwc7rZJ

I try to PING 192.168.55.1 but I cannot reach it. There is no connection.

  1. I then use the command “sudo ifconfig enp0s20f0u1 192.168.55.5 netmask 255.255.255.0” to manually assign an IP address in the network of the Jetson to the first of the newly generated interfaces. After doing this I can SUCCESSFULLY ping 192.168.55.1 and SUCCESSFULLY ssh nvidia@192.168.55.1. HOWEVER STILL in the SDK manager the message JETSON IS IN RECOVERY MODE appears and cannot continue with the SDK components installation process.

PLEASE let me know clear and step by step process on how to solve this issue. If not, let me know another procedure to install the SDK components that does not uses the SDK Manager.

If am really looking forward for your answer. I have not been able to run a new, out of the box Xavier in 2 weeks!

Thank you.

Sorry for the inconvenience, could you please run “sudo ifconfig enp0s20f0u1 192.168.55.100 netmask 255.255.255.0” and try again?

Hi juanmedrano.ec09,

Have you managed to get device flashed and installed through SDK manager successfully?
Any result can be shared?

Thanks

Hello,

Yes I was able to try the last advice from EdwardZhou with success. SDK Manager was able to flash the Nvidia Xavier and install all the SDK Components. The only part in which the installation failed was installing the cross compiler in the host machine. However the installation process finished cleanly.

In conclusion:

  1. After SDK Manager installs the OS Image and all the initialization process is finished up to one being in Ubuntu Desktop, and in the SDK Manager requires Jetson Xavier password and indicates ‘Jetson is in recovery mode’, on should MANUALLY configure the ipV4 address of any of the newly created network interfaces. (One should assume that the fact that ‘Jetson is in recovery mode’ appears, means that automatic ipv4 address configuration FAILED)

  2. One must set the ipv4 address to [b]192.168.55.100 / 255.255.255.0[b]. The command

sudo ifconfig enp0s20f0u1 192.168.55.100 netmask 255.255.255.0

worked for me. There ‘enp0s20f0u1’ is the name of one (of the several) newly created network interfaces. I am not sure how to discriminate which of the several newly created interfaces to use at this point, and guess that one should try until finding one that works.

  1. After configuring the ipv4 address one should retry to input the password in SDK Manager and hopefully it will be able to communicate with the Jetson Xavier and continue with the SDK Components installation process.

Hi juanmedrano.ec09,

Good to know it’s working by our suggestion, and thanks for having the conclusion to let other developers be reference once they met similar problem.

Thanks

im having simlilar problems i recently purchased a jetson xavier.

Jetson Xavier: p2972
OS: ubuntu 18.04
sdkmanager 1.1.0.6343

im trying to flash 4.4 on it but like the OP, im having the similar issues. i tried manually flashing it, putting in into recovery it detects it then afterwards, when it begins to flash it afterwards says it cant detect it. I couldnt do automatic flash because the l4t mode service wasnt running. so i connected my jetson nano open the txt file that contained the commands to run it because i forgot they were in the /opt folder, ranned the command to start the service and it failed. so i took the file from the /opt/nvida/l4t-usb-mode/ in the rootfs folder, and overwritten the one in the /opt folder. ranned the command again, now i got a ip address on the front usb port. try the flash the board again, using “automatic”, the xavier is forced into recovery. and a black screen on my display. and when the sdkmanager is finished downloading it, says it cannot find the board and halts everything asking me if i want to retry

Blockquote * 05:39:39 INFO : Automatic trying to flash the target device with Manual Flash option failed!

  • 05:39:39 INFO : Automatic trying to flash the target device with Automatic Flash option…
  • 05:39:39 DEBUG : running command < [ lsusb | grep -c "0955:" -ne 1 ] >
  • 05:39:39 DEBUG : command terminated with error
  • 05:39:39 INFO : Only one NVIDIA device detected, as expected.
  • 05:39:39 DEBUG : running command < ip addr | grep 192.168.55.1 >
  • 05:39:40 INFO : inet 192.168.55.100/24 brd 192.168.55.255 scope global dynamic noprefixroute enp0s20f0u2i5
  • 05:39:40 INFO : command finished successfully
  • 05:39:40 DEBUG : running command < nc -z -vv -w 5 192.168.55.1 22 >
  • 05:39:40 INFO : Connection to 192.168.55.1 22 port [tcp/ssh] succeeded!
  • 05:39:40 INFO : command finished successfully
  • 05:39:40 INFO : Connection to the device via SSH is avaliable.
  • 05:39:40 DEBUG : running command < ssh -F /dev/null -o PubkeyAuthentication=no -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o ConnectTimeout=5 mark@192.168.55.1 echo hello >
  • 05:39:40 INFO : Warning: Permanently added ‘192.168.55.1’ (ECDSA) to the list of known hosts.
  • 05:39:40 INFO : [target] mark@192.168.55.1’s password:
  • 05:39:40 INFO :
  • 05:39:41 INFO : hello
  • 05:39:41 INFO : command finished successfully
  • 05:39:41 INFO : Validated its username and password.
  • 05:39:41 DEBUG : running command < ssh -F /dev/null -o PubkeyAuthentication=no -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o ConnectTimeout=5 -o ServerAliveInterval=1 -o ServerAliveCountMax=5 -tt mark@192.168.55.1 sudo reboot forced-recovery >
  • 05:39:41 INFO : Warning: Permanently added ‘192.168.55.1’ (ECDSA) to the list of known hosts.
  • 05:39:41 INFO : [target] mark@192.168.55.1’s password:
  • 05:39:41 INFO :
  • 05:39:42 INFO : [target] [sudo] password for mark:
  • 05:39:42 INFO :
  • 05:39:42 INFO : Connection to 192.168.55.1 closed by remote host.
  • 05:39:42 INFO : Connection to 192.168.55.1 closed.
  • 05:39:42 DEBUG : command terminated with error
  • 05:39:42 INFO : The command to set device into recovery mode processed.
  • 05:39:47 DEBUG : running command < lsusb | grep -i “0955:” >
  • 05:39:47 DEBUG : command terminated with error
  • 05:39:52 DEBUG : running command < lsusb | grep -i “0955:” >
  • 05:39:52 INFO : Bus 001 Device 039: ID 0955:7019 NVidia Corp.
  • 05:39:52 INFO : command finished successfully
  • 05:39:52 DEBUG : running command < lsusb | grep 0955:7020 >
  • 05:39:52 DEBUG : command terminated with error
  • 05:39:53 INFO : Recovery mode is set for 0955:7019.
  • 05:39:53 DEBUG : running command < lsusb | grep 0955:7019 >
  • 05:39:53 INFO : Bus 001 Device 039: ID 0955:7019 NVidia Corp.
  • 05:39:53 INFO : command finished successfully
  • 05:39:53 INFO : Verified, 0955:7019 detected in recovery mode.
  • 05:39:53 INFO : Device Mode Host Setup in Flash : Start to install ‘Device Mode Host Setup in Flash’
  • 05:39:53 DEBUG : Device Mode Host Setup in Flash : using adapter to install NV_DEVICE_MODE_SETUP_IMAGE_COMP@JETSON_AGX_XAVIER to /home/mark/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER
  • 05:39:53 INFO : Device Mode Host Setup in Flash : [ Disk Avail:168.70 GB ]
  • 05:39:53 INFO : Device Mode Host Setup in Flash : Using GenericInstaller to Install NV_DEVICE_MODE_SETUP_IMAGE_COMP
  • 05:39:53 INFO : Device Mode Host Setup in Flash : change working directory to /home/mark/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER
  • 05:39:53 INFO : Device Mode Host Setup in Flash : [ Component Install Started ]
  • 05:39:53 INFO : Device Mode Host Setup in Flash : current working directory is /home/mark/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER
  • 05:39:53 INFO : Device Mode Host Setup in Flash : exec_command [host]:
  • 05:39:53 INFO : Device Mode Host Setup in Flash : **********************
  • 05:39:53 INFO : Device Mode Host Setup in Flash : #!/bin/bash
  • 05:39:53 INFO : Device Mode Host Setup in Flash : set -e
  • 05:39:53 INFO : Device Mode Host Setup in Flash : set +e
  • 05:39:53 INFO : Device Mode Host Setup in Flash : eth_port_name=$(ip route show default | awk ‘/default via/ {print $5; exit}’)
  • 05:39:53 INFO : Device Mode Host Setup in Flash : if [[ $eth_port_name == ‘’ ]]; then
  • 05:39:53 INFO : Device Mode Host Setup in Flash : echo ‘Can not found route default $eth_port_name, device mode setup failed!’
  • 05:39:53 INFO : Device Mode Host Setup in Flash : exit 0
  • 05:39:53 INFO : Device Mode Host Setup in Flash : fi
  • 05:39:53 INFO : Device Mode Host Setup in Flash : echo ‘Found route default’ $eth_port_name’, setting up device mode’
  • 05:39:53 INFO : Device Mode Host Setup in Flash : setup_t=‘192.168.55.0/24’
  • 05:39:53 INFO : Device Mode Host Setup in Flash : sudo iptables -t nat -A POSTROUTING -s $setup_t -o $eth_port_name -j MASQUERADE
  • 05:39:53 INFO : Device Mode Host Setup in Flash : sudo iptables -A FORWARD -s $setup_t -o $eth_port_name -j ACCEPT
  • 05:39:53 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
  • 05:39:53 INFO : Device Mode Host Setup in Flash : sudo sysctl -w net.ipv4.ip_forward=1
  • 05:39:53 INFO : Device Mode Host Setup in Flash : check_google_dns=$(dig @8.8.8.8 nvidia.com || true)
  • 05:39:53 INFO : Device Mode Host Setup in Flash : if [[ $check_google_dns == ‘Got answer’ ]]; then
  • 05:39:53 INFO : Device Mode Host Setup in Flash : echo ‘Device mode on host successfuly set with DNS 8.8.8.8!’
  • 05:39:53 INFO : Device Mode Host Setup in Flash : exit 0
  • 05:39:53 INFO : Device Mode Host Setup in Flash : else
  • 05:39:53 INFO : Device Mode Host Setup in Flash : echo ‘Default google DNS is not working, trying to find a valid server in local host settings!’
  • 05:39:53 INFO : Device Mode Host Setup in Flash : dns_list=$(nmcli -t device show eth_port_name | grep 'DNS' | grep -o '[^:]*')
  • 05:39:53 INFO : Device Mode Host Setup in Flash : for dns in $dns_list; do
  • 05:39:53 INFO : Device Mode Host Setup in Flash : check_dns=$(dig @$dns nvidia.com || true)
  • 05:39:53 INFO : Device Mode Host Setup in Flash : if [[ $check_dns == ‘Got answer’ ]]; then
  • 05:39:53 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
  • 05:39:53 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
  • 05:39:53 INFO : Device Mode Host Setup in Flash : echo ‘Device mode on host successfuly set with DNS’ $dns’!’
  • 05:39:53 INFO : Device Mode Host Setup in Flash : exit 0
  • 05:39:53 INFO : Device Mode Host Setup in Flash : fi
  • 05:39:53 INFO : Device Mode Host Setup in Flash : done
  • 05:39:53 INFO : Device Mode Host Setup in Flash : echo ‘Can not found a valid DNS server, device mode setup failed!’
  • 05:39:53 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.’
  • 05:39:53 INFO : Device Mode Host Setup in Flash : exit 0
  • 05:39:53 INFO : Device Mode Host Setup in Flash : fi
  • 05:39:53 INFO : Device Mode Host Setup in Flash : **********************
  • 05:39:53 INFO : Device Mode Host Setup in Flash : exec_command: /tmp/tmp_NV_DEVICE_MODE_SETUP_IMAGE_COMP.sh
  • 05:39:53 INFO : Device Mode Host Setup in Flash : Found route default enp0s31f6, setting up device mode
  • 05:39:53 INFO : Device Mode Host Setup in Flash : [host] [sudo] password for mark:
  • 05:39:53 INFO : Device Mode Host Setup in Flash :
  • 05:39:53 INFO : Device Mode Host Setup in Flash : net.ipv4.ip_forward = 1
  • 05:39:53 INFO : Device Mode Host Setup in Flash : Device mode on host successfuly set with DNS 8.8.8.8!
  • 05:39:53 INFO : Device Mode Host Setup in Flash : [ Component Install Finished Successfully ]
  • 05:39:53 INFO : Device Mode Host Setup in Flash : [ 16.00 KB used. Disk Avail: 168.70 GB ]
  • 05:39:53 INFO : Device Mode Host Setup in Flash : [ NV_DEVICE_MODE_SETUP_IMAGE_COMP Install took 1s ]
  • 05:39:53 INFO : Device Mode Host Setup in Flash : command finished successfully
  • 05:39:53 INFO : Device Mode Host Setup in Flash : Install ‘Device Mode Host Setup in Flash’ success
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : Start to install ‘Flash Jetson AGX Xavier 16GB/32GB’
  • 05:39:53 DEBUG : Flash Jetson AGX Xavier 16GB/32GB : using adapter to install NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER to /home/mark/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : [ Disk Avail:168.70 GB ]
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : Using GenericInstaller to Install NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : change working directory to /home/mark/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : [ Component Install Started ]
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : current working directory is /home/mark/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : exec_command [host]:
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : **********************
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : #!/bin/bash
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : set -e
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : set -e
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : if [ -e ./bootloader/system.img ]; then
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : echo sudo ./flash.sh --no-systemimg jetson-xavier mmcblk0p1
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : sudo ./flash.sh --no-systemimg jetson-xavier mmcblk0p1
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : else
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : echo sudo ./flash.sh jetson-xavier mmcblk0p1
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : sudo ./flash.sh jetson-xavier mmcblk0p1
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : fi
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : sleep 20
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : **********************
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : exec_command: /tmp/tmp_NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP.sh
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : sudo ./flash.sh jetson-xavier mmcblk0p1
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB : [host] [sudo] password for mark:
  • 05:39:53 INFO : Flash Jetson AGX Xavier 16GB/32GB :
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB : ###############################################################################
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB : # L4T BSP Information:
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB : # R32 , REVISION: 4.2
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB : ###############################################################################
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB : # Target Board Information:
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB : # Name: jetson-xavier, Board Family: t186ref, SoC: Tegra 194,
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB : # OpMode: production, Boot Authentication: NS,
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB : ###############################################################################
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB : copying soft_fuses(/home/mark/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-soft-fuses-l4t.cfg)… done.
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB : ./tegraflash.py --chip 0x19 --applet “/home/mark/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER/Linux_for_Tegra/bootloader/mb1_t194_prod.bin” --skipuid --soft_fuses tegra194-mb1-soft-fuses-l4t.cfg --bins “mb2_applet nvtboot_applet_t194.bin” --cmd “dump eeprom boardinfo cvm.bin;reboot recovery”
  • 05:39:54 ERROR : Flash Jetson AGX Xavier 16GB/32GB : /usr/bin/env: ‘python’
  • 05:39:54 ERROR : Flash Jetson AGX Xavier 16GB/32GB : : No such file or directory
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB : Reading board information failed.
  • 05:39:54 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
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB : [ Component Install Finished with Error ]
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB : [ 16.00 KB used. Disk Avail: 168.70 GB ]
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB : [ NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP Install took 0s ]
  • 05:39:54 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
  • 05:39:54 INFO : Flash Jetson AGX Xavier 16GB/32GB :
  • 05:39:54 ERROR : Flash Jetson AGX Xavier 16GB/32GB : command terminated with error
  • 05:39:54 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/mark/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_AGX_XAVIER > terminated with error.
  • 05:39:54 INFO : Device Mode Host Setup in Target SDK : Install ‘Device Mode Host Setup in Target SDK’ Skipped
  • 05:39:54 INFO : DateTime Target Setup : Install ‘DateTime Target Setup’ Skipped
  • 05:39:54 INFO : CUDA Toolkit for L4T : Install ‘CUDA Toolkit for L4T’ Skipped
  • 05:39:54 INFO : cuDNN on Target : Install ‘cuDNN on Target’ Skipped
  • 05:39:54 INFO : TensorRT on Target : Install ‘TensorRT on Target’ Skipped
  • 05:39:54 INFO : OpenCV on Target : Install ‘OpenCV on Target’ Skipped
  • 05:39:54 INFO : VisionWorks on Target : Install ‘VisionWorks on Target’ Skipped
  • 05:39:54 INFO : VPI on Target : Install ‘VPI on Target’ Skipped
  • 05:39:55 INFO : NVIDIA Container Runtime with Docker integration (Beta) : Install ‘NVIDIA Container Runtime with Docker integration (Beta)’ Skipped
  • 05:39:55 INFO : Multimedia API : Install ‘Multimedia API’ Skipped
  • 05:39:56 INFO : All done!

im at the point im literally going to just copy over the rootfs to the emmc via
nvme. i honestly just need the GPU/Cuda to work for blender and krita. I like this GPU more then my RTX 2070 super. but i do want to be able to reflash it when ever it necessary. This is exact problem was my greatest fear with this board, because youre dependent upon SDKmanager, and there isnt a downloadable image for it like the nano or the xavier NX

Are you using a VM? If so, then this is what VMs do (this is very common in a VM). If not a VM, then there is a genuine problem.

During flash the USB disconnects and reconnects several times. VMs tend to lose that connection unless special effort was set up to make sure the VM keeps ownership.

No, this isnt VM. Ubuntu has been installed on a sandisk 240 GB SSD, being booted off a sata to usb3 enclosure

Is the SSD over USB using USB’s power (is the Jetson providing power)? Or is this an externally powered USB3 enclosure? I’m thinking that if this is powered by the Jetson, and not externally, then perhaps you are hitting a higher power use causing problems (and power use would depend on what is going on at the moment).

The SSD Enclosure is a usb 3.0, powerd/booting on 32 GB of memory, an Intel i7-7770k, Rx580 8GB. On a Gigabyte z270 Designare motherboard. The jetson xavier is only powered by its stock power supply it comes with.

Are you speaking of an SSD connected to the Intel i7? I’m hoping to be able to clarify if the SSD is going directly to the Jetson, or if this is being used in some intermediate way. If the Jetson is using a file server as a disk source, rather than directly a disk, then it can change requirements.

I hooked it up sata to sata, and and flashed properly with jetpack 4.4, and cuda is working in blender. Tha ks. Now im going back to my other thread about recompiling the kernel, because im getting errors when trying to reconpile the kernel for the xavier. Because my managed to get one of my tablets to work on the jetson nano. So i wanted to do the same process on the xavier, but getting errors. Ill post it on my other theard. Thanks