Jetson Xavier NX MassFlash using massflash blob - fails

Hi,

Recently I had asked about mass flashing of Jetson devices, as suggested(Programming Multiple modules at a time - #6) I have tried to flash two boards bit it failed and throughs error below:

*** Boot Rom communication
/home/hm/BSP/fsc/nx/20220111/testing/massfalsh-blob-online-method/mfi_jetson-xavier-nx-devkit-emmc/tegrarcm_v2 --instance 1-5 --chip 0x19 0 --rcm rcm_list_signed.xml
BootRom is not running
*** Boot Rom communication succeeded.

*** Checking applet
/home/hm/BSP/fsc/nx/20220111/testing/massfalsh-blob-online-method/mfi_jetson-xavier-nx-devkit-emmc/tegrarcm_v2 --instance 1-5 --isapplet
USB communication failed.Check if device is in recovery
*** Error: Checking applet failed.

I have followed below steps:
1)I have generated mfi_jetson-xavier-nx-devkit-emmc.tbz2 blob file from my custom BSP. Used online method ( command sudo ./nvmassflashgen.sh jetson-xavier-nx-devkit-emmc mmcblk0p1)
2) unzipped it and then tried flashing two NX modules and both throw above error.
followed the commands as instructed in the readme (flash command : ./nvmflash.sh)

I am able to flash individual boards with usual flash script on the same host machine and cable set and during mass flash both the modules are in recovery mode and listed as USB device.

Is your NX device a new one 16GB NX or not?

Hi, No. Its old NX module (900-83668-0000-000 8GB)

Could you just use massflash on single board usecase and try again?

Hi, sure i will try that and let you know

Hi,
I have connected single board and tried flashing with same mass flash script and still I get the same error:
/usr/bin/xauth: /home/hm/.Xauthority not writable, changes will be ignored
hm@hm:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
Bus 001 Device 002: ID 04ca:0061 Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
hm@hm:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
Bus 001 Device 002: ID 04ca:0061 Lite-On Technology Corp.
Bus 001 Device 050: ID 0955:7e19 NVidia Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
hm@hm:~$ cd /…/
hm@hm:~/…/testing$

nv_boot_control.conf xusb_sil_rel_fw_sigheader.encrypt
hm@hm:~/…/massfalsh-blob-offline-method/mfi_jetson-xavier-nx-devkit-emmc$ ./nvmflash.sh
Start flashing device: 1-1, PID: 31264
Ongoing processes: 31264
Ongoing processes:
Flash complete (WITH FAILURES)
hm@hm:~/…/massfalsh-blob-offline-method/mfi_jetson-xavier-nx-devkit-emmc$

Hi,

I have tried to flash same NX module on devkit using Xavier NX devkit but I get the same error.

hm@hm:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 060: ID 0955:7e19 NVidia Corp.
Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
Bus 001 Device 002: ID 04ca:0061 Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
hm@hm:~$ cd …/massfalsh-blob-offline-method/mfi_jetson-xavier-nx-devkit-emmc/
hm@hm:~…/massfalsh-blob-offline-method/mfi_jetson-xavier-nx-devkit-emmc$ ./nvmflash.sh
Start flashing device: 1-5, PID: 2914
Ongoing processes: 2914
Ongoing processes:
Flash complete (WITH FAILURES)
hm@hm:…/massfalsh-blob-offline-method/mfi_jetson-xavier-nx-devkit-emmc$

log:

*** Boot Rom communication
/massfalsh-blob-offline-method/mfi_jetson-xavier-nx-devkit-emmc/tegrarcm_v2 --instance 1-5 --chip 0x19 0 --rcm rcm_list_signed.xml
BootRom is not running
*** Boot Rom communication succeeded.

*** Checking applet
/massfalsh-blob-offline-method/mfi_jetson-xavier-nx-devkit-emmc/tegrarcm_v2 --instance 1-5 --isapplet
USB communication failed.Check if device is in recovery
*** Error: Checking applet failed.

Do you have other kind of jetson device to test on your side? Like TX2 or AGX Xavier. Just want to clarify whether this issue only to NX or other platforms too.

Hi,
I have tried with Nano as well. I can try with AGX Xavier. Since I have tried multiple custom carrier board, multiple NX modules, nano module, also on devkits, with different cable and host machines I dont think module or the set up has the issue.

Is your NX test on devkit or not?

yes it is NX Devkit, first I have tried on our carrier board and then tried on devkit

Hi,
For the flash command I have used sudo and now error message is a bit different:
/home/…/massfalsh-blob-offline-method/mfi_jetson-xavier-nx-devkit-emmc$ sudo ./nvmflash.sh --showlogs
[sudo] password for hm:
Start flashing device: 1-1, PID: 12031
X11 connection rejected because of wrong authentication.
Flash complete (WITH FAILURES)

below is the log file generated:

*** Boot Rom communication
/home/…/massfalsh-blob-offline-method/mfi_jetson-xavier-nx-devkit-emmc/tegrarcm_v2 --instance 1-1 --chip 0x19 0 --rcm rcm_list_signed.xml
BR_CID: 0x321010016445c8471800000008048580
RCM version 0X8
Boot Rom communication failed
*** Error: Boot Rom communication failed.

Hi, Any suggestion on this?

Hi WayneWWW,
I have tried AGX Xavier as well and no change, any suggestion?

You mean try AGX xavier with massflash tool and it cannot flash it either?

Hi,

Yes, I have tried on AGX Xavier Devkit and our carrier board and can not flash

Which jetpack release is in use here?

I have used L4T 32.6.1 Jetpack 4.6

I will try with my xavier nx/agx.

In the meantime, if you have other host machines, please also try them.

Hi,

We cannot reproduce this issue on our side.

Please try a different host/usb port on your side and try again.