Massflashgen.sh problems with TX2-4GB

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
,
1

I have run into a handful of problems preventing nvmassflash.sh from working with our system. It’s frustrating that Nvidia seems to have completely overlooked this module as a product they sell and support.

  1. The TX2-4GB is not even listed in the documentation. BOARDID=3489, FAB=A00, and SKU is 0888?

  2. nvmassflash.sh fails when trying to create the tarball because some files are missing.

    copying emmc_bootblob_ver.txt … succeeded.
    Error: gpt_secondary_0_3.bin does not exist.

I am not sure why the files are located in ./bootloader/signed/ but the script is only looking in ./bootloader/. I copied them to ./bootloader/ and then the nvmassflash.sh completed (after about 45 minutes).

  1. Running ./nvmflash.sh on the factory floor fails because the script does not properly look for the USB ID of a TX2-4GB device.

    	dir="$(dirname "${fn_devnum}")"
vendor="$(cat "${dir}/idVendor")"
if [ "${vendor}" != "0955" ]; then
	continue
fi
product="$(cat "${dir}/idProduct")"
case "${product}" in
"7721") ;;
"7f21") ;;
"7018") ;;
"7c18") ;;
"7121") ;;
"7019") ;;
"7e19") ;;
"7418") ;;  ### ADDED THIS LINE
*)

I added USB ID 7418 to the list, and now the board is detected, but it fails almost immediately with the following log:

*** Boot Rom communication
/home/ubuntu/secureboot/redacted_encrypt_signed/tegrarcm_v2 --instance 3-1 --chip 0x18 0 --rcm rcm_1_signed.rcm
BootRom is not running
*** Boot Rom communication succeeded.

*** Checking applet
/home/ubuntu/secureboot/redacted_encrypt_signed/tegrarcm_v2 --instance 3-1 --isapplet
USB communication failed.Check if device is in recovery
*** Error: Checking applet failed.

It should be noted that our carrier board does not have an EEPROM with Board ID, etc.

Can Nvidia provide some patches to this soon so we can implement this on our production line. Thanks.

3

Hi,

We will check this. But I cannot guarantee the patch will be released soon.
Sorry in advance.

6

Hi,

After you add 7418 to the ID list, could you try to use below command and see if it can work?

$ sudo BOARDID=3489 BOARDSKU=0888 FAB=300 FUSELEVEL=fuselevel_production ./nvmassflashgen.sh jetson-tx2-devkit-4gb mmcblk0p1

7

Essentially I was already running what you said to run. In your command, you specify FAB=300 whereas I was specifying A00. This seems to have made no difference. Same error:

*** Boot Rom communication
/media/ubuntu/8ae627b0-3f56-47d9-a935-5185438a266c/secureboot/mfi_jetson-tx2-devkit-4gb_encrypt_signed/tegrarcm_v2 --instance 3-2 --chip 0x18 0 --rcm rcm_1_signed.rcm
BootRom is not running
*** Boot Rom communication succeeded.

*** Checking applet
/media/ubuntu/8ae627b0-3f56-47d9-a935-5185438a266c/secureboot/mfi_jetson-tx2-devkit-4gb_encrypt_signed/tegrarcm_v2 --instance 3-2 --isapplet
USB communication failed.Check if device is in recovery
*** Error: Checking applet failed.

This is the exact command I’m running, since we need PKC and SBK files:

sudo BOARDID=3489 FAB=300 BOARDSKU=0888 FUSELEVEL=fuselevel_production ./nvmassflashgen.sh -x 0x18 -y SBKPKC -u test.pem -v test.sbk -r jetson-tx2-devkit-4gb mmcblk0p1

8

Hi,

If your board is fused one, then the case is different. We only resolved the non-fused case yet…

Please wait for our update.

9

Hi Wayne,

Do you have any updates on this?

10

Hi Undertow10,

Sorry for tale reply. This is still under debug.

12

massflash_32.4.4.tbz2.txt (415.3 KB)

Hi,

Sorry for late reply. Please download the attachment and rename the “txt” inside it.

Please use this overlay tarball on your Linux_for_Tegra driver package. It should fix your issue.