Flashing TX2 jetpack3.3.1 error update and fail

Hi everybody,

try update jetson kit TX2 with sdk 1.0.1.5538 (same issue with previous version) I have see in terminal :

2:56:40 ERROR : Flash Jetson TX2 : 1203: SKP: 57344( 14 blks) ==> 835725440:12
12:56:40 ERROR : Flash Jetson TX2 : 1204: RAW: 20480( 5 blks) ==> 835725452:20492
12:56:40 INFO : Flash Jetson TX2 : 1205: SKP: 8192( 2 blks) ==> 835745944:12
12:56:40 ERROR : Flash Jetson TX2 : 1206: RAW: 16384( 4 blks) ==> 835745956:16396
12:56:40 ERROR : Flash Jetson TX2 : 1207: SKP: 4096( 1 blks) ==> 835762352:12
12:56:40 ERROR : Flash Jetson TX2 : 1208: RAW: 16384( 4 blks) ==> 835762364:16396
12:56:40 ERROR : Flash Jetson TX2 : 1209: SKP: 20480( 5 blks) ==> 835778760:12
12:56:40 ERROR : Flash Jetson TX2 : 1210: RAW: 4096( 1 blks) ==> 835778772:4108
12:56:40 INFO : Flash Jetson TX2 : 1211: SKP: 8192( 2 blks) ==> 835782880:12
12:56:40 INFO : Flash Jetson TX2 : 1212: RAW: 8192( 2 blks) ==> 835782892:8204
12:56:40 INFO : Flash Jetson TX2 : 1213: SKP: 4096( 1 blks) ==> 835791096:12rminal this :

and also later

13:11:36 ERROR : CUDA Toolkit for L4T : command safe_apt_install "sudo dpkg -i /opt/nvidia/deb_repos/cuda-repo-l4t-9-0-local_9.0.252-1_arm64.deb" 5; sleep 5; ; safe_apt_install "sudo apt-get -y install cuda-toolkit-9-0 " 5 finished with error
13:11:36 INFO : CUDA Toolkit for L4T :
13:11:37 ERROR : CUDA Toolkit for L4T : command terminated with error
13:11:37 ERROR : CUDA Toolkit for L4T : install 'CUDA Toolkit for L4T' failure, command < cd '/home/emmanuel/nvidia/nvidia_sdk/JetPack_3.3.1_Linux_GA_P3310' ; '/opt/nvidia/sdkmanager/resources/app/output/installUtils/adapter' -a='install' -c='eyJpZCI6Ik5WX0w0VF9DVURBX1RBUkdFVF9QT1NUX0lOU1RBTExfQ09NUCIsIm5hbWUiOiJDVURBIFRvb2xraXQgZm9yIEw0VCIsImRlc2NyaXB0aW9uIjoiQ1VEQSB0byBiZSBpbnN0YWxsZWQgb24gdGFyZ2V0LiBDVURBIGlzIGEg
...
13:11:37 ERROR : Unavailable components detected, please check log
13:11:37 ERROR : cuDNN on Target : cuDNN on Target Skipped. Due to its dependencies fail to install: CUDA Toolkit for L4T,
13:11:37 ERROR : TensorRT on Target : TensorRT on Target Skipped. Due to its dependencies fail to install: CUDA Toolkit for L4T,
13:11:37 ERROR : OpenCV on Target : OpenCV on Target Skipped. Due to its dependencies fail to install: CUDA Toolkit for L4T,
13:11:37 ERROR : VisionWorks on Target : VisionWorks on Target Skipped. Due to its dependencies fail to install: CUDA Toolkit for L4T,
13:11:37 ERROR : Multimedia API : Multimedia API Skipped. Due to its dependencies fail to install: CUDA Toolkit for L4T,

Update fails.

(With the previous sdk manager version I have the first block error but update arrived to the end.)

Laurent.

Hi laurent.delaon,

Please ignore flash ERROR message, it’s known issue, we will fix it on next release JetPack.
The image still can be flash success, right?
Please try to use eth0 IP address instead of USB device mode IP address (192.168.55.1) to install sdk components again. Thanks!

Hi Carolyuu,

Yes I arrived flashing the TX2 (the end is extremly slowly…)

But I can’t install VisionWork1.6 on host 16.04. (I ever arrive to do it on my previous falsh and I don’t renember really how I do it…)

Same pb with the previous release sdk (using l4t28.3.1, because it’s impossible to compile and rewrite code application over it’s release)

Is it normal when flashing to lose all installed application and package under ubuntu ?
The number 28.3.1 seem not evolving and the sdk flash anyway ?

regards.
Laurent.

Normal flash puts a brand new operating system in by using a “sample rootfs” (which is purely Ubuntu), and adding NVIDIA-specific drivers to this (and then it is referred to as “L4T”). The final flashed image is almost an exact duplicate of that content (some boot related files are added during flash depending on boot options). Previous content is lost.

If you were to replace files in the rootfs being flashed, then the booted system, after flash, would also have those changes (assuming they were not boot files, although with extra effort boot files can also be edited).

You could even replace the entire sample rootfs with a clone of the existing system, and then other than some boot files the final image would match your clone.

Do note that you cannot mix a clone from one release with a flash to a different release (other than for a minor patch release). Extra content related to CUDA is closely bound to other files in the system, and so a clone from R28.x could not be used to flash a working R32.x, but an R28.2.1 clone could be used on an R28.2.3 flash.

Actual cloning procedure depends on release. If you want to know your L4T release:

head -n 1 /etc/nv_tegra_release