Trouble with JetPack4.1 install

I have the device in USB ForceRecovery Mode as per the install.

(Press ForceRecovery Button and Then power button and release together)

lsusb also shows NVIDIA corp.

Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0bda:0411 Realtek Semiconductor Corp.
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 013: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
Bus 001 Device 012: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
Bus 001 Device 004: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 016: ID 0955:7019 NVidia Corp.
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

But the install fails every time with the message below.

How can I proceed ? I was able to put 4.0 on it without issues.

###############################################################################

L4T BSP Information:

R31 (release), REVISION: 0.2, GCID: 12860113, BOARD: t186ref, EABI: aarch64,

DATE: Sat Sep 29 05:14:38 UTC 2018

###############################################################################
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.
0

you should avoid use of virtualized environments flashing the target
are you using virtualbox?
you may try flash.sh method, in my opinion.

I am using a native Ubuntu host

Where can I find the alternative flash method ?

You may found this script from where you’ve installed JetPack on host:

<wherever_you_installed_JetPack>/Xavier/Linux_for_Tegra/flash.sh

Actually I did find it, thanks. I am still unable to flash the device.

Is there a way to debug this further ?

For example can I see the recovery mode console through a usb-serial console ?

Using lsusb you should see the NVIDIA device in recovery mode from host.

Be sure to use a good quality cable…With some poor quality ones, you may be able to see the device from lsusb but unable to flash however.

I do see the NVIDIA device in recovery mode from host. Tried with 2 different cables. I will attempt with a different Ubuntu PC and see if it works.

If it doesn’t work, you may:

  • remove any non mandatory device from your Jetson that may draw power
  • remove any hub or any other device from host while flashing
  • if the above doesn’t work, and if you’re using an old host, try inserting a recent USB hub between your host and Jetson, it might improve signal quality.

Use the type-C connector next to the power LED (the kit comes with a type-C to type-A cable useful for this). Hold the recovery button down (middle of the three), tap the power button, and release all. The power LED should be on, and the following command should show the Xavier is in recovery mode:

lsusb -d -955:7019

This is the prerequisite to complete prior to starting flash. Does it get that far? Does the error show despite seeing output from “lsusb -d 0955:7019”?

It does get that far. Its failing within the get_fuse_level code inside the script.

Debugging the flash script, it looks like when its trying to find the USB device it fails even though NVidia Corp is visible in lsusb.

get_fuse_level fails even if I give it the correct bus/device

tegrarcm_v2 --instance /001/030 --uid

tegrarcm_v2 --uid

both fails with error
USB communication failed.Check if device is in recovery

lsusb

Bus 001 Device 030: ID 0955:7019 NVidia Corp.

lsusb -d -955:7019

Bus 001 Device 030: ID 0955:7019 NVidia Corp.

You may have an actual hardware issue since it is not a VM and recovery mode shows while some flash step failure. Can you attach a complete log?

~/Downloads/JetPack4.1/Xavier/Linux_for_Tegra$ sudo ./flash.sh jetson-xavier mmcblk0p1
###############################################################################

L4T BSP Information:

R31 (release), REVISION: 0.2, GCID: 12860113, BOARD: t186ref, EABI: aarch64,

DATE: Sat Sep 29 05:14:38 UTC 2018

###############################################################################
get_fuse_level
ECID tegrarcm_v2 /home/ssunil/Downloads/JetPack4.1/Xavier/Linux_for_Tegra/bootloader
hwchipid
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.

Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0bda:0411 Realtek Semiconductor Corp.
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 035: ID 0955:7019 NVidia Corp.
Bus 001 Device 024: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
Bus 001 Device 023: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
Bus 001 Device 004: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 017: ID 1050:0116 Yubico.com Yubikey NEO(-N) OTP+U2F+CCID
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I assume lsusb showed the Xavier just prior to this (and we already know it isn’t a VM)? I hate to say it, but unless someone from NVIDIA has an idea, then it might be time to RMA the board. If interested in RMA search for RMA near the top of this:
https://devtalk.nvidia.com/default/topic/793798/embedded-systems/some-jetson-web-links/

@Linuxdev thanks. Yes its not a VM and lsusb is consistent in showing the device when I put it into recovery mode. I suspect it has something to do with my PC’s USB 3.0 Roothub/Controller chip. I am going to attempt this with my laptop and see of this makes a difference. I hope its not h/w since this board is $$$. Actually I could put a USB analyzer inline and check too (I have a 3.0 analyzer), but dont want to spend too much time on it if my laptop works.

Hmm, Tried again with my older laptop running the same version of Ubuntu. It successfully flashed the JP4.1.

This may help others who run into this issue. Seems to be a USB issue of some sort.