Problem flashing Jetson TX2 d02

Autonomous Machines Jetson & Embedded Systems Jetson TX2
#1

Hi !

I am trying to flash a Jetson TX2 (d02) but flash fails. I don’t have a development board, I use another one. If I run ./flash.sh jetson-tx2 mmcblk0p1 manually, installation remains blocked at

[ 6.6888 ] Sending bootloader and pre-requisite binaries [ 6.6898 ] tegrarcm_v2 --download blob blob.bin [ 6.6906 ] Applet version 01.00.0000 [ 6.6934 ] Sending blob [ 6.6935 ] [................................................] 100% [ 7.1687 ] [ 7.1715 ] tegrarcm_v2 --boot recovery [ 7.1739 ] Applet version 01.00.0000 [ 7.1791 ] [ 8.1831 ] tegrarcm_v2 --isapplet [ 8.8828 ] [ 8.8885 ] tegradevflash_v2 --iscpubl [ 8.8910 ] Cannot Open USB [ 9.3445 ] [ 10.3484 ] tegrarcm_v2 --isapplet

I am trying to install Jetpack 4.3 in order to have CUDA 10.0 and Cudnn 7. Installation works with Jetpack 4.4.1.
Maybe the problem comes from the d02 revision ?
Flashing a Jetson from a random carrier board may cause some trouble ?

Thanks !

#2

If the host PC is a VM, then this causes a lot of problems just like this. Flashing itself should not care which carrier board is used during the flash, although booting on a carrier board without the correct firmware (mainly device tree) would be a problem (third party carrier boards require their firmware to boot, but not for flash).

Assuming the host PC is not a VM, and has nothing special about it, then I would next suspect the micro-B USB cable. The cable which arrives with the dev kit is very high quality, while most “charger” cables have very low quality. You might see 6 or more strands of copper in a good cable, and perhaps shielding, with a quality cable; however, charger cables quite often have only 2 strands of copper for data, and no shielding. They tend to work for short low speed data transfers, but fail for sustained or higher speed transfers. What is the source of your cable? Do you have other brands you can try? I’d say about 3 out of 4 “charger” cables won’t work for flashing.

#3

Thank you for the answer. Indeed my host PC is not a VM
That’s interesting but the same USB cable works with newer l4t version so I don’t think that’s the problem here. I believe that the new tx2 revision is not compatible with old l4t versions… I can’t find any information about this…

I wanted to install l4t 32.3.1 to avoid cudnn8 which is very slow…

#4

You may be correct about this, but I have not heard of TX2 revisions having any effect on older releases versus newer releases, except for different TX2 models, e.g., the TX2i industrial versus the dev kit. Are the failing module and carrier board both dev kit?

Does the command line flash continue if you unplug and replug the recovery mode Jetson’s USB when the error occurs? When the error occurs, does “lsusb -d 0955:7c18” still show the Jetson present?

#5

I had the same issues (cannot open usb) with jetpack 4.3 on a linux machine. we had multiple tx2 and some would work and some would fail. turns out it is an issue with the DRAM and eMMC changes on Nvidia’s side. here’s the product change notification from one of our suppliers https://connecttech.com/ftp/pdf/CTIU-00030.pdf

My question regarding this issue is if there’s guide that we can reference the serial number to figure out if it has this product change. For example, serial number XXXXX and above has the new DRAM and eMMC and requires Jetpack 4.4

#6