Cloning TK1

Autonomous Machines Jetson & Embedded Systems Jetson TK1
#1

Dear team,
I managed to flash the tk1 multiple times successfully, however now that the project is completed I would
like to have a copy of my system. When I try to flash it, using the following command, it gets stuck.

~/JetPackTK1-1.2/Linux_for_Tegra/bootloader$ sudo ./nvflash --read 12 system.img --bl fastboot.bin --go
Nvflash 4.13.0000 started
BR_CID: 0x34001001740de1001c0000000c060480
rcm version 0X400001
System Information:
chip name: unknown
chip id: 0x40 major: 1 minor: 1
chip sku: 0x0
chip uid: 0x00000001740de1001c0000000c060480
macrovision: disabled
hdcp: disabled
jtag: disabled
sbk burned: false
board id: 0
warranty fuse: 0
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0

RCM communication completed
downloading bootloader – load address: 0x83d88000 entry point: 0x83d88000
sending file: fastboot.bin

  • 594363/594363 bytes sent
    fastboot.bin sent successfully
    waiting for bootloader to initialize

I’m using a short usb cable.

Update: after waiting a while, I received the following error:
usb read error (32): Broken pipe
bootloader failed NvError 0x0
command failure/warning: bootloader download failed

#2

Is there really a partition number 12? What do you see from:

sudo gdisk -l /dev/mmcblk0

I don’t know if this would cause the failure message you saw, but perhaps. Try this instead, using a label:

sudo ./nvflash --read APP system.img --bl ardbeg/fastboot.bin --go
#3

I chose #12 because in the flash.cfg it says name=APP id=12 and it has the biggest size

this is the output of the sudo gdisk -l /dev/mmcblk0

GPT fdisk (gdisk) version 0.8.8

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/mmcblk0: 30777344 sectors, 14.7 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): A81E231F-7B1C-C564-1473-5AC55E4B7963
Partition table holds up to 9 entries
First usable sector is 94208, last usable sector is 30773247
Partitions will be aligned on 2048-sector boundaries
Total free space is 0 sectors (0 bytes)

Number Start (sector) End (sector) Size Code Name
1 94208 29454335 14.0 GiB 0700 APP
2 29454336 29462527 4.0 MiB 0700 DTB
3 29462528 29593599 64.0 MiB 0700 EFI
4 29593600 29601791 4.0 MiB 0700 USP
5 29601792 29609983 4.0 MiB 0700 TP1
6 29609984 29618175 4.0 MiB 0700 TP2
7 29618176 29626367 4.0 MiB 0700 TP3
8 29626368 29630463 2.0 MiB 0700 WB0
9 29630464 30773247 558.0 MiB 0700 UDA

#4

I don’t know how the config file might be “optimized” or reordered during flash, but so far as I know rootfs always has label “APP”. In all cases I know of so far from TK1 through Xavier this ends up as partition 1. I suppose customization might change this, but “1” is probably what you want for this case. The nice thing about a label, should the label exist, using this as a specification will work out correctly regardless of where the partition might migrate.

Did clone work using either a “1” or “APP”?