unable install any JetPacks Jetson TX2
I'm cabling some standard micro-USB --- USB cable between Jetson TX2 and HOST=Ubuntu 16.04 DELL Precision 5520 Notebook with 3.0 USB-connector I'# install all necessary software in host: tar xpf ./Tegra186_Linux_R28.2.0_aarch64.tbz2 $sudo tar xpf ../../Tegra_Linux_Sample-Root-Filesystem_R28.2.0_aarch64.tbz2 $sudo flash.sh jetson-tx2 mmcblk0p1 I've press RC-Btn and shortly also Rest-button and now I can see output from $lsusb -d 0955:7c18 Bus 001 Device 062: ID 0955:7c18 NVidia Corp. afterthat: $sudo ./flash.sh jetson-tx2 mmcblk0p1 It always failed (with and w/o usb-2.0 hub) with the same error: ############################################################################### # L4T BSP Information: # R28 (release), REVISION: 2.0, GCID: 10567845, BOARD: t186ref, EABI: aarch64, # DATE: Fri Mar 2 04:57:01 UTC 2018 ############################################################################### Error: probing the target board failed. Make sure the target board is connected through micro-B USB port and is in recovery mode. What's wrong?
I'm cabling some standard micro-USB --- USB cable between Jetson TX2 and HOST=Ubuntu 16.04 DELL Precision 5520 Notebook with 3.0 USB-connector
I'# install all necessary software in host:

tar xpf ./Tegra186_Linux_R28.2.0_aarch64.tbz2
$sudo tar xpf ../../Tegra_Linux_Sample-Root-Filesystem_R28.2.0_aarch64.tbz2
$sudo flash.sh jetson-tx2 mmcblk0p1

I've press RC-Btn and shortly also Rest-button and now I can see output from
$lsusb -d 0955:7c18
Bus 001 Device 062: ID 0955:7c18 NVidia Corp.

afterthat: $sudo ./flash.sh jetson-tx2 mmcblk0p1

It always failed (with and w/o usb-2.0 hub) with the same error:

###############################################################################
# L4T BSP Information:
# R28 (release), REVISION: 2.0, GCID: 10567845, BOARD: t186ref, EABI: aarch64,
# DATE: Fri Mar 2 04:57:01 UTC 2018
###############################################################################
Error: probing the target board failed.
Make sure the target board is connected through
micro-B USB port and is in recovery mode.



What's wrong?

#1
Posted 04/03/2018 04:09 PM   
You should use the specific USB cable[micro-B] for flashing , and you should put jetson in recovery mode. Could you execute at the HOST PC [code]lsusb [/code] and verify you can see NVIDIA device ?
You should use the specific USB cable[micro-B] for flashing , and you should put jetson in recovery mode.
Could you execute at the HOST PC
lsusb

and verify you can see NVIDIA device ?
#2
Posted 04/03/2018 05:32 PM   
He already showed that he can see the device: [code]$lsusb -d 0955:7c18 Bus 001 Device 062: ID 0955:7c18 NVidia Corp. [/code]
He already showed that he can see the device:
$lsusb -d 0955:7c18
Bus 001 Device 062: ID 0955:7c18 NVidia Corp.

#3
Posted 04/03/2018 05:45 PM   
Thank you for pointing that out!
Thank you for pointing that out!
#4
Posted 04/03/2018 06:12 PM   
It seems that device is connected somehow and in recovery mode. What is the return of [code]uname -a[/code] at HOST PC?
It seems that device is connected somehow and in recovery mode.
What is the return of
uname -a
at HOST PC?
#5
Posted 04/03/2018 06:14 PM   
$uname -a Linux abcd-Precision-5520 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$uname -a
Linux abcd-Precision-5520 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

#6
Posted 04/03/2018 07:18 PM   
could you also provide output of [code]cat /etc/*release[/code] ?
could you also provide output of
cat /etc/*release

?
#7
Posted 04/03/2018 07:23 PM   
Is the cable you used the micro-B USB supplied with the kit?
Is the cable you used the micro-B USB supplied with the kit?
#8
Posted 04/03/2018 07:26 PM   
I can see an alike case here : https://devtalk.nvidia.com/default/topic/1029740/jetson-tx-2-fail-to-flash-ubuntu-16-jetpack-3-1-3-2/
$ cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS" NAME="Ubuntu" VERSION="16.04 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" UBUNTU_CODENAME=xenial
$ cat /etc/*release

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
NAME="Ubuntu"
VERSION="16.04 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
UBUNTU_CODENAME=xenial

#10
Posted 04/03/2018 07:41 PM   
Could you approach flashing jetson from a different PC ?
Could you approach flashing jetson from a different PC ?
#11
Posted 04/03/2018 07:49 PM   
I am guessing it is the cable. Most "standard micro-USB" are not valid cables...many are intended only for charging (some don't even have the data wire). If the cable is not the one which came with the Jetson, then the cable is very likely the issue.
I am guessing it is the cable. Most "standard micro-USB" are not valid cables...many are intended only for charging (some don't even have the data wire). If the cable is not the one which came with the Jetson, then the cable is very likely the issue.

#12
Posted 04/03/2018 09:08 PM   
* flashing jetson from a different PC* Yes, I'll try to use VM, it's not so fast, wait little bit
* flashing jetson from a different PC*
Yes, I'll try to use VM, it's not so fast, wait little bit

#13
Posted 04/04/2018 08:33 PM   
Don't use a VM...this will fail.
Don't use a VM...this will fail.

#14
Posted 04/04/2018 09:31 PM   
[quote=""]Don't use a VM...this will fail.[/quote] Hmm, in our office we have only new Ubuntu-16.04 notebooks with usb-3.0. I'll try to pick up my old PC-notebok with USB-2.0 and Windows-7 from home. And install Ubuntu-14 VM and try to forward USB form Win to VM. Isn't that the best choice? P.S.: Unfortunately we've lost the original USB-cabel form NVIDIA :(
said:Don't use a VM...this will fail.


Hmm, in our office we have only new Ubuntu-16.04 notebooks with usb-3.0.
I'll try to pick up my old PC-notebok with USB-2.0 and Windows-7 from home.
And install Ubuntu-14 VM and try to forward USB form Win to VM.

Isn't that the best choice?

P.S.: Unfortunately we've lost the original USB-cabel form NVIDIA :(

#15
Posted 04/05/2018 04:34 PM   
Scroll To Top

Add Reply