Jetpack failing after flashing the OS

haranbolt · April 15, 2019, 4:22pm

I am trying to flash a Jetson Xavier using Jetpack 4.2.

After the OS is flashed, Jetpack prompts me to finish the Ubuntu setup wizard and input the login credentials of Xavier into Jetpack so as to finish installing the SDK components. When I do that and click ‘Install’, Jetpack says that it is unable to connect to the device.

I connected the Xavier to the host via with the provided usb cable and haven’t changed the setup after the OS got flashed. I tried reflashing once more, but the Jetpack failed with the same error.

The link below leads to an image containing the error and the relevant logs.
[url]https://drive.google.com/file/d/1J9K0L0U2M4O9GTaJoDW9MGr2gFaOi0oN/view?usp=sharing[/url]

Honey_Patouceul · April 15, 2019, 6:30pm

Assuming it’s correctly flashed, you may check this post. You may also try post-flash only with wired ethernet instead of ip over USB.

haranbolt · April 17, 2019, 5:44am

What do you mean by wired ethernet?
This is my current setup:

Xavier: connected to host via usb and connected to the internet via a wired ethernet connection to a router
Host: connected to xavier via usb and connected to the internet via the same router wirelessly

The link below contains the log files asked in the forum post you had linked.
https://drive.google.com/drive/folders/1sDqMqy9tg8urL823zVdkAc2eVE8NSf34?usp=sharing

WayneWWW · April 17, 2019, 7:21am

Jetpack uses usb cable for flashing the image to Xavier.
But for the sw components, it is using wired ethernet. USB cable has nothing to do at this step.

In brief, if your host is able to ping the IP addr of Xaiver, it should work.

haranbolt · April 17, 2019, 8:33am

I have verified that the host is able to ping the Xavier. But jetpack still is unable to connect to the Xavier.

WayneWWW · April 17, 2019, 9:26am

Sorry, if this is sdkmanager, it transmits the component through the usb cable. Could you share the result of “lsusb” on your host during installation failure?

haranbolt · April 17, 2019, 10:56am

Here’s the output of lsusb.

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1bcf:2b97 Sunplus Innovation Technology Inc. 
Bus 001 Device 003: ID 187c:0550 Alienware Corporation 
Bus 001 Device 006: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 8087:0025 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

WayneWWW · April 18, 2019, 2:10am

haranbolt,

I just notice your sdkmanager is still searching “NVIDIA Corp” in lsusb. It means the manager is trying to flash the OS.

Are you sure your device is flashed correctly and you are not flashing it again?

haranbolt · April 22, 2019, 6:51am

So, I have flashed the OS, but the SDK components haven’t been flashed. That’s where the problem lies.

WayneWWW · April 22, 2019, 9:08am

Could you use manual script to flash the board? We just received some similar bug reports as yours.

Please use below steps and see if it can flash or not.

Put device into recovery mode.
cd Linux_for_Tegra
3… sudo ./flash jetson-xaiver mmcblk0p1

WayneWWW · April 22, 2019, 9:10am

Are you really sure the OS is flashed? I suspect this because in your sdkmanager, it is still checking “NVIDIA Corp”.

“NVIDIA Corp” checking is only needed when flashing OS. There is no need to do it when installing components.

WayneWWW · April 22, 2019, 9:59am

hmm… per checked your log, it seems boot up. Are you able to see there is a USB interface with ip 192.168.55.1 in your ifconfig?

Also, you should also see another interface from ifconfig on your host PC.

These two interfaces should be able to ping each other when usb cable is connected. You don’t need a router.

Could you capture the log of installation failure? I don’t see you post it.

haranbolt · April 23, 2019, 11:21am

Here is the entire log when trying to install just the SDK components after the OS is flashed.

