Jetson Nano Developer Kit - Cloning Issue [Jetpack 4.4] hangs on tegradevflash --oem platformdetails storage storage_info.bin

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

Hi,
I’ve recently tried to clone my Jetson Nano Developer Kit flashed with Jetpack 4.4.
Entering the comand:

sudo ./flash.sh -r -k APP -G backup.img jetson-nano-devkit mmcblk0p1

terminal hangs on “tegradevflash --oem platformdetails storage storage_info.bin” .

The whole log is reported below:

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.0423 ] Generating RCM messages
[ 0.0435 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm nvtboot_recovery.bin 0 0
[ 0.0445 ] RCM 0 is saved as rcm_0.rcm
[ 0.0451 ] RCM 1 is saved as rcm_1.rcm
[ 0.0451 ] List of rcm files are saved in rcm_list.xml
[ 0.0451 ]
[ 0.0451 ] Signing RCM messages
[ 0.0462 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0474 ] Assuming zero filled SBK key
[ 0.0568 ]
[ 0.0568 ] Copying signature to RCM mesages
[ 0.0580 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0597 ]
[ 0.0598 ] Boot Rom communication
[ 0.0609 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml
[ 0.0619 ] BootRom is not running
[ 0.2374 ]
[ 0.2375 ] Parsing partition layout
[ 0.2387 ] tegraparser --pt flash.xml.tmp
[ 0.2402 ]
[ 0.2403 ] Creating list of images to be signed
[ 0.2414 ] tegrahost --chip 0x21 0 --partitionlayout flash.xml.bin --list images_list.xml
[ 0.2478 ]
[ 0.2478 ] Generating signatures
[ 0.2489 ] tegrasign --key None --list images_list.xml --pubkeyhash pub_key.key
[ 0.2499 ] Assuming zero filled SBK key
[ 0.3396 ]
[ 0.3396 ] Send BCT from Host
[ 0.3397 ] Generating br-bct
[ 0.3410 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.cfg --chip 0x21 0
[ 0.3422 ] Copying Sdram info from 0 to 1 set
[ 0.3438 ] Copying Sdram info from 1 to 2 set
[ 0.3438 ] Copying Sdram info from 2 to 3 set
[ 0.3438 ]
[ 0.3439 ] Updating boot device parameters
[ 0.3449 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatedevparam flash.xml.bin
[ 0.3460 ] Warning: No sdram params
[ 0.3461 ]
[ 0.3461 ] Updating bl info
[ 0.3472 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updateblinfo flash.xml.bin --updatesig images_list_signed.xml
[ 0.3490 ]
[ 0.3490 ] Updating secondary storage information into bct
[ 0.3502 ] tegraparser --pt flash.xml.bin --chip 0x21 0 --updatecustinfo P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct
[ 0.3513 ]
[ 0.3514 ] Updating Odmdata
[ 0.3524 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatefields Odmdata =0x94000
[ 0.3535 ] Warning: No sdram params
[ 0.3537 ]
[ 0.3537 ] Get Signed section of bct
[ 0.3548 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --listbct bct_list.xml
[ 0.3559 ]
[ 0.3559 ] Signing BCT
[ 0.3583 ] tegrasign --key None --list bct_list.xml --pubkeyhash pub_key.key
[ 0.3594 ] Assuming zero filled SBK key
[ 0.3601 ]
[ 0.3601 ] Updating BCT with signature
[ 0.3611 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatesig bct_list_signed.xml
[ 0.3624 ]
[ 0.3624 ] Sending BCTs
[ 0.3635 ] tegrarcm --download bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct
[ 0.3654 ] Applet version 00.01.0000
[ 0.6333 ] Sending bct
[ 0.6334 ] […] 100%
[ 0.8119 ]
[ 0.8120 ] Retrieving storage infomation
[ 0.8132 ] tegrarcm --oem platformdetails storage storage_info.bin
[ 0.8143 ] Applet version 00.01.0000
[ 1.0852 ] 00000003: Could not initialize storage device
[ 1.5508 ]
[ 1.5521 ] tegradevflash --oem platformdetails storage storage_info.bin

2

Is this the SD card version, or the eMMC version? You might try your flash command again naming “jetson-nano-emmc” if a production model with eMMC, or “jetson-nano-qspi-sd” for the SD card model instead of “jetson-nano-devkit”. Don’t know if that will help or not, but it is easy to test.

3

This is the SD version (Developer Kit). I’ve already test all the possible configurations, with the same result. I’ve already tried to change USB port, cable and PC as well. I don’t find information about my issue!

4

Do you have an SD card slot on your host PC? If so, then there is no need to use recovery mode for clone. You could simply use dd on that partition.

As an example, if on your PC it turns out the SD card shows up as “/dev/mmcblk1” (I’m just making that up…monitor “dmesg --follow” as you connect the card and see what it is really called), then this would create a clone of the rootfs (the part which needs backup):
sudo dd if=/dev/mmcblk1p1 of=clone.bin bs=1M

Note the “p1”. This is the first partition, which is where the “APP” label is, and “APP” is rootfs. This will also be the only ext4 partition. If for some reason the SD used a name like “/dev/sdb”, then the same partition would be “/dev/sdb1”. Adjust for your case.

1 Like
5

Yes, I ought to try in this way. In another forum I found that JetsonNano SD does not support flash script. Thank you!!