Backup nano production emmc (JN30)

Hi,

I’m desperately trying to create an image backup of my jetson nano production module mounted on a JN30 carrier board using:

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

Unfortunately it keeps hanging on this part:

...
[   0.1311 ] 
[   0.1311 ] Get Signed section of bct
[   0.1317 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --listbct bct_list.xml
[   0.1324 ] 
[   0.1325 ] Signing BCT
[   0.1337 ] tegrasign --key None --list bct_list.xml --pubkeyhash pub_key.key
[   0.1344 ] Assuming zero filled SBK key
[   0.1350 ] 
[   0.1351 ] Updating BCT with signature
[   0.1362 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatesig bct_list_signed.xml
[   0.1380 ] 
[   0.1381 ] Sending BCTs
[   0.1392 ] tegrarcm --download bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct
[   0.1400 ] Applet version 00.01.0000
[   0.1540 ] Sending bct
[   0.1541 ] [................................................] 100%
[   0.2269 ] 
[   0.2270 ] Retrieving storage infomation
[   0.2305 ] tegrarcm --oem platformdetails storage storage_info.bin
[   0.2330 ] Applet version 00.01.0000
[   0.2491 ] 00000004: Failed to get an accessor of secondary boot device
[   0.2502 ] 
[   0.2547 ] tegradevflash --oem platformdetails storage storage_info.bin

Anyone knows what’s wrong? I was able to flash the board properly, using l4t r32.2.1.

hello Error323,

it’s a known issue that image backup functionality not working with l4t-r32.2.1
you may check discussion threads, such as Topic 1065012, and Topic 1064479 as see-also.

you could have an alternative way to use dd commands to clone APP partition,
therefore, you should replace it with $OUT/Linux_for_Tegra/bootloader/system.img.

you’ll still need local machine to perform script to flash the other Nano boards.
please also do remember to add “-r” commands, which skip building and reuse existing system.img.
thanks

Hi JerryChang,

Thank you for your answer. Does this imply that for higher versions of l4t it does work properly?

hello Error323,

it’s a regression for image backup functionality starting from l4t-r32.x
we’re not yet root cause the failure and it’s still under investigation.
please working with dd commands to clone APP partition as your temporary approach.
thanks