hello joolzgnux82,
we had fix the Nano APP partition cloning issue, which correct the failure of reading partition data from the the target device.
could you please upgrade to l4t-r32.3.1, please download the attachment, and overwrite below binary for verification.
$OUT/Linux_for_Tegra/bootloader/nvtboot_recovery.bin
thanks
devtalk1064479_r32.3.1_nvtboot_recovery.tar.gz (82.6 KB)
Tried and failed
encoder@encoder:~/Hämtningar/Jetson/Linux_for_Tegra/bootloader$ sudo ./tegraflash.py --bl cboot.bin --applet nvtboot_recovery.bin --chip 0x21 --cmd “read APP my_backup_image_APP.img”
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
[ 0.0027 ] Generating RCM messages
[ 0.0039 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm nvtboot_recovery.bin 0 0
[ 0.0050 ] RCM 0 is saved as rcm_0.rcm
[ 0.0057 ] RCM 1 is saved as rcm_1.rcm
[ 0.0057 ] List of rcm files are saved in rcm_list.xml
[ 0.0057 ]
[ 0.0057 ] Signing RCM messages
[ 0.0066 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0074 ] Assuming zero filled SBK key
[ 0.0130 ]
[ 0.0130 ] Copying signature to RCM mesages
[ 0.0143 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0157 ]
[ 0.0158 ] Boot Rom communication
[ 0.0167 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml
[ 0.0176 ] BR_CID: 0x321010016445c8460000000014fd83c0
[ 0.0938 ] RCM version 0X210001
[ 0.1821 ] Boot Rom communication completed
[ 1.1996 ]
[ 1.1998 ] Reading BCT from device for further operations
[ 1.1998 ] Retrieving storage infomation
[ 1.2032 ] tegrarcm --oem platformdetails storage storage_info.bin
[ 1.2062 ] Applet version 00.01.0000
[ 1.3648 ] Saved platform info in storage_info.bin
[ 1.4490 ]
[ 1.4492 ] Sending bootloader and pre-requisite binaries
[ 1.4528 ] tegrarcm --download ebt cboot.bin 0 0
[ 1.4560 ] Applet version 00.01.0000
[ 1.6202 ] Sending ebt
[ 1.6204 ] […] 100%
[ 1.9468 ] 00000004: Verification failed
[ 1.9490 ]
Error: Return value 4
Command tegrarcm --download ebt cboot.bin 0 0
encoder@encoder:~/Hämtningar/Jetson/Linux_for_Tegra/bootloader$ ll nvtboot_recovery.bin
-rwxr-xr-x 1 root root 184144 jan 14 14:27 nvtboot_recovery.bin
hello joolzgnux82,
please try to read APP partition and making back-up images through flash script files.
for example,
$ sudo ./flash -r -k APP -G backup.img jetson-nano-emmc mmcblk0p1
Thanks for that, it is now reading the flash, a bit slow but its reading.
What would be the correct command to flash a BLANK unit with this back APP image.
If you use the same release from which the clone is derived, and have your clone put in the “Linux_for_Tegra/bootloader/” directory with name “system.img”, then this image will be used without regenerating a new image whenever the “-r” option is used. As an example, assuming eMMC version:
sudo ./flash.sh <b>-r</b> jetson-nano-emmc mmcblk0p1
This is a full flash, but will use the image in place rather than creating a new image from the sample rootfs. A lot of partitions are required for boot since embedded systems do not have a BIOS, and thus you need those other partitions…but the trick is that those other partitions are standardized, and so the real customization is the rootfs.
Thanks again for all the help.
HI, I would like to zip the flash.sh and it’s binaries and use it to flash production module in the factory. I am trying to do following
1.Generate all the images by
– sudo sudo ./flash.sh --no-flash jetson-nano-emmc mmcblk0p1
2.zip Linux_for_Tegra without rootfs directory
3.try to unzip on another machine and run sudo sudo ./flash.sh -r jetson-nano-emmc mmcblk0p1
the script seems still looking for rotofs directory. is there any other way i can achieve this ?
Thanks
[quote=“linuxdev, post:10, topic:82908”]
The dd command itself won’t care what it runs on…this command is an exact bit-for-bit binary copy without any knowledge of what the underlying data is
[/quote]sudo ./flash.sh -r -k APP -G backup.img jetson-nano-qspi-sd mmcblk0p1, but error,
hello, I want clone jetson with sd img by
[0004.728] Number of retries left 2
[0004.731] Error mask set in wait for cmd complete with error 0x3 in HwSdmmcWaitForCommandComplete func at 278 line
[0004.741] Command complete wait failed with error 0x3 Interrupt 0x18001
[0004.748] Number of retries left 1
[0004.751] Error mask set in wait for cmd complete with error 0x3 in HwSdmmcWaitForCommandComplete func at 278 line
[0004.761] Command complete wait failed with error 0x3 Interrupt 0x18000
[0004.768] Number of retries left 0
[0004.771] Send command failed with 0x3
[0004.774] CMD8 send failed. Retrying CMD0/CMD8 (0)…
[0004.779] Error mask set in wait for cmd complete with error 0x3 in HwSdmmcWaitForCommandComplete func at 278 line
[0004.790] Command complete wait failed with error 0x3 Interrupt 0x18000
[0004.796] Number of retries left 4
[0004.799] Error mask set in wait for cmd complete with error 0x3 in HwSdmmcWaitForCommandComplete func at 278 line
[0004.810] Command complete wait failed with error 0x3 Interrupt 0x18000
[0004.816] Number of retries left 3
[0004.820] Error mask set in wait for cmd complete with error 0x3 in HwSdmmcWaitForCommandComplete func at 278 line
[0004.830] Command complete wait failed with error 0x3 Interrupt 0x18000
[0004.836] Number of retries left 2
[0004.840] Error mask set in wait for cmd complete with error 0x3 in HwSdmmcWaitForCommandComplete func at 278 line
[0004.850] Command complete wait failed with error 0x3 Interrupt 0x18000
[0004.856] Number of retries left 1
[0004.860] Error mask set in wait for cmd complete with error 0x3 in HwSdmmcWaitForCommandComplete func at 278 line
[0004.870] Command complete wait failed with error 0x3 Interrupt 0x18001
[0004.876] Number of retries left 0
[0004.879] Send command failed with 0x3
[0004.883] CMD55 send failed with error 0x3 in SdIdentifyCard func at 1870 line
[0004.890] SD Identify card failed with 0x3
[0004.894] SdIdentifyCard has failed with error 0x3 in NvTbootSdmmcInit func at 87 line
[0004.901] Sdmmc Init failed with 0x3 error
[0004.927] Error is 3