Not detecting device in RCM mode when trying to generate massflash image

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

Using JetPack4.3 .
I am trying to create a massflash image for JETSON_TX2_4GB.

I moved my device to recovery mode

lsusb 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
Bus 001 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 009: ID 0955:7418 NVidia Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and when running the mass flash script I see the following error:

$ sudo ./nvmassflashgen.sh jetson-tx2-4GB mmcblk0p1
================================================================================
|| Generate Massflash Image in the master host:                               ||
|| Requires the Jetson connected in RCM mode.                                 ||
================================================================================
0 Jetson devices in RCM mode. USB: 
* Error: No Jetson device found.
Connect 1 Jetson in RCM mode and rerun ./nvmassflashgen.sh jetson-tx2-4GB mmcblk0p1

Am I missing something in the process?
Are there any further checks I can do?

4

hello ofirtvf0z,

massflash was not implemented to support TX2-4GB with JetPack-4.3 / L4T-r32.3.1.
you may access the latest JetPack release, i.e. JetPack-4.4.1 to include the changes to make it works.
thanks

5

Got the same problem with JetPack-4.4.1

6

hello ofirtvf0z,

may I know your steps in detail.
for example,
are you download JetPack-4.4.1 release image with NVIDIA SDKManager for verification,
thanks

7

I have my backup image which is based on TX2-4GB with JetPack-4.3 / L4T-r32.3.1, with orbitty carrier board
My goal is to generate a mass flash image for this image, if it’s not possible I will upgrade my base image in order to generate a mass flash image.

Now I have tried to create a mass flash image with the following setups:

  1. using orbitty carrier board which was flashed with a L4T-r32.3.1 OS with the nvmassflashgen.sh of JetPack-4.3

  2. using orbitty carrier board which was flashed with a L4T-r32.3.1 OS with the nvmassflashgen.sh of JetPack-4.4.1

  3. using dev-kit carrier board which was flashed with a L4T 32.4.4 OS with the nvmassflashgen.sh of JetPack-4.4.1

all of them failed the same:

running lsusb I see the device:

lsusb 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
Bus 001 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 009: ID 0955:7418 NVidia Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and when running the mass flash script I see the following error:

$ sudo ./nvmassflashgen.sh jetson-tx2-4GB mmcblk0p1
================================================================================
|| Generate Massflash Image in the master host:                               ||
|| Requires the Jetson connected in RCM mode.                                 ||
================================================================================
0 Jetson devices in RCM mode. USB: 
* Error: No Jetson device found.
Connect 1 Jetson in RCM mode and rerun ./nvmassflashgen.sh jetson-tx2-4GB mmcblk0p1

I guess it’s either a bug or a configuration issue on my end

9

Hi ofirtvf0z,

Please reference this topic to download corrected Massflash utility for JetPack-4.4/4.4.1.

10

Hello ofirtvf0z -

Have you contacted CTI’s Tech Support Team? If you fill out our support request form, our tech team will help you troubleshoot. You can find the form here: Customer Support Form - Connect Tech Inc.

Let me know if you have any questions!
Jacki

11

I talked with CTI’s Tech Support Team and tey told me to run the following command:

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

using the corrected Massflash utility.

Afterwards:
I was able to generate a mass flash .tbz2 file
I extracted the output
I ran ./nvmflash.sh but it failed with an error

$ ./nvmflash.sh
Start flashing device: 1-1, PID: 32310
Ongoing processes: 32310
Ongoing processes:
Flash complete (WITH FAILURES)

how can I debug/fix this?

12

hello OfirMarcus,

please share the console logs of the failure messages for reference,
thanks

13

I am not sure where can I find additional logs.
It was fixed using CTI’s massflashgen files which have some changes

14

hello OfirMarcus,

please contact with CTI for the steps to gather bootloader messages,
you may also refer to Serial Console – NVIDIA Jetson TX2 for an example,
thanks