Difference between revisions of "Jetson/TX2 Cloning"

From eLinux.org
Jump to: navigation, search
(Created page with "Using the L4T tools, it is possible to create a carbon copy of Jetson TX1 by backing-up and restoring the eMMC partitions.<br /> The Jetson must be connected to a remote PC o...")
 
m
 
Line 10: Line 10:
  
 
In this case, we call the file system.img, so the same flash.sh script can be re-used to format and flash other Jetson's with the image.
 
In this case, we call the file system.img, so the same flash.sh script can be re-used to format and flash other Jetson's with the image.
 +
 +
Note that if you receive an error from the script about unrecognized -G option, replace your flash.sh with the script from [https://devtalk.nvidia.com/default/topic/1000105/jetson-tx2/tx2-cloning/post/5111893/#5111893 this post].
  
 
== Restoring the Image ==
 
== Restoring the Image ==

Latest revision as of 07:04, 20 April 2017

Using the L4T tools, it is possible to create a carbon copy of Jetson TX1 by backing-up and restoring the eMMC partitions.

The Jetson must be connected to a remote PC over USB and entered into recovery mode. The TX2 cloning procedure is slightly different from TX1.

Cloning the Image

cd into the directory containing the L4T installation package on the host PC. The command below will save the TX2's eMMC image to the specified file on the host.

 $ sudo ./flash.sh -r -k APP -G system.img jetson-tx2 mmcblk0p1

In this case, we call the file system.img, so the same flash.sh script can be re-used to format and flash other Jetson's with the image.

Note that if you receive an error from the script about unrecognized -G option, replace your flash.sh with the script from this post.

Restoring the Image

The recommended way to restore multiple units with different serial numbers is to save the image above as "system.img" and use the head L4T flashing script, flash.sh, with the -r option (to reuse your backed-up system.img without rebuilding the vanilla image from scratch):

  $ sudo ./flash.sh -r jetson-tx2 mmcblk0p1

Discussion Thread

see https://devtalk.nvidia.com/default/topic/1000105/?comment=5111893