jetpack4.2 fail to install SDK components on my tx2

Hi,
I follow the step-by-step instruction to upgrade my tx2, but always failed at the step of installing SDK components. I ended up with logs like below
base_sigheader.dtb.encrypt
17:00:28 INFO : Flash Jetson TX2 : [ 185.3821 ] […] 100%
17:00:28 INFO : Flash Jetson TX2 : [ 185.3952 ] Writing partition kernel-dtb_b with tegra186-quill-p3310-1000-c03-00-base_sigheader.dtb.encrypt
17:00:28 INFO : Flash Jetson TX2 : [ 185.4016 ] […] 100%
17:00:28 INFO : Flash Jetson TX2 : [ 185.4208 ]
17:00:28 INFO : Flash Jetson TX2 : [ 185.4216 ] tegradevflash_v2 --write BCT br_bct_BR.bct
17:00:28 INFO : Flash Jetson TX2 : [ 185.4221 ] Bootloader version 01.00.0000
17:00:28 INFO : Flash Jetson TX2 : [ 185.4238 ] Writing partition BCT with br_bct_BR.bct
17:00:28 INFO : Flash Jetson TX2 : [ 185.4239 ] […] 100%
17:00:28 INFO : Flash Jetson TX2 : [ 185.4823 ]
17:00:28 INFO : Flash Jetson TX2 : [ 185.4876 ] tegradevflash_v2 --write MB1_BCT mb1_cold_boot_bct_MB1_sigheader.bct.encrypt
17:00:28 INFO : Flash Jetson TX2 : [ 185.4882 ] Bootloader version 01.00.0000
17:00:28 INFO : Flash Jetson TX2 : [ 185.4900 ] Writing partition MB1_BCT with mb1_cold_boot_bct_MB1_sigheader.bct.encrypt
17:00:28 INFO : Flash Jetson TX2 : [ 185.4904 ] […] 100%
17:00:28 INFO : Flash Jetson TX2 : [ 185.5576 ]
17:00:28 INFO : Flash Jetson TX2 : [ 185.5586 ] tegradevflash_v2 --write MB1_BCT_b mb1_cold_boot_bct_MB1_sigheader.bct.encrypt
17:00:28 INFO : Flash Jetson TX2 : [ 185.5591 ] Bootloader version 01.00.0000
17:00:28 INFO : Flash Jetson TX2 : [ 185.5609 ] Writing partition MB1_BCT_b with mb1_cold_boot_bct_MB1_sigheader.bct.encrypt
17:00:28 INFO : Flash Jetson TX2 : [ 185.5613 ] […] 100%
17:00:28 INFO : Flash Jetson TX2 : [ 185.6176 ]
17:00:28 INFO : Flash Jetson TX2 : [ 185.6176 ] Flashing completed
17:00:28 INFO : Flash Jetson TX2 :
17:00:28 INFO : Flash Jetson TX2 : [ 185.6177 ] Coldbooting the device
17:00:28 INFO : Flash Jetson TX2 : [ 185.6189 ] tegradevflash_v2 --reboot coldboot
17:00:28 INFO : Flash Jetson TX2 : [ 185.6196 ] Bootloader version 01.00.0000
17:00:30 INFO : Flash Jetson TX2 : [ 185.6258 ]
17:00:30 INFO : Flash Jetson TX2 : *** The target t186ref has been flashed successfully. ***
17:00:30 INFO : Flash Jetson TX2 : Reset the board to boot from internal eMMC.
17:00:30 INFO : Flash Jetson TX2 :
17:00:30 INFO : Flash Jetson TX2 : exec_command: sleep 10
17:00:40 INFO : Flash Jetson TX2 : [ Component Install Finished Successfully ]
17:00:40 INFO : Flash Jetson TX2 : [ 120.00 KB used. Disk Avail: 28.27 GB ]
17:00:40 INFO : Flash Jetson TX2 : [ NV_L4T_FLASH_TX2_WITH_OS_IMAGE_COMP Install took 11m1s ]
17:00:40 INFO : Flash Jetson TX2 : command finished successfully
17:00:41 INFO : Flash Jetson TX2 : install ‘Flash Jetson TX2’ success
17:05:55 DEBUG : running command < ip addr | grep 192.168.55.100/24 >
17:05:55 ERROR : command terminated with error
17:05:55 DEBUG : running command < lsusb | grep “NVidia Corp” >
17:05:55 INFO : Bus 001 Device 045: ID 0955:7020 e[01;31me[KNVidia Corpe[me[K.
17:05:55 INFO : command finished successfully
17:05:56 ERROR : Jetson device is in recovery mode.
17:14:45 INFO : Device Mode Host Setup in Target SDK : install ‘Device Mode Host Setup in Target SDK’ Skipped
17:14:45 INFO : DateTime Target Setup : install ‘DateTime Target Setup’ Skipped
17:14:45 INFO : CUDA Toolkit for L4T : install ‘CUDA Toolkit for L4T’ Skipped
17:14:46 INFO : cuDNN on Target : install ‘cuDNN on Target’ Skipped
17:14:46 INFO : TensorRT on Target : install ‘TensorRT on Target’ Skipped
17:14:46 INFO : OpenCV on Target : install ‘OpenCV on Target’ Skipped
17:14:46 INFO : VisionWorks on Target : install ‘VisionWorks on Target’ Skipped
17:14:46 INFO : Multimedia API : install ‘Multimedia API’ Skipped
17:14:47 INFO : All done!
error.png
err.log (120 KB)

I have attached the error.log and a screenshot “error.png” when the annoying prompt “jetson device is in recovery mode” kept showing up, making me have to cancel installation.

Please let me know how to fix this.
SDKM_logs_JetPack_4.2_Linux_for_Jetson_TX2_04012019_1649.zip (70.8 KB)

Hi HooverLv,

From the log, that USB ID (7020) is the USB ID of a booted Jetson system, not the USB ID of a Jetson in recovery mode, and hence the ERROR message is incorrect. Would you please try with other USB cable to see if issue still can be reproduced?

Thanks

Hi HooverLv,

Seems L4T USB device mode is not working. Could you please try the below steps?

  1. Run “dmesg” on the host and provide the full output. This might show any errors the host might have had when enumerating the Jetson USB device.

Now, connect jetson device with a ethernet cable, get its IP address, ssh to Jetson and:

  1. Run “journalctl -u nv-l4t-usb-device-mode” to show any errors configuring the USB device mode service on Jetson, during boot.

  2. As root, run “/opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode-stop.sh”. This is expected to show some errors; ignore them.

  3. As root, run “bash -x /opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode.sh” and provide the entire output that prints. This should (a) show the same errors as in (2) above, and/or (b) actually make L4T USB device mode work, if the reason it failed the first time was due to some missing dependency that wasn’t available right when the script ran at boot.

The above step did not work, indicates that file does not exist, am using Jetson TX2 Ubuntu 18.x, on MAC via VMWare Fusion 11.0. installed SDK manager for Jetson TX2, Flash step after forced recovery mode in manual install, throws error after 2 min, indicating SDK manager lost connection to target device, strange as lsusb still works… The error message “Flash Jetson TX2: Lost connection”. It exits with 255, seem to continue with installation for some reason ignoring that, and fails as follows … errors such as ERROR : Flash Jetson TX2 : NV_L4T_FLASH_TX2_WITH_OS_IMAGE_COMP command sudo ./flash.sh jetson-tx2 mmcblk0p1 finished with error… strange tigra_flash.py and INFO : Flash Jetson TX2 : ./tegraflash.py --chip 0x18 --applet “/home/mouli/nvidia/nvidia_sdk/JetPack_4.2_Linux_P3310/Linux_for_Tegra/bootloader/mb1_recovery_prod.bin” --skipuid --cmd "dump eeprom boardinfo cvm.bin failed ERROR : Flash Jetson TX2 : : No such file or directory for env and python… strange

VMs usually fail and are not supported. A VM can be made to work, but typically the Jetson will disconnect and reconnect during the flash and the VM will lose the port to the host. You have to make sure the Jetson remains owned 100% by the VM at all times.

Jetson is connected, worked fine when i tried using Virtualbox and Ubuntu 16.04, guess there was change in VM container VMWare Fusion and Ubuntu 198.x LTS due to some issues in the Install SDK manager step failure with Virtualbox. Using Virtualbox, Flash was successful, OS configuration, setup on Jetson TX was fine, however installing components failed, due to connection issues with target device, lsusb seemed to show it was there. It is kind of random issues to make Nvidia Jetson TX flash and installed SDK. Not sure, why others did not have issues. I need a version that works VMWare Fusion, Ubuntu etc, as setting such as USB settings with USB 3.0 and using Linux as the default connection for USB (not MAC). Can someone post a version that works, at least i can try to reproduce with that Ubuntu version on ORacle Virtualbox and VMWare Fusion… Spent countless hours on this … no luck, seems to fail somewhere.

Is this SDK Manager 4.2 (JetPack4.2)? If so, then wired networking is virtual over USB, and the same issue of disconnect/reconnect during flash occurs for ethernet over USB…meaning that the host must give that USB virtual ethernet device completely to the VM without ever getting in the way. Even if the VM gets the virtual ethernet it may still be required to enable it in the network GUI by means of the MAC address.

For SDKM, if you monitor “dmesg --follow” on the host PC as you unplug and replug the USB you should see a message with the MAC address (this assumes the TX2 is fully booted…you can run package install at any time by unchecking flash and unchecking host side components and try this without starting over from scratch).