16:48:22 INFO : null
16:48:26 INFO : OpenCV on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/libopencv-dev_3.3.1-2-g31ccdfe11_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : OpenCV on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/libopencv_3.3.1-2-g31ccdfe11_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : OpenCV on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/libopencv-python_3.3.1-2-g31ccdfe11_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : OpenCV on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/libopencv-samples_3.3.1-2-g31ccdfe11_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : cuDNN on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/libcudnn7-dev_7.3.1.28-1+cuda10.0_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : cuDNN on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/libcudnn7_7.3.1.28-1+cuda10.0_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : cuDNN on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/libcudnn7-doc_7.3.1.28-1+cuda10.0_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : TensorRT on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/libnvinfer5_5.0.6-1+cuda10.0_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : TensorRT on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/libnvinfer-dev_5.0.6-1+cuda10.0_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : TensorRT on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/tensorrt_5.0.6.3-1+cuda10.0_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : TensorRT on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/python-libnvinfer_5.0.6-1+cuda10.0_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : TensorRT on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/python-libnvinfer-dev_5.0.6-1+cuda10.0_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : TensorRT on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/python3-libnvinfer_5.0.6-1+cuda10.0_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : TensorRT on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/python3-libnvinfer-dev_5.0.6-1+cuda10.0_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : TensorRT on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/graphsurgeon-tf_5.0.6-1+cuda10.0_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : TensorRT on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/uff-converter-tf_5.0.6-1+cuda10.0_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : VisionWorks on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/libvisionworks-repo_1.6.0.500n_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : VisionWorks on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/libvisionworks-sfm-repo_0.90.4_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : VisionWorks on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/libvisionworks-tracking-repo_0.88.2_arm64.deb with correct checksum, skip downloading.
16:48:26 INFO : Multimedia API : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/Tegra_Multimedia_API_R32.1.0_aarch64.tbz2 with correct checksum, skip downloading.
16:48:27 INFO : TensorRT on Target : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/libnvinfer-samples_5.0.6-1+cuda10.0_all.deb with correct checksum, skip downloading.
16:48:27 INFO : CUDA Toolkit for L4T : Found file /home/haranrk/Downloads/nvidia/sdkm_downloads/cuda-repo-l4t-10-0-local-10.0.166_1.0-1_arm64.deb with correct checksum, skip downloading.
16:50:08 INFO : [host] [sudo] password for haranrk:
16:50:08 INFO :
16:50:08 INFO :
16:50:08 DEBUG : running command < ip addr | grep 192.168.55.100/24 >
16:50:08 ERROR : command terminated with error
16:50:08 DEBUG : running command < lsusb | grep "NVidia Corp" >
16:50:08 ERROR : command terminated with error
16:50:08 ERROR : Could not connect to the target device. Verify that: 1. The device is connected to this host machine with a USB cable. 2. Ubuntu 'System configuration wizard' is completed on the device. 3. Jetson's Ubuntu OS is up and running.
16:50:12 INFO : Device Mode Host Setup in Target SDK : install 'Device Mode Host Setup in Target SDK' Skipped
16:50:12 INFO : DateTime Target Setup : install 'DateTime Target Setup' Skipped
16:50:12 INFO : CUDA Toolkit for L4T : install 'CUDA Toolkit for L4T' Skipped
16:50:12 INFO : cuDNN on Target : install 'cuDNN on Target' Skipped
16:50:12 INFO : TensorRT on Target : install 'TensorRT on Target' Skipped
16:50:12 INFO : OpenCV on Target : install 'OpenCV on Target' Skipped
16:50:12 INFO : VisionWorks on Target : install 'VisionWorks on Target' Skipped
16:50:12 INFO : Multimedia API : install 'Multimedia API' Skipped
16:50:13 INFO : All done!

haranbolt · April 23, 2019, 11:22am

Could you tell me where the Linux_for_Tegra folder is? It’s not there in the files downloaded by jetpack

haranbolt · April 23, 2019, 11:24am

There is no change in the output of the ifconfig between when the xavier is connected via usb and when it’s not

WayneWWW · April 23, 2019, 3:59pm

Hi,

This log matches what I thought. Could you just share your the result of ifconfig with us?

16:50:08 DEBUG : running command < ip addr | grep 192.168.55.100/24 >
16:50:08 ERROR : command terminated with error
16:50:08 DEBUG : running command < lsusb | grep "NVidia Corp" >
16:50:08 ERROR : command terminated with error

Also, Linux_for_Tegra folder path is definitely under your host. Otherwise the OS flash would not be done.
It would be installed somewhere. Sorry that I am not with my office pc now so cannot give you the answer.

If I remember correctly, you can choose a path in sdkmanager.Linux_for_Tegra should be there.

WayneWWW · April 23, 2019, 4:00pm

Note: please share ifconfig result of both your host pc and xaiver.

Andrey1984 · April 23, 2019, 4:19pm

