MassFlash issue in TX2

Hi,
I created the massflashimage with
sudo ./nvmassflashgen.sh jetson-tx2 mmcblk0p1
created the image. But after creating this the board is not accessible.

Though the board is seems to be in REC mode, as per below command,

Linux_for_Tegra$ lsusb -d 0955:7c18
Bus 002 Device 031: ID 0955:7c18 NVidia Corp.
user-jrth@userjrth-Latitude-E6420:~/Desktop/Linux_for_Tegra$

But flash.sh script fails.
Linux_for_Tegra$ sudo ./flash.sh -r -k kernel-dtb jetson-tx2 mmcblk0p1
###############################################################################

L4T BSP Information:

R32 , REVISION: 3.1

###############################################################################
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.
Linux_for_Tegra$

WHy is the above behavior?
then after massflash image creation, why the board is not rebooting?

BR

Were you using a VM? USB disconnects and reconnects during a flash, and VMs usually have improper handling and the parent o/s takes the USB back. If not using a VM, were you using the supplied micro-B USB cable, or a charger cable?

I am using the supplied USB cable.
I am not using VM. It is Ubuntu host machine with 18.04

In that case, if the mass flash was otherwise set up correctly, it should work. Normally failure to identify the board is associated with a VM. On the other hand, I don’t know enough about mass flash to further debug, but is it possible the flash completed and it is just looking for another to flash? I only have one TX2 so I cannot test mass flash, and I am unsure if a mass flash offers to flash another after completing a flash (and completing a flash reboots the Jetson so it is no longer in recovery mode).

hello jk.t,

may I have your confirmation as below.

would you like to perform flashing to multiple Jetson devices simultaneously?
or, you would like to update kernel-dtb partition with the flash script?

Jerry,
Actually both.
Yes, we like to perform flashing to multiple devices. But initially I tried with single board.
At times when we change the device tree fles, we do update kernel-dtb.

Now, in this issue, I tried this flash script for flashing single board.

hello jk.t,

  1. $ sudo ./flash.sh -r -k kernel-dtb jetson-tx2 mmcblk0p1 this commands should works for update device tree partition. however, since it’s a partial update, had you perform a whole flash to flash the default image already?

  2. could you please have a try to generate system images “offline” by specify the board information.
    you may refer to documentation README_Massflash.txt located in the same folder for the instructions.
    please also enable “–showlogs” options to gather more details.
    for example, $ sudo ./nvmflash.sh --showlogs

$ sudo ./flash.sh -r -k kernel-dtb jetson-tx2 mmcblk0p1` this commands should works for update device tree partition. however, since it’s a partial update, had you perform a whole flash to flash the default image already?

Yes I did.

could you please have a try to generate system images “offline” by specify the board information.
you may refer to documentation README_Massflash.txt located in the same folder for the instructions.
please also enable “–showlogs” options to gather more details.
for example, $ sudo ./nvmflash.sh --showlogs.

I already followed that instruction and during that only I came across the issue specified in this post.

hello jk.t,

assume you’re able to flash the board with the following, $ sudo ./flash.sh -r jetson-tx2 mmcblk0p1
it has the same approach to parse board information.

may i have your confirmation,
thanks

yes I can flash using flash.sh script.

hello jk.t,

it should be JetPack-4.4 DP release bug that nvmassflash not functional, which works with JP-4.3.
we’re tracking this internally, will update the status after we come out conclusions.

BTW,
could you please have a try to update massflash script files as following for testing.
thanks

--- a/massflash/nvmassflashgen.sh
+++ b/massflash/nvmassflashgen.sh
@@ -722,6 +722,9 @@ gen_param()
                                i=$((i+1));
                                continue;
                        fi;
+                       if [[ ${a[$i]} =~ ^\-\- ]]; then
+                               break;
+                       fi;
                        na=`echo "${a[$((i+1))]}" | cut -d'.' -f1`;
                        suf=`echo "${a[$((i+1))]}" | cut -d'.' -f2`;
                        blobxmltxt+="<file name=\"";
1 Like