Mass flash generation TX2NX JetPack 4.6.6

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

I can’t seem to get the nvmassflashgen.shscript to generate a working mass-flash directory. The command succeeds and it outputs a tbz2 file but whenever I try to flash one of these new modules using the generated mass flash directory, it fails with the output at the end of this post.

The command I’m running to generate the mass flashing configuration is the following (using the ONLINE method):

sudo ./nvmassflashgen.sh jetson-xavier-nx-devkit-tx2-nx mmcblk0p1

The Jetson that fails to flash has the following identification details:

Board ID(3636) version(302) sku(0001) revision(C.0)

Please advise, thank you.

Failing flash output (from sudo ./nvmflash.sh)

BR_CID: 0x81801001640e27071400000017ff84c0
RCM version 0X180001
Boot Rom communication completed
*** Boot Rom communication succeeded.

*** Checking applet
/opt/hwui/massflash_tx2nx/tegrarcm_v2 --instance 5-1 --isapplet
Applet version 01.00.0000
*** Checking applet succeeded.

*** Sending BCTs
/opt/hwui/massflash_tx2nx/tegrarcm_v2 --instance 5-1 --download bct_bootrom br_bct_BR.bct --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
Applet version 01.00.0000
Sending bct_bootrom
[................................................] 100%
Sending bct_mb1
[................................................] 100%
*** Sending BCTs succeeded.

*** Sending bootloader and pre-requisite binaries
/opt/hwui/massflash_tx2nx/tegrarcm_v2 --instance 5-1 --download blob blob.bin
Applet version 01.00.0000
Sending blob
[................................................] 100%
*** Sending bootloader and pre-requisite binaries succeeded.

*** Booting Recovery
/opt/hwui/massflash_tx2nx/tegrarcm_v2 --instance 5-1 --boot recovery
Applet version 01.00.0000
*** Booting Recovery succeeded.

*** Checking applet
/opt/hwui/massflash_tx2nx/tegrarcm_v2 --instance 5-1 --isapplet

*** Checking CPU bootloader
/opt/hwui/massflash_tx2nx/tegradevflash_v2 --instance 5-1 --iscpubl
Bootloader version 01.00.0000
Bootloader version 01.00.0000
*** Checking CPU bootloader succeeded.

*** Flashing the device
/opt/hwui/massflash_tx2nx/tegradevflash_v2 --instance 5-1 --pt flash.xml.bin --create
Bootloader version 01.00.0000
Erasing sdmmc_boot: 3 ......... [Done]
Writing partition secondary_gpt with gpt_secondary_0_3.bin
[................................................] 100%

Erasing sdmmc_user: 3 ......... [Done]
Writing partition master_boot_record with mbr_1_3.bin
[................................................] 100%
Writing partition primary_gpt with gpt_primary_1_3.bin
[................................................] 100%
000000000d0d0001:

*** Error: Flashing the device failed.
3

hello jlucier,

did you try adding board info to the command-line?
for instance,
$ sudo BOARDID=XXXX BOARDSKU=YYYY FAB=ZZZ FUSELEVEL=fuselevel_production ./nvmassflashgen.sh jetson-xavier-nx-devkit-tx2-nx mmcblk0p1

4

I tried the following command to generate the mass flashing directory. Using the newly generated mass flash setup failed with the same results:

sudo BOARDID=3636 BOARDSKU=0001 FAB=100 BOARDREV=C.0 FUSELEVEL=fuselevel_production ./nvmassflashgen.sh jetson-xavier-nx-devkit-tx2-nx mmcblk0p1

For clarity, I am trying to flash a Jetson TX2NX module with the newer DRAM chip.

This should be something you can reproduce on your end? Let me know what I can try next.

5

hello hello jlucier,

did you meant it’s a customize board, and, it’s now using different DDR configuration on the target?
you must have re-generate a new sdram configure file if you’re using different DRAM modules.

6

BTW,
please refer to Jetson Linux R32.7.6 | NVIDIA Developer, there’s overlay update (i.e. PCN211181) to support new memory.

8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.