there should as well be some peculiarity when host could be able to connect to guest[jetson] only after manually with keyboard and monitor the post installation configuration has been made at guest[jetson] where username and password are set. I understand that it is not the issue, but unless username and password are set manually, the sdk manager processed post installation can not be completed, as it seems to me from my experience.

WayneWWW · April 24, 2019, 3:36am

I guess the usb-ethernet interface is not up on your host.

haranbolt · April 24, 2019, 6:04am

Here are the ifconfigs.

Host:

br-1af98daaeaa5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.20.0.1  netmask 255.255.0.0  broadcast 172.20.255.255
        inet6 fe80::42:3cff:fe28:b64f  prefixlen 64  scopeid 0x20<link>
        inet6 fe80::42:3cff:fe28:b64f  prefixlen 64  scopeid 0x20<link>
        ether 02:42:3c:28:b6:4f  txqueuelen 0  (Ethernet)
        RX packets 1946  bytes 145304 (145.3 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1944  bytes 1073190 (1.0 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-b678cd3b6216: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        inet6 fe80::42:78ff:fe57:6ac2  prefixlen 64  scopeid 0x20<link>
        ether 02:42:78:57:6a:c2  txqueuelen 0  (Ethernet)
        RX packets 12  bytes 336 (336.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 299  bytes 33753 (33.7 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-caf73303b1b3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.19.0.1  netmask 255.255.0.0  broadcast 172.19.255.255
        inet6 fe80::42:9eff:feb2:c2db  prefixlen 64  scopeid 0x20<link>
        ether 02:42:9e:b2:c2:db  txqueuelen 0  (Ethernet)
        RX packets 20  bytes 1040 (1.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 326  bytes 36252 (36.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:ee:d4:f7:03  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp0s20f0u2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.55.100  netmask 255.255.255.0  broadcast 192.168.55.255
        inet6 fe80::a9fc:4b0:4682:f7eb  prefixlen 64  scopeid 0x20<link>
        ether 82:93:1d:bf:86:76  txqueuelen 1000  (Ethernet)
        RX packets 214  bytes 25956 (25.9 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 57  bytes 14198 (14.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp0s20f0u2i5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::e815:b7f8:86d4:ed29  prefixlen 64  scopeid 0x20<link>
        ether 76:57:cc:50:7d:92  txqueuelen 1000  (Ethernet)
        RX packets 63  bytes 8564 (8.5 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 57  bytes 10013 (10.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp68s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether e4:b9:7a:2f:b2:8d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 18

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 191284  bytes 49188165 (49.1 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 191284  bytes 49188165 (49.1 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp69s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1490
        inet 10.79.197.195  netmask 255.255.248.0  broadcast 10.79.199.255
        inet6 fe80::7348:3d48:4aea:4d70  prefixlen 64  scopeid 0x20<link>
        ether 3c:6a:a7:f4:ba:cd  txqueuelen 1000  (Ethernet)
        RX packets 13351201  bytes 17142190265 (17.1 GB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2914576  bytes 545529612 (545.5 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Topic		Replies	Views
SDK Manager fails to install target componetns on Xavier Jetson AGX Xavier	29	2263	December 23, 2019
SDK manager Flashing failed, please help me Jetson AGX Xavier sdkm	9	2356	October 18, 2021
Jetpack 4.2: Can not install SDK components Jetson AGX Xavier	16	6294	October 18, 2021
Jetson AGX Xavier Flash Failure Jetson AGX Xavier	12	4981	October 18, 2021
Nvidia xavier nx dev kit not able to boot properly Jetson Xavier NX boot	31	917	July 13, 2022
Jetson Xavier NX (Developer Edition) not starting (blank screen) Jetson Xavier NX boot , hw , ubuntu , usb , power	21	3385	July 1, 2022
I can't install JetPack 4.6 (REV.2) on Xavier Development Kit Jetson AGX Xavier jetpack	35	2064	December 1, 2021
Jetson SDK Components: recovery mode problem Jetson AGX Xavier	19	4582	October 18, 2021
AGX Xavier Jetpack 4.2 Flashing Failed (At Around 98%) Jetson AGX Xavier reflash	29	2694	October 18, 2021
Xavier does not flash with host pc Jetson AGX Xavier	14	1543	October 18, 2021

Jetpack failing after flashing the OS

Related topics