Flash Jetson TX2 error : CPU Bootloader is not running on device && Failed to execute commands with GenericInstaller

Hi, everyone. I am trying to reflash TX2 with VMware ubuntu 16.04, but failed this time. The terminal in SDK Manager report " Flash Jetson TX2: [ 2.7596 ] CPU Bootloader is not running on device." and “Flash Jetson TX2: Failed to execute commands with GenericInstaller”. But, the “lsusb” command show that the host machine can detect NVIDIA Crop.Could somebody help me please?

04:55:34 DEBUG: Flash Jetson TX2: using adapter to install NV_L4T_FLASH_TX2_WITH_OS_IMAGE_COMP@JETSON_TX2 to /home/burlon/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_TX2
04:55:34 INFO: Flash Jetson TX2: [ Disk Avail:80.27 GB ]
04:55:34 INFO: Flash Jetson TX2: Using GenericInstaller to Install NV_L4T_FLASH_TX2_WITH_OS_IMAGE_COMP
04:55:34 INFO: Flash Jetson TX2: change working directory to /home/burlon/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_TX2/Linux_for_Tegra
04:55:34 INFO: Flash Jetson TX2: [ Component Install Started ]
04:55:34 INFO: Flash Jetson TX2: current working directory is /home/burlon/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_TX2/Linux_for_Tegra
04:55:34 INFO: Flash Jetson TX2: exec_command [host]:
04:55:34 INFO: Flash Jetson TX2: **********************
04:55:34 INFO: Flash Jetson TX2: #!/bin/bash
04:55:34 INFO: Flash Jetson TX2: set -e
04:55:34 INFO: Flash Jetson TX2: set -e
04:55:34 INFO: Flash Jetson TX2: if [ -e ./bootloader/system.img ]; then
04:55:34 INFO: Flash Jetson TX2: echo sudo ./flash.sh --no-systemimg jetson-tx2 mmcblk0p1
04:55:34 INFO: Flash Jetson TX2: sudo ./flash.sh --no-systemimg jetson-tx2 mmcblk0p1
04:55:34 INFO: Flash Jetson TX2: else
04:55:34 INFO: Flash Jetson TX2: echo sudo ./flash.sh jetson-tx2 mmcblk0p1
04:55:34 INFO: Flash Jetson TX2: sudo ./flash.sh jetson-tx2 mmcblk0p1
04:55:34 INFO: Flash Jetson TX2: fi
04:55:34 INFO: Flash Jetson TX2: sleep 20
04:55:34 INFO: Flash Jetson TX2: **********************
04:55:34 INFO: Flash Jetson TX2: exec_command: /tmp/tmp_NV_L4T_FLASH_TX2_WITH_OS_IMAGE_COMP.sh
04:55:34 INFO: Flash Jetson TX2: sudo ./flash.sh jetson-tx2 mmcblk0p1
04:55:34 INFO: Flash Jetson TX2: [host] [sudo] password for burlon:
04:55:34 INFO: Flash Jetson TX2:
04:55:34 INFO: Flash Jetson TX2: ###############################################################################
04:55:34 INFO: Flash Jetson TX2: # L4T BSP Information:
04:55:34 INFO: Flash Jetson TX2: # R32 , REVISION: 4.3
04:55:34 INFO: Flash Jetson TX2: ###############################################################################
04:55:34 INFO: Flash Jetson TX2: # Target Board Information:
04:55:34 INFO: Flash Jetson TX2: # Name: jetson-tx2, Board Family: t186ref, SoC: Tegra 186,
04:55:34 INFO: Flash Jetson TX2: # OpMode: production, Boot Authentication: NS,
04:55:34 INFO: Flash Jetson TX2: ###############################################################################
04:55:34 INFO: Flash Jetson TX2: ./tegraflash.py --chip 0x18 --applet “/home/burlon/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_TX2/Linux_for_Tegra/bootloader/mb1_recovery_prod.bin” --skipuid --cmd “dump eeprom boardinfo cvm.bin”
04:55:35 INFO: Flash Jetson TX2: Welcome to Tegra Flash
04:55:35 INFO: Flash Jetson TX2: version 1.0.0
04:55:35 INFO: Flash Jetson TX2: Type ? or help for help and q or quit to exit
04:55:35 INFO: Flash Jetson TX2: Use ! to execute system commands
04:55:35 INFO: Flash Jetson TX2:
04:55:35 INFO: Flash Jetson TX2: [ 0.0104 ] Generating RCM messages
04:55:35 INFO: Flash Jetson TX2: [ 0.0257 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x18 0 --download rcm /home/burlon/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_TX2/Linux_for_Tegra/bootloader/mb1_recovery_prod.bin 0 0
04:55:35 INFO: Flash Jetson TX2: [ 0.0265 ] RCM 0 is saved as rcm_0.rcm
04:55:35 INFO: Flash Jetson TX2: [ 0.1478 ] RCM 1 is saved as rcm_1.rcm
04:55:35 INFO: Flash Jetson TX2: [ 0.1478 ] List of rcm files are saved in rcm_list.xml
04:55:35 INFO: Flash Jetson TX2: [ 0.1478 ]
04:55:35 INFO: Flash Jetson TX2: [ 0.1479 ] Signing RCM messages
04:55:35 INFO: Flash Jetson TX2: [ 0.2561 ] tegrasign_v2 --key None --list rcm_list.xml --pubkeyhash pub_key.key
04:55:35 INFO: Flash Jetson TX2: [ 0.2570 ] Assuming zero filled SBK key
04:55:35 INFO: Flash Jetson TX2: [ 0.2719 ]
04:55:35 INFO: Flash Jetson TX2: [ 0.2720 ] Copying signature to RCM mesages
04:55:35 INFO: Flash Jetson TX2: [ 0.2731 ] tegrarcm_v2 --chip 0x18 0 --updatesig rcm_list_signed.xml
04:55:35 INFO: Flash Jetson TX2: [ 0.2743 ]
04:55:35 INFO: Flash Jetson TX2: [ 0.2743 ] Boot Rom communication
04:55:35 INFO: Flash Jetson TX2: [ 0.2751 ] tegrarcm_v2 --chip 0x18 0 --rcm rcm_list_signed.xml --skipuid
04:55:35 INFO: Flash Jetson TX2: [ 0.2759 ] RCM version 0X180001
04:55:38 INFO: Flash Jetson TX2: [ 0.3651 ] Boot Rom communication completed
04:55:38 INFO: Flash Jetson TX2: [ 1.3825 ]
04:55:38 INFO: Flash Jetson TX2: [ 2.3857 ] tegrarcm_v2 --isapplet
04:55:38 INFO: Flash Jetson TX2: [ 2.3877 ] Applet version 01.00.0000
04:55:38 INFO: Flash Jetson TX2: [ 2.5288 ]
04:55:38 INFO: Flash Jetson TX2: [ 2.5300 ] Retrieving EEPROM data
04:55:38 INFO: Flash Jetson TX2: [ 2.5300 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/burlon/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_TX2/Linux_for_Tegra/bootloader/cvm.bin
04:55:38 INFO: Flash Jetson TX2: [ 2.5312 ] Applet version 01.00.0000
04:55:38 INFO: Flash Jetson TX2: [ 2.6673 ] 00000000000a0111:
04:55:38 INFO: Flash Jetson TX2: [ 2.7321 ]
04:55:38 INFO: Flash Jetson TX2: [ 2.7572 ] tegradevflash_v2 --oem platformdetails eeprom cvm /home/burlon/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_TX2/Linux_for_Tegra/bootloader/cvm.bin
04:55:38 INFO: Flash Jetson TX2: [ 2.7596 ] CPU Bootloader is not running on device.
04:55:38 INFO: Flash Jetson TX2: [ 2.8973 ]
04:55:38 INFO: Flash Jetson TX2: Error: Return value 4
04:55:38 INFO: Flash Jetson TX2: Command tegradevflash_v2 --oem platformdetails eeprom cvm /home/burlon/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_TX2/Linux_for_Tegra/bootloader/cvm.bin
04:55:38 INFO: Flash Jetson TX2: Reading board information failed.
04:55:38 INFO: Flash Jetson TX2: [ Component Install Finished with Error ]
04:55:38 INFO: Flash Jetson TX2: [ 264.00 KB used. Disk Avail: 80.27 GB ]
04:55:38 INFO: Flash Jetson TX2: [ NV_L4T_FLASH_TX2_WITH_OS_IMAGE_COMP Install took 4s ]
04:55:38 INFO: Flash Jetson TX2:
04:55:38 SUMMARY: Flash Jetson TX2: Failed to execute commands with GenericInstaller

During flash the Jetson’s USB will repeatedly disconnect and reconnect. VMs tend to fail to pick up the reconnect even if they original could detect the Jetson. Some people get this to work by configuring to make the Jetson’s USB always go to the VM instead of parent o/s, but is not officially supported (there is nothing Jetson can do about a VM’s settings).

Thanks a lot. I will try to flash it with an ubuntu host instead of a VM. Actually, I am also very interested about how to configure VM for making it work just like you mentioned.

Every VM is different, and you would need to ask the VM support people about this. If you give specific VM details, then someone who has already done this might reply.

Hi, I had tried to flash tx2 with ubuntu16.04 machine, but still failed, neither jetpack4.4 or other version. And terminal always report “Failed to execute commands with GenericInstaller” and “CPU Bootloader is not running on device”. I think maybe my TX2 is broken, it had be used for few years, and the guys in our lab did not treat TX2 properly in the daily time.
Anyway, thank you so much for your kindness.

Recent releases need an Ubuntu 18.04 host. 16.04 has not been used since the R28.x L4T releases. However, the “CPU Bootloader is not running on device” is still most likely a VM issue if you are using a VM.

That is why I think It is werid. I flashed jetpack3.3 to TX2 by using ubuntu16.04 host, and it just reported “Failed to execute commands with GenericInstaller” now. I can not even kown why. Can I flash TX2 with a SD card just like flashing Jetson Nano?

15:13:12 SUMMARY: Drivers for Jetson: Install completed successfully.
15:25:06 SUMMARY: File System and OS: Install completed successfully.
15:25:32 SUMMARY: Device Mode Host Setup in Flash: Install completed successfully.
15:25:34 SUMMARY: Flash Jetson TX2: Failed to execute commands with GenericInstaller
15:25:34 SUMMARY: NVIDIA Container Runtime with Docker integration (Beta): Depends on failed component
15:25:34 SUMMARY: Multimedia API: Depends on failed component
15:25:34 SUMMARY: TensorRT on Target: Depends on failed component
15:25:34 SUMMARY: NVIDIA Container Runtime with Docker integration (Beta): Depends on failed component
15:25:34 SUMMARY: Multimedia API: Depends on failed component
15:25:34 SUMMARY: VisionWorks on Target: Depends on failed component
15:25:34 SUMMARY: NVIDIA Container Runtime with Docker integration (Beta): Depends on failed component
15:25:34 SUMMARY: VPI on Target: Depends on failed component
15:25:34 SUMMARY: CUDA Toolkit for L4T: Depends on failed component

Assuming a non-VM, the optional components are never installed during the actual flash. What happens is that if you have checked to flash, then flash occurs first, and the Jetson then fully reboots. The Jetson automatically boots after the completion of a flash.

Once fully booted, then optional component install occurs over ssh. This implies you need to know the name/pass to log in with. If you are using L4T R28.x or older, then probably this is the default “nvidia”/“nvidia”. If you are using R32.x or newer, then this account will not exist until you complete first boot setup and create that user name/pass (there is actually a law in California about not providing a default name/pass, and is the origin of this change in procedure).

For a given optional install to succeed it is necessary for full network access. It looks like flash succeeded. Unfortunately, I do not know the specific meaning of:

15:25:34 SUMMARY: Flash Jetson TX2: Failed to execute commands with GenericInstaller

Someone from NVIDIA would need to comment on “GenericInstaller”. In general though, from the errors of dependencies, I am guessing this means you have some sort of network failure or route issue. Do your host and Jetson have internet access during the flash?

Thanks again for your patient. I had connected my ubuntu bost and TX2 in the same route, and yes, they do have internet access during the flash.
Someone tell me that maybe I can try to flash TX2 bu using SD card just like Nano, but I can not find the SD card image of TX2 in Jetson download center, and it seems that this is not an official method to flash TX2.
I wonder konw that can I flash TX2 with SD card method? And how can I get the SD card image of TX2?

Units with eMMC are very different in how they boot versus an SD card model. There is no such thing as an SD card image for the units with eMMC (Nano has versions which are purely SD card…the production modules with eMMC are different electrical designs and not just a difference in having an SD card slot). There are some options for flash, but those options and how they were are likely very different than how you might expect. For a TX2 you will find SD card can complicate things, and will actually be more difficult to get working correctly.

Hopefully someone from NVIDIA can comment on this:
15:25:34 SUMMARY: Flash Jetson TX2: Failed to execute commands with GenericInstaller

I met with the same issue but its not regarding memory card. I was trying to flash the jetson tx2 with jetpack 4.4.1.

The “Failed to execute commands with GenericInstaller” is an error I don’t know the cause of. If this is occurring for a TX2 dev kit, then someone from NVIDIA may need to comment on that specific error. Any details you might have, such as the logs, would probably be useful.

You can try to figure out whether this error comes from

  1. Flash error

or

  1. Installing sdk error.

“Failed to execute commands with GenericInstaller” is a very general error that we cannot tell what is going on.
Are you able to tell whether sdkmanager starts to flash your board or not? The screenshot you just shared looks like the sdkmanager is still preparing the driver package. I guess the flash is not yet started. Could you confirm that?

Thank you all for your kind reply, but I have already bought the NX.

Exactly, flashing not started, still at package preparation. Soon after the stage mentioned in the image, the process gets terminated.

I think you can try manual setup first.

  1. Go to the download center.
    https://developer.nvidia.com/embedded/downloads

  2. Download the l4t rootfs.

L4T Sample Root File System 32.4.4 2020/10/21

  1. Download the l4t driver package.

L4T Jetson Driver Package 32.4.4 2020/10/21

  1. Copy (with sudo) the root file system to the Linux_for_Tegra/rootfs you just downloaded from driver package.

  2. Refer to Quick start guide. For further steps.

L4T Quick Start Guide 32.4.4 2020/10/21

If you want us to help check sdkmanger log, please check the picture you shared. There is an “EXPORT LOGS” button here.

image

Please dump the full log and share it here.

I did the manual setup and got an error regarding the ownership of the folder 'file system'. I checked the script apply_binaries it was actually verifying the ownership of the folder. My folder ownership couldn't be modified to root root and that was the issue. I created a folder in /home/{user_name} and repeated the steps mentioned in the Quick Start Guide. Now the Jetson tx2 flash is success.
Thank you all for the support.

1 Like

hello sir, I have the same problem, and sdkmanager log is shown as follows:


I did the manual setup. What’s shown in the terminal as follows:

It looked like the command ‘sudo ./apply_binaries.sh’ was the issue. But I didn’t know how to solve this problem. I really needed your help.
My computer was a dual system, and the Ubuntu partition had insufficient storage space, so the working path was on another disk. What’s more, I used zsh and I was in China.Below was sdkmanager log:
SDKM_logs_JetPack_4.4.1_Linux_for_Jetson_TX2_2020-11-21_23-18-29.zip (318.1 KB)